VCF to CSV Converter
Drop a VCF export from your phone or address book — get a clean CSV ready for import into any CRM, spreadsheet, or email tool.
Drop your VCF file here
Converts to .csv — stays on your device
Why convert VCF to CSV?
- Importing an iPhone contacts export (Contacts.app → Export → vCard) into HubSpot, Salesforce, Pipedrive, or Zoho CRM.
- Moving a Gmail contacts VCF download into a Mailchimp, ConvertKit, or Klaviyo subscriber list where CSV is the required format.
- Migrating from iCloud Contacts to a new CRM during a job change, where the new platform only accepts CSV bulk imports.
- Preparing a team's shared VCF address book for a Google Sheets deduplication pass before re-importing into a new tool.
- Converting Outlook or macOS Contacts exports into a format that a BI tool (Airtable, Notion databases) can accept.
- Archiving a contacts backup from an old phone as a flat CSV for long-term storage where VCF's evolving spec matters less.
How our converter works
Your VCF file is parsed — every BEGIN:VCARD/END:VCARD block becomes a row. Standard fields (FN, N, TEL, EMAIL, ORG, TITLE, ADR, NOTE) map to columns matching the Google Contacts CSV schema, which imports cleanly into virtually every CRM and email platform. Multi-value fields (mobile phone vs work phone, personal vs work email) are separated into their own columns. Everything runs locally — your address book, including personal contacts mixed with professional ones, never leaves your device.
VCF vs CSV — what's the difference?
| Feature | VCF | CSV |
|---|---|---|
| Structure | One block per contact | One row per contact |
| Field richness | vCard spec is huge — photos, types, custom fields | Whatever columns you define |
| CRM imports | Some platforms, usually one-at-a-time | Universal — every CRM accepts CSV |
| Editing | Specialized tools or manual text editing | Any spreadsheet |
| Best for | Phone transfers, single-contact sharing | Bulk operations, CRM imports, deduplication |
Frequently asked questions
Which CSV columns are in the output?
Eleven: Name, First Name, Last Name, Mobile Phone, Work Phone, Email, Work Email, Organization, Title, Address, Notes. That matches Google Contacts' schema and imports cleanly into HubSpot, Salesforce, Mailchimp, and most other CRMs.
Will profile photos survive?
No. CSV doesn't carry binary data. Embedded photos in the VCF are dropped. If you need photos, keep the VCF as your master.
What if my VCF contains 500 contacts in one file?
Handled. The converter parses multi-card VCFs natively — each BEGIN:VCARD block becomes its own CSV row. Large address books (thousands of contacts) convert in a few seconds.
Does the order of fields in the VCF matter?
No. Properties can appear in any order within a vCard; the parser looks up each field by name (FN, TEL, EMAIL, etc.) rather than position.
What about custom labels like TEL;TYPE=HOME;TYPE=VOICE?
Recognized when they include CELL, MOBILE, or WORK. Other combinations fall into the default Phone / Email columns. For completely custom field labels, a manual CSV clean-up after conversion is the reliable path.
Are my contacts uploaded?
No. The conversion runs entirely in your browser. Address books are sensitive — they stay on your device, always.
About the VCF format
VCF (vCard, RFC 6350) is the universal electronic business-card format — the standard phones, email clients, and contact apps use to share a single contact or an entire address book. A VCF file is human-readable text: each contact is a BEGIN:VCARD/END:VCARD block with properties like FN (full name), TEL (phone), EMAIL, ADR (address). It's excellent for phone-to-phone transfers and single-contact sharing. CSV is the opposite: a flat tabular format with no nesting or types, universally supported by every spreadsheet, CRM, and bulk-operations tool. The VCF→CSV conversion is the bridge from 'I've got a phone address book' to 'I need to import 200 contacts into HubSpot' — the most common reason people reach for a contact converter at all.