VCF to CSV / XLSX / TXT
Convert phone vCard (.vcf) contacts into Excel/CSV/Text — 100% private client-side processing.
Active Converter
VCF to Excel / CSV / TXT: Decoding vCard 2.1, 3.0 & 4.0 Contacts with UTF-8 BOM Fix
Technical Anatomy of vCard (.VCF) Files
The vCard format (.vcf), standardized across versions 2.1, 3.0 (RFC 2426), and 4.0 (RFC 6350), is the universal interchange envelope for smartphone address books. Each contact is enclosed between BEGIN:VCARD and END:VCARD delimiters and composed of key-value property lines such as FN (Formatted Name), N (Structured Surname;GivenName), TEL;TYPE=CELL, EMAIL;TYPE=INTERNET, and ORG.
Real-world phone exports are rarely clean: iOS iCloud exports fold long lines across 75-octet boundaries using leading spaces (CRLF + SPACE), while Samsung and Xiaomi Android devices frequently emit vCard 2.1 blocks with ENCODING=QUOTED-PRINTABLE hex escapes for Arabic, Chinese, or accented European characters. Our parser unfolds wrapped lines, normalizes property parameters, and maps every contact record into clean tabular columns ready for Excel (.xlsx) or UTF-8 BOM .csv.
Raw vCard 3.0 Input vs. Clean Spreadsheet Output
# Input: iPhone / Android Contact Export (contacts.vcf)
BEGIN:VCARD
VERSION:3.0
FN:Ahmed El-Mansouri
ORG:Atlas Logistics SARL
TEL;TYPE=CELL:+212661002233
EMAIL;TYPE=WORK:ahmed@atlaslogistics.ma
END:VCARD
# Converted Excel / CSV Output (with UTF-8 BOM for Arabic/Unicode):
Name,Phone,Email,Organization
"Ahmed El-Mansouri","+212661002233","ahmed@atlaslogistics.ma","Atlas Logistics SARL"
Real-World Software & Hardware Ecosystem
Sales teams, recruiters, and smartphone users export .vcf backups from Apple iCloud Contacts, Google Contacts, Samsung Smart Switch, Microsoft Outlook, and WhatsApp Business, then convert them to Excel or CSV for import into HubSpot, Salesforce, Zoho CRM, Mailchimp, or bulk SMS gateways.
Troubleshooting & Edge Cases
- Arabic & Unicode Garbling in Excel: Always leave Fix Arabic/Unicode Excel Encoding (UTF-8 BOM) checked. Without the 3-byte BOM header, Excel misreads UTF-8 Arabic names as Windows-1252 gibberish.
- Leading Zeros & Plus Signs Stripped from Phone Numbers: When opening raw CSV in Excel, numbers like
+212661002233can turn into2.12661E+11. Export directly to native.XLSXso SheetJS preserves phone strings cleanly without scientific notation. - Embedded Base64 Contact Photos: iPhone vCards sometimes embed multi-kilobyte
PHOTO;ENCODING=b;TYPE=JPEG:...blobs. Our parser skips binary photo payloads so your Excel sheet stays lightweight and fast.
vCard Version Comparison: 2.1 vs. 3.0 vs. 4.0
| Specification | vCard 2.1 (Android Legacy) | vCard 3.0 (iOS / RFC 2426) | vCard 4.0 (RFC 6350) |
|---|---|---|---|
| Character Encoding | Per-property CHARSET=UTF-8 + Quoted-Printable |
File-level UTF-8 (folded at 75 octets) | Mandatory UTF-8 only |
| Phone Property Syntax | TEL;CELL:+212... |
TEL;TYPE=CELL:+212... |
TEL;VALUE=uri:tel:+212... |
| Primary Generators | Samsung Smart Switch, Xiaomi, Huawei | Apple iCloud, Google Contacts, Outlook | Nextcloud, Fastmail, Thunderbird |
Step-by-Step CRM & WhatsApp Migration Workflow
- Export Your Master Address Book: On iPhone, visit iCloud.com → Contacts → Select All → Export vCard. On Android, open Google Contacts → Fix & Manage → Export to .vcf file.
- Verify UTF-8 BOM Encoding for Arabic/Multilingual Names: Before clicking convert, keep UTF-8 BOM (Arabic/Excel Fix) active. This writes bytes
0xEF 0xBB 0xBFat byte zero of the CSV so Microsoft Excel on Windows never mangles Arabic, French, or Cyrillic letters into Windows-1252 mojibake. - Clean Duplicate or Blank Entries in Interactive Table Mode: Switch the preview pane from Text to Table. Search for contacts missing phone numbers or drop unused columns such as
Organizationby clicking the×button on the header. - Export Native .XLSX for Scientific-Notation Protection: When importing into HubSpot, Salesforce, or WhatsApp Business API tools, prefer
.XLSXover raw CSV so international numbers like+966501234567remain exact text strings rather than turning into9.66501E+11.
Command-Line Verification Equivalent (Python / Shell)
# Verify UTF-8 BOM bytes on exported CSV in Linux/macOS terminal:
head -c 3 contacts.csv | xxd
# Expected output: 00000000: efbb bf ...
Deduplicating Multi-Device Phonebooks Before CRM Import
Users who sync contacts across an iPhone, an Android work handset, and Microsoft Outlook frequently end up with duplicate cards—one storing +212 661-002233 and another storing 0661002233. After converting your merged .vcf archive to Excel, add a helper normalization column using =SUBSTITUTE(SUBSTITUTE(SUBSTITUTE(B2," ",""),"-",""),"+",""), then run Excel's Data → Remove Duplicates on the normalized phone column. You can then push the deduplicated sheet straight back into our CSV-to-VCF converter to build one pristine master address book for every device.
Frequently Asked Questions
Microsoft Excel defaults to legacy ANSI/Windows-1252 encoding when double-clicking a plain UTF-8 CSV file. Prepending the 3-byte UTF-8 Byte Order Mark (0xEF 0xBB 0xBF) via our Smart Auto-Fix toggle forces Excel to decode Arabic and international Unicode names properly.
Older Android and Samsung phone exports encode non-ASCII names using CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE. The parser unfolds soft line breaks (=\r\n), converts every =XX hex escape back into raw bytes, and decodes the resulting UTF-8 sequence into crisp readable text.
Yes. Multi-contact vCard archives concatenate thousands of BEGIN:VCARD ... END:VCARD blocks inside one file. The parser splits every contact card cleanly into its own spreadsheet row with Name, Phone, Email, and Organization columns.
Yes. Switch the right-hand preview from Text to Table view, search or filter rows, click the × button on any unwanted column header, and export the cleaned contact sheet straight to .XLSX.