vCard vs CSV vs Google Contacts CSV: Which Format for Your Contacts?
· 3 min read · By the BizCardPro.AI team
Every contact tool eventually asks the same question: export as what? Pick wrong and you get phone numbers stripped of their + signs, photos lost, or an import screen demanding you map “Column F” to something. Pick right and the data flows through untouched. Here’s the whole decision in one guide.
What is a vCard (.vcf), exactly?
The vCard is the universal contact card format — a small text file that carries one person (or many) with typed, structured fields: name parts, organization, title, phone numbers with their types (mobile/work/fax), emails, addresses, URLs and even an embedded photo.
Its superpower is that every contacts app on earth opens it natively: tap a .vcf on iPhone or Android and the new-contact screen appears pre-filled. That’s why it powers every “Save contact” button on digital business cards.
Use vCard when the destination is a contacts app: sending a colleague someone’s details, importing a batch into your phone, or keeping a faithful backup.
What is CSV good for?
CSV — comma-separated values — is a table: one row per contact, one column per field. It’s the lingua franca of spreadsheets and CRMs. Anything that displays data in rows wants CSV.
Its weakness is that CSV has no standard for contact semantics. One tool writes Name, another
writes First Name/Last Name, a third writes 名前. Import screens exist to bridge that gap by
hand. Two rules keep CSV painless:
- Split fields beat blobs. A CSV with separate family-name, given-name, native-script and romanized columns (what BizCardPro.AI’s spreadsheet export writes — 14 columns) sorts, filters and mail-merges cleanly. A single “Name” column doesn’t.
- Import, don’t double-click. Open CSVs in Excel via Data → From Text/CSV and mark phone columns as Text, or leading + signs and zeros can be eaten. Numbers stored in E.164 format survive best.
Use CSV when the destination is a spreadsheet, a CRM import, or a human who wants to scan a table.
What makes Google Contacts CSV different?
It’s still CSV — but with Google’s exact column schema: Given Name, Family Name,
Organization 1 - Name, Phone 1 - Type, Phone 1 - Value, and so on. Upload it at
contacts.google.com → Import and every field lands in the right place with no mapping screen,
then syncs to Gmail autocomplete and Android automatically.
If Google Contacts is your team’s address book, this format removes the one error-prone step from the pipeline. (Full walkthrough: scanning cards into Excel and Google Contacts.)
The decision table
| Destination | Format | Why |
|---|---|---|
| iPhone / Android contacts | vCard (.vcf) | Opens natively, keeps photos and phone types |
| A colleague (“send me his details”) | vCard | One tap to save on any phone |
| Excel / Google Sheets / Numbers | Spreadsheet CSV | Rows and columns, sortable, mail-merge ready |
| CRM import (HubSpot, Salesforce…) | Spreadsheet CSV | CRMs map CSV columns; split fields import cleanly |
| Google Contacts | Google Contacts CSV | Zero-guesswork field mapping, instant sync |
| Long-term backup | vCard (+ CSV) | vCard is lossless for contact data; CSV adds human readability |
The deeper principle: never get locked in
Formats are only half the story — the other half is whether your tools let the data out. A contact archive you can’t export in open formats isn’t yours; it’s rented. That’s why every BizCardPro.AI plan, including the free one, exports all three formats plus your original card images: the test of a good scanner is that leaving it would be easy.
Scan a few real cards, export them each way, and open the files — the whole experiment takes five minutes and costs nothing.
Frequently asked questions
Is vCard or CSV better for backing up contacts?
vCard preserves more (photos, typed phone numbers, multiple emails per person) and re-imports perfectly into contacts apps, making it the better backup. CSV is better when a human or a spreadsheet needs to read the data. Exporting both costs nothing.
Why did my CSV import map fields wrongly in Google Contacts?
Generic CSVs use arbitrary column names that Google has to guess at. A Google Contacts CSV uses Google’s own column schema (Given Name, Family Name, Phone 1 - Type…), so the import maps every field without guesswork.
Can Excel open a vCard file?
Not usefully — vCard is a card-per-record text format, not a table. If the destination is Excel or Google Sheets, export CSV instead; if the destination is a contacts app, use the vCard.
What happens to Chinese or Japanese names in these formats?
All three formats carry Unicode fine. The real question is whether your scanner exported both the native script and the romanization as separate fields — if it did, both survive round-trips through vCard and CSV.
Keep reading
· 3 min read
How Accurate Are AI Business Card Scanners? (And How to Verify)
What accuracy really means for business card scanning: where AI extraction fails, why per-card confidence scores matter more than headline percentages, and a 2-minute verification workflow.
Read the guide →· 3 min read
How to Scan Korean Business Cards (명함) with AI
Digitize Korean myeongham accurately: hangul extraction with romanization, family-name-first handling, titles that matter, and a step-by-step batch workflow.
Read the guide →· 4 min read
Best Business Card Scanner Apps in 2026 (an Honest Comparison)
Seven business card scanner apps compared for 2026: multilingual accuracy, exports, digital cards and pricing models — including where each one genuinely wins.
Read the guide →