vCard ⇆ CSV converter

Phone and email contact exports commonly come as .vcf (vCard) files — one contact per entry, with fields like name, phone numbers, email addresses, and organization packed into a structured but not especially readable text format. This tool converts a .vcf file, whether it holds one contact or several thousand, into a clean CSV with each contact as a row and each field (name, phone, email, address, company) as its own column.

A contact export is a personal data file almost by definition — full names, phone numbers, home and work addresses, sometimes birthdays, for potentially hundreds or thousands of people who never agreed to have their information run through a third-party server. Converting it locally means that entire contact list stays in your browser through the whole process, with nothing transmitted anywhere to produce the CSV.

Upload your .vcf file — exported from a phone’s contacts app, an email client, or a CRM’s contact export feature — and the tool parses each vCard entry, mapping standard fields (name, phone numbers, emails, organization, address) into consistent CSV columns. Contacts with multiple phone numbers or email addresses are split into separate columns (phone 1, phone 2, and so on) rather than being combined into one messy field, and any custom or non-standard fields present in the vCard are preserved as additional columns rather than silently dropped.

FAQ

Why do some contacts have more populated columns than others?

This just reflects what was actually filled in for each contact originally — a vCard only includes the fields that existed for that person, so a contact with just a name and phone number will naturally have more blank columns in the CSV than one with a full set of details.

Does this handle vCard files with hundreds or thousands of contacts, not just a few?

Yes — a full phone contacts export or CRM database dump in .vcf format converts the same way as a single-contact file, just with more rows in the resulting CSV.

What happens to a contact’s photo if the vCard includes one?

Embedded photos are typically encoded as base64 data within the vCard file — the converter can either skip these (keeping the CSV clean and text-only) or include the raw encoded data in a column, depending on whether you actually need the image data preserved in the output.

Can I convert the CSV back into vCard format later if I need to re-import it somewhere?

This tool handles the vCard-to-CSV direction; if you need to go back to .vcf after editing the CSV, most contact management apps can re-import a correctly formatted CSV directly without needing an intermediate vCard conversion step.

If your CSV export ends up needing deduplication — common with contact lists merged from multiple sources — the Fuzzy Duplicate Row Matcher catches near-duplicate entries that an exact match would miss, like the same person saved under slightly different name spellings.