★ 4.6 / 5
from 695 verified reviews on G2, Capterra and Trustpilot
vCard Converter For Every Contact List
PCDOTS vCard Converter Software reads VCF contact files on Windows and converts them to PST, CSV, PDF, Excel, HTML and live cloud address books. Auto-detects every vCard version, decodes platform encoding quirks, and preserves photos and custom fields through the conversion.
Bulk vCard work breaks generic converters in three ways: mixed versions (single VCF files holding vCard 2.1, 3.0 and 4.0 together), encoding inconsistency (Samsung quoted-printable, iPhone BASE64 photos, Google URI references), and X-PROPERTIES (platform-specific custom fields like X-ABRELATEDNAMES, X-GOOGLE-TALK, X-MS-OL-DESIGN). The PCDOTS software auto-detects version per record, decodes encoding transparently, and preserves X-PROPERTIES through the output.
Auto-Detection of vCard 2.1, 3.0 and 4.0
The parser reads the VERSION line at the top of each BEGIN:VCARD block and applies the appropriate field rules per record, so a single VCF can mix all three versions and the converter handles each correctly. Compliant with RFC 6350 (vCard 4.0), RFC 2426 (3.0) and RFC 2425 (2.1).
Per-record version detection (handles mixed-version VCF files)
Quoted-printable, BASE64 and UTF-8 encoding decoded transparently
RFC 2425, 2426, 6350 compliant; X-PROPERTIES preserved where possible
Choosing What to Convert (and What to Skip)
Filter the VCF before conversion by name pattern, company, phone area code, email domain, birthday range or category. Filters apply at parse time, so a 10,000-contact source filtered down to 200 matches converts in roughly the time those 200 records would take on their own.
Filter by name, company, phone area code, email domain, category
Filters apply at parse time, runtime proportional to selection
Useful for trimming long-accumulated address books before migration
Reading the Contact the Way the Source App Stored It
The preview pane shows three views on every record: rendered output (the way the source app displayed the contact), full field listing (every property with its value, including X-PROPERTIES), and raw VCF bytes (for diagnosing encoding issues). Same tool ships in the standalone PCDOTS VCF Viewer.
Three render views: rendered, field listing, raw VCF bytes
Catches encoding issues before they reach the output
Same tool ships in standalone PCDOTS VCF Viewer
Bulk Conversion of Many VCF Files
Queue a folder of VCF files (one per sales rep, one per phone backup, one per CRM dump) and process them under a single job with one progress display. Memory footprint stays flat regardless of queue depth. Tested up to 200 VCF files / 500,000 contacts in a single execution.
Reads vCard From Any Source Application
Tested coverage: Apple Contacts (iCloud, macOS), Google Contacts, Samsung phones (quoted-printable), iPhone (BASE64 photos), Android, Outlook (X-MS-OL-DESIGN), BlackBerry, Skype, WhatsApp, LinkedIn, plus generic CardDAV exports. Source detection runs at file load.
Merge Many VCF Into One, or Split One Into Many
Two complementary operations on the same parsed contact set. Merge combines a folder of single-contact VCF files (iPhone-style) into a single multi-contact VCF. Split takes a multi-contact VCF (Outlook-style) and produces one VCF per contact named after the FN field.
Extracting Specific Fields Out of an Address Book
When the goal is not full migration but specific data: email addresses (TXT or CSV), phone numbers (E.164 normalized), contact photos (folder of JPG files), company names (CRM enrichment CSV). Field extraction works against the same parsed VCF as the converter.
Direct Delivery to Cloud Address Books
Output writes directly to live contact services via OAuth (Microsoft 365, Google Contacts) or CardDAV (any standards-compliant server, plus iCloud). The intermediate VCF or CSV file step disappears.
No Outlook or Address Book Software Required
Runs on a bare Windows PC with .NET Framework 4.5+ only. No Outlook, no Office license, no Java runtime, no mobile-device drivers. Compatible with Windows XP through 11, plus all Server editions from 2003 through 2022.
18K+Address books in regression suite
21Years tracking vCard versions
99.5%Field preservation across versions
12Output destinations
Simple 3-Step Process
The Three-Stage vCard Workflow
vCard conversion follows three logical stages: load the source, decide what crosses over to the output, write to the destination. Each stage corresponds to a specific operator decision. The detailed 11-step walkthrough later on the page covers advanced filter rules, merge/split operations, and authenticated cloud destinations.
01
1. Load the Source VCF
Three input modes cover the common cases. Single file: one VCF containing many contacts (typical for Outlook or Google Contacts exports). Folder of files: many VCF files each with one contact (typical for iPhone and Apple Contacts exports). Mixed folder: a directory tree containing both layouts (typical for accumulated phone backups). The parser handles all three the same way.
02
2. Verify and Filter
The preview pane is the operator decision point. Browse the loaded contacts, verify that names with non-Latin characters render correctly (catches Samsung quoted-printable issues), check that photos came through as images and not as raw BASE64 strings, confirm that the version detection identified each record correctly. Apply filter rules at this stage: by name pattern, company, phone area code, email domain, birthday range. The conversion writes only what the filters match.
03
3. Write to the Destination
Three output categories. Email and contact file formats: PST for Outlook, CSV for Excel and most CRM tools, vCard (any version) for re-export, MSG for individual contact records. Document formats: PDF, PDF/A, HTML, XLSX. Live cloud and CardDAV: Microsoft 365, Google Contacts, iCloud Contacts, generic CardDAV. The conversion writes every preserved field, including X-PROPERTIES where the destination format supports them.
Software Compatibility
Supported vCard Sources and Output Formats
Reads from every common vCard source: iCloud exports, Google Contacts, Outlook contacts, Samsung phones, iPhone, Android. Writes to every common destination: file formats, document formats and live cloud services.
vCard Sources
Tested Across Every vCard Version and Platform
The vCard converter for Windows reads VCF files from desktop apps, mobile devices, cloud services and CRM systems. Whether the file came from a Samsung Android export (vCard 2.1 with quoted-printable), a Pixel device (vCard 3.0), an iCloud download (vCard 3.0) or a CardDAV server (vCard 4.0), the converter handles it natively.
vCard 2.1 (Versit specification, 1996)
vCard 3.0 (RFC 2426, the most common)
vCard 4.0 (RFC 6350, with KIND and GENDER)
iCloud Contacts exports
Google Contacts exports
Outlook 2010, 2013, 2016, 2019, 2021, 365 contacts
Samsung Android vCard 2.1 (with QP encoding)
iPhone Contacts app exports
Skype contacts
WhatsApp contact backups
LinkedIn contact exports
Quoted-printable encoded files
PCDOTS vCard Converter v3.4
All Sources
Complete Format Coverage
Every Supported vCard Source and Output, Listed in Detail
Browse the full list of vCard versions, source platforms and output destinations the vCard converter tool reads and writes.
vCard Source Versions3 versions
Version
Year
Specification
Description
vCard 2.1Input
1996
Versit Consortium (no IETF RFC)
Original vCard format. Uses per-property CHARSET parameters and quoted-printable encoding for non-ASCII text. Still produced by Samsung Android phones and many legacy systems.
Configurable column mapping. Each contact becomes one row, fields become columns.
PST
Microsoft Outlook
Direct import as Outlook Contacts folder. Photos preserved as embedded images.
PDF
Printable contact sheets, archiving
One contact card per page or condensed list view. Photos rendered inline.
Excel (XLSX)
Spreadsheet analysis
Native Excel format with formatted columns and freeze headers.
HTML
Web-based contact directory
Self-contained HTML with embedded photos. Opens in any browser.
vCard 3.0 / 4.0
Version upgrade
Convert old vCard 2.1 files to modern 3.0 or 4.0. Decodes quoted-printable, removes CHARSET parameters, normalizes UTF-8.
TXT
Plain text archiving
One contact per record with field labels. Useful for grep, indexing, scripting.
Cloud & Service Destinations5 destinations
Destination
Type
Auth Method
Notes
Google Contacts
Cloud Contact Service
OAuth 2.0
Direct push to Google Contacts. Labels and contact groups preserved.
iCloud Contacts
Cloud Contact Service
App-specific Password
Apple iCloud sync. Groups and contact metadata preserved.
Microsoft 365
Cloud Business
OAuth 2.0 / Modern Auth
Direct push to Exchange Online Contacts. Photos preserved.
Outlook.com
Webmail
OAuth 2.0
Microsoft personal Outlook.com address book.
Any CardDAV Server
Universal Protocol
HTTPS / Basic Auth
Push to any CardDAV-compliant server: FastMail, ownCloud, Nextcloud, Radicale, Baikal.
Advanced Filters
Reading, Searching and Extracting From the Same Loaded Address Book
Beyond simple conversion, the same loaded VCF supports three operations at no extra parse cost: reading (preview pane), searching (indexed query across the loaded set), and extracting (pulling specific fields without a full conversion output).
Reading mode is the natural starting point for any vCard project. The preview pane runs three view layers against every record: rendered output, full field listing (with X-PROPERTIES), and raw VCF bytes for diagnosing Samsung quoted-printable, BASE64 photo corruption and X-PROPERTY drift before they reach the conversion output. The same software ships in the standalone PCDOTS Email Forensics Investigation product. tool.
Search across eight fields: full name, email, phone, organization, title, address, category, X-PROPERTY value. Boolean operators (AND, OR, NOT) combine field queries; phrase searches in quotes work for multi-word values. Match results export as a separate output without rerunning the full conversion.
PCDOTS vCard Converter v3.4
Smart Search
Why Users Switch to PCDOTS
Four Recurring vCard Problems and Their Resolutions
The four problems below are the recurring failure modes that drive vCard conversion support cases. Each maps to a specific resolution path in the converter. The list is derived from 21 years of customer support data covering vCard work across phones, CRMs, and cloud address books.
Problems You're Facing
Problem: non-Latin names display as encoding stringsThe way Samsung phones (and some other Android devices) export vCard is with quoted-printable encoding on non-ASCII characters. So "Müller" becomes "M=C3=BCller" in the VCF file. Apps that ignore the encoding header (CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE) display the encoded string verbatim. The contact data is not corrupted, but every downstream consumer sees broken text.
Problem: Outlook imports vCard files one at a timeMicrosoft Outlook native vCard import handles single VCF files with one contact each. A 5,000-contact phone export, even split into 5,000 individual files, requires 5,000 manual import operations. There is no built-in bulk-import path. Outlook will accept a PST file with thousands of contacts, but vCard does not natively convert to PST without an intermediate tool.
Problem: CRM expects CSV with specific column mappingsMost CRM platforms (Salesforce, HubSpot, Zoho, Pipedrive) accept contact import via CSV with specific column headers that match their internal field names. A raw VCF file does not match any of these layouts. Manually converting via text editor loses photo data, address structure (street/city/state separated), and category tags. A direct VCF-to-CSV converter that does not understand CRM column conventions produces a CSV that the CRM imports incorrectly.
Problem: a single VCF file contains mixed vCard versionsLong-accumulated address books contain records imported from different sources at different times. The same VCF file can hold vCard 2.1 records (older imports), vCard 3.0 records (the most common middle version), and vCard 4.0 records (current). Field rules differ between versions; converters that assume single-version input apply the wrong rules to mixed records and silently corrupt fields like phone number formatting and date encoding.
PCDOTS Solves Each One
Resolution: transparent quoted-printable decodingThe parser reads the CHARSET and ENCODING parameters per field, applies the appropriate decoder, and outputs clean Unicode. "M=C3=BCller" in the source becomes "Müller" in the output, with full UTF-8 preservation through the destination format. The same handling applies to BASE64-encoded photos, URL-encoded address fields, and any other encoded property the vCard format supports.
Resolution: native PST writer with bulk contact supportThe PST writer produces an Outlook-compatible PST file containing contacts as native Outlook contact items, with photos embedded as Outlook-native attachments and X-MS-OL-DESIGN preservation where present. PST output imports cleanly into Outlook 2007 through Microsoft 365 with a single operation, regardless of how many contacts the source VCF contained. Tested up to 500,000 contacts in a single PST output.
Resolution: CSV output with CRM-aware column mappingThe CSV writer produces output with column headers matching common CRM templates: Salesforce, HubSpot, Zoho, Pipedrive, and a generic CRM template that covers most niche systems. Phone numbers normalize to E.164. Addresses split into street, city, state, postal code, country columns. Photos export as a sibling folder with filename references in the CSV. The result imports into the destination CRM without manual column remapping.
Resolution: per-record version detection in the parserThe parser handles version per record, not per file. Each BEGIN:VCARD block is read with its own VERSION line, the appropriate field rules apply for that version, and the next record can use a different version without affecting parsing. Mixed-version VCF files (the typical case for accumulated address books) parse correctly without operator intervention.
Real-World Applications
Six Common Reasons People Convert vCard Files
The way the vCard format works in practice is that it is rarely the final destination for the contact data. It is almost always a transit format: a phone exports it, then it needs to become CSV for a CRM, or PST for Outlook, or live records in a cloud address book. The six scenarios below cover most of what people actually do with the vCard converter once they have a VCF file in front of them.
Loading VCF Contacts Into a New CRM
Migrating contacts into Salesforce, HubSpot, Zoho or any CRM. The converter writes CSV with column headers matching common CRM templates, preserves photo references where supported, and normalizes phone numbers to E.164 for global tenants.
Moving Contacts Between Phone Ecosystems
Switching from Samsung to iPhone or Android to iCloud. The converter normalizes Samsung quoted-printable encoding, converts iPhone BASE64 photos, and produces a clean destination-compatible VCF that imports without errors.
Extracting Email Addresses for Marketing
Field extraction pulls email addresses from the loaded VCF set into deduplicated CSV with one row per recipient. Optional filtering: by category, organization, domain. Useful for marketing list builds after a CRM platform change.
Loading Networking Contacts Into an ATS
Recruiting and HR teams loading business cards, LinkedIn exports and event attendee lists into an Applicant Tracking System. The converter writes CSV with column headers matching ATS candidate templates and preserves company / title fields that drive matching algorithms.
Personal Address Book Backup to PDF
Personal vCard backup as a printable PDF with one contact per page or directory layout, photos rendered inline, alphabetical index. PDF/A output (per ISO 19005-1) for long-term archival storage.
Deduplicating and Splitting an Address Book
Long-accumulated address books with the same contact in multiple forms. Merge collapses duplicates by name and phone match; Split takes a multi-contact VCF and produces one VCF per contact named after the FN field.
Why Customers Choose This Tool
Eight Things This Tool Does That Generic VCF Converters Skip
Generic VCF converters handle the easy cases: a single-version VCF file, ASCII names, no photos, small contact counts, no platform-specific X-PROPERTIES. The eight capabilities below address the cases where generic tools quietly fail or produce broken output. Each capability is derived from 21 years of customer support data covering vCard work across phone ecosystems, CRM platforms and address book consolidation.
Local-Only Processing
VCF files never leave your workstation. Network requests issue only when the operator selects a cloud destination, and they go directly host-to-destination without intermediation. Compatible with GDPR and HIPAA-protected contact data.
One-Time License, No Recurring Cost
$49 one-time payment covers lifetime usage on the operator workstation. No annual renewal, no subscription billing, no per-contact fees. Updates ship at no additional cost. 30-day refund if the conversion does not meet documented capabilities.
Bulk Queue for Large Address Book Sets
The batch queue accepts a folder root, walks it recursively for VCF files, and processes each in source order under a single job. Memory footprint stays flat regardless of total queue size. Tested ceiling: 200 VCF files containing 500,000 total contacts.
Field-Level Preservation Through the Conversion
Every property, value, encoding and X-PROPERTY passes through to the output where the destination format supports it. CSV preserves photos as base64; PST stores them as Outlook-native attachments; cloud destinations write photos to the destination CDN.
Forensic Inspection of vCard Bytes
The forensic preview pane runs three render layers simultaneously: rendered output, full field listing, raw VCF bytes. Surfaces Samsung quoted-printable errors, BASE64 photo corruption, missing PROPID separators in Outlook X-PROPERTIES.
Verify Output Before Committing the Conversion
Preview mode renders any contact with the appearance it would have in the destination format. Catches structural mismatches (different version, missing required fields, different photo encoding) before committing a long export run that produces broken output.
Direct Delivery to Cloud Address Books
OAuth-authenticated direct delivery to Microsoft 365, Google Contacts, and any CardDAV server (including iCloud Contacts). Skips the intermediate VCF or CSV file step entirely. Authentication, throttling backoff and retry logic execute inside the converter.
Twenty-One Years Tracking vCard Format Changes
PCDOTS has shipped Windows contact tools since 2005. vCard 2.1, 3.0, 4.0 and platform X-PROPERTIES integrated into the regression suite within the major release after publication. Product line at pcdots.com covers other formats; this tool stays focused on vCard.
Technical Specs
System and Software Requirements
What you need to run the vCard converter for Windows, plus the trial limitations.
Software Name
PCDOTS vCard Converter
Current Version
3.4
Processor
Pentium-class or higher (Intel Pentium 4 / 1 GHz+)
RAM
Minimum 512 MB, 2 GB recommended for large address books (50,000+ contacts)
Hard Drive Space
150 MB free space for installation
Operating System
Windows 11, 10, 8.1, 8, 7, Vista, XP. Server 2019, 2016, 2012, 2008, 2003 and earlier.
Trial limitation: the demo edition exports up to 10 contacts per file so you can verify accuracy on real data before purchasing. The full edition has no limits and ships with a lifetime license.
Trial vs Full
Trial vs Full Edition for vCard Conversion
Both editions ship the same conversion wizard, with the same parser, the same destination writers, the same preview pane. The trial caps each source file at 10 contacts in the conversion output for evaluation. The full edition (one-time $49 license) removes the cap, adds priority technical support, and includes lifetime updates.
Feature
Trial Version
Full Version
Conversion output volume per file
Capped at 10 contacts per file
✓ No cap
vCard 2.1, 3.0, 4.0 with per-record version detection
✓
✓
Multi-destination output (PST, CSV, M365, Google Contacts)
The vCard converter market splits into three groups. Paid commercial tools (vCard Wizard, BitRecover, eSoftTools) priced from $30 to $80. Free online VCF services that accept VCF upload to a third-party server. Built-in OS tools (Outlook, Apple Contacts) that handle single-VCF imports but lack bulk processing. The PCDOTS converter combines the privacy posture of a local tool with the bulk capabilities of paid alternatives plus the format depth (mixed-version handling, encoding decoding, X-PROPERTY preservation) typically missing from all three groups. Comparison data below comes from public vendor pages and hands-on testing on representative VCF files.
Feature
Best ChoicePCDOTS
Other Paid ToolsSysTools, Softaken, RecoveryTools
Free Tools / Online
vCard 2.1, 3.0, 4.0 with per-record version detection
All 3
Partial
Usually 1 or 2
Output destinations and vCard version coverage
10+
3 to 8
1 to 2
Quoted-printable and BASE64 transparent decoding
Automatic
Partial
No
Direct delivery to Google Contacts and iCloud
Yes
Partial
No
Bulk multi-file processing
Unlimited
Limited per batch
No
Photos and X-PROPERTY preservation
Yes
Partial
Usually No
Forensic preview pane (hex / raw bytes)
Yes
No
No
Mixed-version VCF handling
Yes
Often Fails
No
Local-only processing (privacy)
100% Local
Mixed
Cloud Upload
Lifetime license model
Yes ($49)
Subscription common
Free (limited)
Video Tutorial
Watch How to Convert vCard / VCF Files in 5 Minutes
A short walkthrough showing every step of the vCard to CSV / PST workflow, from opening the source file to verifying output in your destination app.
5 min walkthrough
YouTube
Real Performance Numbers
vCard Conversion Performance Reference
The numbers below combine two reference sources. Internal regression testing: 18,000+ address books spanning vCard 2.1, 3.0 and 4.0 from iCloud, Google Contacts, Samsung, iPhone, Android, BlackBerry and Outlook. Customer survey data: 695 verified reviewers reporting on production vCard conversion outcomes.
90%
Customer Satisfaction
95%
Output Accuracy
97%
Successful Conversions
85%
Recommend to Peers
How It Works
The Full Eleven-Step vCard Conversion Walkthrough
The three-step quick guide further up the page covers the standard conversion. The 11 steps below go deeper: filter rules, merge/split operations, advanced output options, verification before relying on the converted contacts. Each step has an associated screenshot from a real conversion run. Operator time: 6 to 12 minutes for a configured conversion, plus the unattended runtime of the conversion itself.
1. Launch the Converter on Windows
Install PCDOTS vCard Converter on a Windows PC and launch from the Start menu or desktop shortcut. Architecture detection at install time selects the appropriate 32-bit or 64-bit binary. Outlook, address book software and mobile-device drivers are not required on the conversion machine.
2. Open the VCF Source
Click Email Data File and select vCard / VCF. Acceptable inputs: a single VCF file (typical for Outlook or Google Contacts exports), a folder of single-contact VCF files (typical for iPhone exports), or a mixed folder containing both layouts. The parser handles all three the same way.
3. Add Files to the Queue
Browse to the source VCF file or folder. The queue accepts individual files (Ctrl-click to add multiple) or recursive folder selection. Each entry shows the contact count after parsing. Mixed vCard versions in a single file or across the queue are handled without operator intervention; the parser detects version per record.
4. Parse the Loaded Address Book
The parser reads each VCF file in the queue and extracts every contact record. Quoted-printable encoding (Samsung-style "M=C3=BCller" handling), BASE64-inline photos (iPhone-style), URI-referenced photos (Google Contacts-style), and platform-specific X-PROPERTIES all decode transparently during this stage. The contact count, total size and detected vCard versions display in the loaded-data summary.
5. Verify Records in the Preview Pane
Click any contact to render the full record in the preview pane. Three view layers work simultaneously: rendered output (the way the source app would have displayed it), full field listing (every property with its value, including X-PROPERTIES), and raw VCF bytes. This is when the operator catches encoding issues, missing photos, or character set drift before committing the conversion.
6. Search and Filter the Loaded Set
Open Quick Search to query the loaded address book across eight fields: full name, email, phone, organization, title, address, category, X-PROPERTY value. Boolean operators combine field queries. Useful when the conversion scope is narrow (specific senders, specific company, specific area code) rather than the full set.
7. Select the Output Format
Click Export to open the destination picker with three categories: email and contact file formats (PST, EML, MSG, vCard re-export), document formats (PDF, PDF/A, HTML, CSV, XLSX), live cloud and CardDAV (Microsoft 365, Google Contacts, iCloud, generic CardDAV). The selection drives which writer the conversion software engages.
8. Configure Output Options
Browse to the destination folder for file outputs, or authenticate against the destination tenant for cloud destinations. Optional configuration covers CSV column header templates (Salesforce, HubSpot, Zoho, generic), photo handling (inline BASE64, sibling folder, URI references), file naming patterns, and post-completion actions ("open destination folder", "delete source on success").
9. Run the Conversion
The Save button commits the conversion job. Live progress display shows per-file counts, the current contact being processed, and a recalculated time-remaining estimate updating every 30 seconds based on observed throughput. The diagnostic log streams in parallel, recording any items the converter flagged for review (typically encoding ambiguities or missing required fields).
10. Inspect the Output
On completion, the Open Folder button launches the destination directory in Windows Explorer. The trial edition writes up to 10 contacts per source file for verification; the licensed edition writes the entire address book without per-file caps. The diagnostic log saves alongside the output as a sibling file.
11. Verify Sample Before Source Deletion
Before deleting the source VCF file or relying on the converted output, open the conversion result in its destination application (Outlook for PST, Excel for CSV, Google Contacts webmail for cloud destinations) and verify a sample. Recommended sample: 1% of total contacts, biased toward records with non-Latin names, photos, and X-PROPERTY data. The diagnostic log identifies which records deserve closest verification scrutiny.
Independent Validation
Reviewed and Awarded by Trusted Software Sites
Independent third-party reviews verify the vCard Converter Wizard performance against advertised capabilities. Each award listed below is sourced from the original publisher (G2, Capterra, Trustpilot, Software Suggest). The aggregate rating combines feedback from 695 verified reviewers since the most recent major release.
4.6
Average across all reviews
695
Verified user reviews
4
Editor's Choice awards
Editor's Pick
5.0
Software Informer
"Editor's Pick award for clean, intuitive vCard / VCF migration to CSV, PST and other formats with no data loss."
Editor's Pick
100% Clean
5.0
Softpedia
"100% Clean award for malware-free, virus-free vCard conversion across all supported versions and formats."
100% Clean Award
5-Star Certified
5.0
Soft32
"5-star certified for excellence in vCard / VCF conversion accuracy, performance and ease of use."
5-Star Certified
Safe Download
5.0
Filehippo
"Safe download verified: clean, signed installer with no bundled adware or unwanted extras."
Safe Download
Verified secure download. Every award listed has been issued by the corresponding directory based on independent malware scans, feature reviews and user feedback.
Quick Definition
What is a vCard Converter?
A vCard converter is a desktop tool that reads vCard / VCF contact files (the standard format for sharing address book entries between phones, email clients, CRM systems and cloud services) and converts them into other formats (CSV, PST, PDF, Excel, HTML) or delivers them to other contact services (Google Contacts, iCloud, Outlook). The vCard format has three versions: 2.1 (1996, Versit), 3.0 (RFC 2426, 2001) and 4.0 (RFC 6350, 2011).
A good vCard converter handles all three versions automatically, decodes legacy quoted-printable encoding (common in Samsung Android exports), preserves photos and custom fields, and produces output that imports cleanly into the destination application. PCDOTS vCard Converter is the most-tested option for IT teams handling contact migrations between iPhone, Android, iCloud, Google, Outlook and CRM systems.
Quick Verdict
Best for: Anyone who has VCF files but no working application that handles them at scale. Common audiences: CRM administrators consolidating contact databases, IT teams handling phone-to-phone migration for departing employees, individual users moving contacts between Apple/Google/Samsung ecosystems.
Free trial: 10 contacts per file, no credit card, lifetime trial.
Price: $49 one-time payment for a lifetime license.
Platforms: Windows 11, 10, 8, 7, Vista, XP plus all Server editions.
Rating: 4.6 out of 5 from 695 verified reviews on G2, Capterra and Trustpilot.
Privacy: 100% local processing, GDPR-compliant, no data uploaded to PCDOTS servers.
FAQs
Common Questions About vCard Conversion
The 12 questions below address the recurring vCard scoping concerns from CRM administrators, IT teams handling phone migration, and individual users moving contacts between platforms. Answers cite vCard versions, source applications, encoding handling and licensing terms where applicable, so the FAQ functions as a scoping reference for vCard conversion projects.
How do I open a VCF file from my phone on Windows?
The way the workflow runs: download PCDOTS vCard Converter on a Windows PC, transfer the VCF file from the phone to the PC (USB cable, email-to-self, cloud sync), open the converter and click Open, select the VCF file or the folder containing it. The parser reads the file and shows every contact in the preview pane. From there, click Export and select the destination: PST for Outlook, CSV for spreadsheet or CRM, vCard for re-export to a different platform, or direct delivery to Google Contacts, iCloud Contacts or Microsoft 365. Single-file conversions complete in seconds; bulk conversions scale linearly with contact count.
Can I extract just the email addresses from a folder of VCF files?
Yes, this is the standard marketing-list use case. The field extractor pulls email addresses from every contact in the loaded VCF set (single file or folder of files) and writes them as a deduplicated CSV with one row per address. Optional filtering: by category, by organization, by domain, by recipient pattern. The same operation also works for phone numbers (line-delimited TXT or CSV with E.164 normalization), addresses (CSV with split street/city/state/postal/country columns), and contact photos (folder of JPG files named after the FN field). Field extraction works against the same parsed VCF as the converter, so the parse cost amortizes if multiple extractions run in sequence.
How many VCF files can the converter handle in one bulk job?
No file count or contact count limit in the licensed edition. The batch queue accepts a folder root, walks recursively for VCF files, and processes each in source order under a single job. Memory footprint stays flat regardless of total queue size. Tested ceiling: 200 VCF files containing 500,000 total contacts in a single execution. Live progress display shows per-file counts and a recalculated time-remaining estimate updating every 30 seconds based on observed throughput. The trial edition processes any size queue but caps each source file at 10 contacts in the conversion output.
My VCF file is on a Mac but I want to convert on Windows. Will that work?
Yes. The vCard format is identical across operating systems (it is a plain-text format defined by RFC 6350), so a VCF file created by Apple Contacts on macOS reads exactly the same when copied to a Windows machine. The standard cross-platform workflow: export the VCF on the Mac, transfer to a Windows PC (network share, USB drive, cloud sync, email-to-self), run PCDOTS vCard Converter on the Windows side. Alternative: run the converter inside a Windows guest VM under Parallels Desktop, VMware Fusion, or VirtualBox, with the VCF file mounted into the VM. PCDOTS does not ship a native Mac or Linux build.
Can I convert only certain contacts from a large VCF file?
Yes, this is what the filter layer is for. Per-contact checkboxes work for short lists (under 500 contacts) where manual selection is practical. Filter rules work for larger sets: by name pattern, company name, phone area code, email domain, birthday range, category. Filters apply at parse time, so a 10,000-contact source filtered down to 200 actual matches converts in roughly the time those 200 records would take on their own. Result sets export as separate output without re-running the parse. Reference application: extracting just the contacts in one specific area code from a national contact database for a regional marketing campaign.
My VCF file mixes vCard 2.1, 3.0 and 4.0 records. Will the converter handle that?
Yes. The parser reads the VERSION line at the top of each BEGIN:VCARD block, applies the appropriate field rules for that version, and continues to the next record. A single VCF file can mix all three versions and the converter handles each correctly. This case is more common than it sounds: long-accumulated address books contain records imported from different sources at different times, and each source may have used a different vCard version. The output normalizes to the destination format's native conventions (CSV, PST, PDF, etc.) regardless of source version mix.
Will any contact field get dropped during the conversion?
The way the conversion handles fields: every property in the source VCF maps to a field in the destination format where one exists, and falls through to a notes field where one does not. For PST output, every Outlook-supported contact field (FN, EMAIL, TEL, ADR, ORG, TITLE, PHOTO, NOTE, plus a long list of others) maps directly. For CSV output, the column header set covers all standard properties plus selectable column templates for common CRMs. For X-PROPERTIES (platform-specific custom fields like X-ABRELATEDNAMES from Apple), the converter preserves them where the destination supports custom fields and writes them to the diagnostic log where it does not. The diagnostic log lists every field that was preserved, transformed or dropped.
My Samsung VCF shows "M=C3=BCller" instead of "Müller". Why does that happen and does the converter fix it?
The way Samsung phones export vCard files is with quoted-printable encoding on non-ASCII characters. The actual data in the file says FN;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:M=C3=BCller, which the format spec defines as encoding rules that consumers must decode. Apps that ignore the encoding header (which is most consumer apps) display the encoded string literally. The data is not corrupted; it just has not been decoded. PCDOTS reads the encoding header per field, applies the appropriate decoder, and outputs clean Unicode. So "M=C3=BCller" in the source becomes "Müller" in the output, and "Fran=C3=A7ois" becomes "François", with full UTF-8 preservation through the destination format.
Will my contact photos come through after the conversion?
Yes, with handling that depends on how the source stored the photo and what the destination expects. BASE64 inline photos (iPhone, Apple Contacts) decode to bytes and write to the destination as native attachments (PST), embedded images (PDF), inline base64 (CSV), or sibling JPG files (CSV with photo folder). URI-referenced photos (Google Contacts) preserve as references where the destination supports them, or fetch and embed where it does not. VCF re-export preserves the original encoding mode. Photo size limits, format conversions and aspect ratios apply only at the destination side; the converter passes through whatever the source stored.
Does my contact data get uploaded to a server during the conversion?
No. The conversion runs entirely on the operator workstation. VCF files, contact data, photos, and authentication credentials never transit PCDOTS infrastructure. Network requests issue only when the operator selects a cloud destination (Microsoft 365, Google Contacts, iCloud), and those requests go directly from the host machine to the destination service without intermediation. The architecture satisfies GDPR data sovereignty requirements and is compatible with handling regulated contact data (HR records, healthcare patient lists, legal client contacts).
Can I combine many VCF files into one, or split a multi-contact VCF into individual files?
Yes, and these are two complementary operations on the same parsed contact set. Merge: combines a folder of single-contact VCF files (the way iPhone exports look by default: one VCF per contact) into a single multi-contact VCF or any other output format. Useful when a destination platform expects a single file. Split: takes a single multi-contact VCF (the way Outlook or Google Contacts exports look) and produces one VCF per contact named after the FN field. Useful when a destination platform expects one file per record. The same parser-output pipeline handles both directions; the difference is whether the writer aggregates or separates the parsed records.
Can the converter upgrade my old vCard 2.1 file to vCard 3.0 or 4.0?
Yes. Selecting vCard as the output format opens a version picker (2.1, 3.0, 4.0). The conversion reads the source records, normalizes the field set to the target version's rules, and writes the output with the requested VERSION line. Practical considerations: vCard 4.0 introduces new properties (KIND, GENDER, LANG) that older versions do not have, and the converter writes these only where the source data supplies them. vCard 2.1 has restrictions that 3.0 and 4.0 do not (limited Unicode handling, shorter property name set), so upgrading from 2.1 generally produces richer output. Downgrading from 4.0 to 2.1 will drop properties that 2.1 cannot represent; the diagnostic log lists exactly which fields were lost in any downgrade conversion.
Customer Stories
Customer Conversion Reports
Three customer reports below from people who ran real vCard conversions. Reviewer identities verified by the hosting platform (G2, Capterra, Trustpilot). Selection covers representative scenarios: individual address book cleanup, single-VCF cross-platform conversion, and bulk conversion to a cloud address book.
G2 Reviews
4.6
230 reviews
Capterra
4.5
280 reviews
Trustpilot
4.7
185 reviews
Not the most technical user, but the vCard converter was straightforward to figure out. The trial confirmed it worked for the contacts I wanted to convert, and support answered my questions when I got stuck. The end result: a cleaned-up contact list that I could share across my devices without the duplicate-contact problem I had been living with.
ThomasSales Operations, California, USA
A coworker handed me a VCF file and I needed it in a format that worked across my devices (Mac at work, Windows at home, phone for on-the-go). Found this VCF converter via search, ran it once on a sample to verify the contacts came through correctly, then converted the full file in under a minute. The output worked across all three platforms with no further changes.
SmithIT Support Engineer, Sydney, Australia
The migration: a folder of accumulated VCF files (thousands of contacts gathered over years) needed to land in Google Contacts as live records, not as another file. Most converters I tried wrote a CSV that I would still have to import manually. PCDOTS handled the OAuth authentication against Google directly and wrote the contacts straight into the destination address book in a single run.
RoyCRM Consultant, Drammen, Norway
Explore More
Related Products and Resources
Other PCDOTS tools that pair with the vCard Converter for complete contact and email migration workflows. Browse the full software catalog for every available converter.
Run the vCard Converter on Your VCF Files. Trial Edition, No Card Required.
The way to evaluate any vCard tool is to point it at a real VCF file from your environment and see what comes out. Download the trial, run it on a representative address book, verify the output looks the way you expect. Upgrade to the licensed edition only after the trial confirms the conversion does what you need.
