Overview
Introduction
Exporting contacts from a phone or email client usually produces a .vcf file full of vCard blocks, not a spreadsheet. This tool extracts the common fields out of every vCard block into CSV rows.
It handles a file with many concatenated vCards at once, producing a full contacts spreadsheet rather than requiring you to process one contact at a time.
What Is vCard to CSV Converter?
A vCard-to-CSV converter that scans for every BEGIN:VCARD...END:VCARD block in the input and extracts the FN, EMAIL, TEL, ORG, and TITLE properties from each into a fixed five-column CSV row.
It's the reverse of CSV to vCard Converter, reading back the same five fields that tool writes out.
How vCard to CSV Converter Works
The input text is scanned with a pattern that matches every BEGIN:VCARD...END:VCARD block, however many are concatenated together in the file.
Within each block, every `PROPERTY:value` line is read; if the property (ignoring any parameters after a semicolon) matches FN, EMAIL, TEL, ORG, or TITLE, its unescaped value fills the corresponding CSV column for that contact's row.
When To Use vCard to CSV Converter
Use it when you've exported contacts as a .vcf file and need them in a spreadsheet for bulk editing, filtering, or import into another system that expects CSV.
It's also useful for quickly auditing how many contacts, and which core fields, a vCard export actually contains.
Often used alongside CSV to vCard Converter, JSON Lines (JSONL) to CSV Converter and SQL INSERT to CSV Converter.
Features
Advantages
- Processes a file containing many concatenated vCards in a single pass, producing one row per contact.
- Unescapes vCard's backslash-escaped special characters back into plain text automatically.
- Runs entirely client-side, so contact data never leaves your browser.
Limitations
- Only five fields (name, email, phone, organization, title) are extracted; everything else in the vCard (address, birthday, photo, notes, custom X- properties) is ignored.
- If a vCard has multiple lines for the same property (e.g. two EMAIL lines), only the last one is kept in the CSV.
Examples
Best Practices & Notes
Best Practices
- Check the row count against the number of contacts you expect; a malformed or truncated vCard block simply won't match and gets skipped.
- If a field you need isn't showing up, confirm the vCard actually uses one of the five recognized property names (FN, EMAIL, TEL, ORG, TITLE).
- Use CSV to vCard Converter afterward to verify a round trip reproduces the same contact data.
Developer Notes
Property matching strips any parameters after a semicolon (e.g. `TEL;TYPE=CELL:...` still matches TEL) before comparing against the recognized property names, since real-world vCard exports frequently attach type/encoding parameters that shouldn't prevent the base property from being recognized.
vCard to CSV Converter Use Cases
- Converting a phone or email client's contact export (.vcf) into a spreadsheet
- Bulk-editing or filtering contact data after pulling it out of vCard format
- Auditing a vCard export for missing or incomplete contact fields
Common Mistakes
- Expecting fields beyond the five recognized ones (address, birthday, notes) to appear in the CSV; they're intentionally not extracted.
- Assuming every EMAIL or TEL line survives when a contact has more than one; only the last matching line per property is kept.
Tips
- If a contact's row looks incomplete, open the raw .vcf and confirm the property names match FN/EMAIL/TEL/ORG/TITLE exactly (ignoring any ;TYPE= parameters).
- Pair with CSV to vCard Converter to check that converting back and forth doesn't lose the fields you care about.