How to fix “the file you're importing isn't formatted for Contacts”
This means the contacts service could not read the file as a valid vCard or CSV. Usually the file is the wrong type, has a broken structure, or uses the wrong encoding. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~7 min Updated Jun 2026 92% found this helpful
Error message
The file you're importing isn't formatted for Contacts. Make sure the file is a CSV or vCard.
Summary
Google Contacts shows this when it cannot read your file as a valid vCard or CSV. The usual causes are that the file is not actually a .vcf or .csv (for example a renamed or wrong-type file, or an Excel workbook), that the vCard structure is broken with mismatched BEGIN:VCARD and END:VCARD tags or a missing FN field, that the encoding is not UTF-8, or that a CSV has columns the importer does not recognise. A file truncated during download or email transfer triggers it too. The fix is to confirm the file really is a clean vCard or CSV, repair the structure, save it as UTF-8, and where possible re-export it from the source rather than hand-editing. For CSV, exporting in the destination's own template format is the most reliable path.
What this error means
A contacts importer accepts two formats: vCard (.vcf), a text format that starts each contact with BEGIN:VCARD, and CSV (.csv), a comma-separated table with a header row. When the file does not match either format closely enough, the importer cannot parse it and reports that the file is not formatted for Contacts.
So this is a format and structure problem, not a problem with the individual contacts. A file with the wrong extension, a broken vCard skeleton, an unrecognised CSV layout, or a non-UTF-8 encoding will all be rejected the same way. Getting the file into a clean, standard vCard or CSV resolves it.
Common causes
The file is not actually a vCard or CSV, for example a renamed or Excel file.
vCard BEGIN:VCARD and END:VCARD tags are mismatched or missing.
A contact is missing a required FN or N field.
The file is not saved in UTF-8.
A CSV has a header or columns the importer does not recognise.
The file was truncated during download or email transfer.
The file was saved in an app-specific format rather than plain vCard or CSV.
Expert insight
“This error is the importer saying I do not even recognise this as a contacts file. The first thing I do is open it in a text editor, because a real vCard literally starts with BEGIN:VCARD and a CSV has a clear header row. If it is neither, someone renamed an Excel file or exported the wrong thing. If it is a vCard but broken, I check the BEGIN and END tags line up and every contact has an FN. And honestly, the cleanest fix is almost always to re-export from the source app rather than wrestle with a half-broken file.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Confirm the file is really vCard or CSV
1Open the file in a plain-text editor. A vCard starts each contact with BEGIN:VCARD; a CSV has a header row of column names.
2If it is an Excel workbook or some other format, export or save it as a proper .vcf or .csv first.
3Make sure the extension matches the actual content.
Method 2
Fix the vCard structure
1Each contact must open with BEGIN:VCARD and close with END:VCARD, with matching counts.
2Every contact needs an FN (formatted name) line, and wrapped lines need a leading space (RFC folding).
3Add a missing END:VCARD, often the file was truncated at the end.
Method 3
Fix a CSV layout
1For CSV, export from the source in the destination's own format, for example Google CSV.
2If you must build it, match the importer's expected column headers and use commas, not semicolons.
3Remove blank rows and stray columns.
Method 4
Save the file as UTF-8
1Re-save the file as UTF-8 so non-ASCII names and fields are read correctly.
2If names look garbled, follow the garbled-characters fix first.
3Avoid a byte order mark for the widest compatibility.
Method 5
Re-export from the source app
1Rather than repairing a broken file by hand, export the contacts again from the original app or account.
2Choose vCard 3.0 or the destination's CSV template.
3A clean export rebuilds the structure correctly.
Method 6
Re-download and retry
1If the file may have been cut off during download or email, get a fresh copy.
2Confirm the last line is a complete END:VCARD or a full CSV row.
3Import the complete file.
This is a format problem, so check the file type first, before the contents. Open it in a text editor: a real vCard starts with BEGIN:VCARD and a CSV has a header row. The most reliable fix is to re-export cleanly from the source as vCard 3.0 or the destination's own CSV template, rather than patching a malformed file.
Frequently asked questions
What does “not formatted for Contacts” mean?
The importer could not read your file as a valid vCard or CSV. The file is the wrong type, has a broken structure, or uses an encoding the importer cannot parse.
How do I know if my file is a real vCard?
Open it in a text editor. A vCard starts each contact with BEGIN:VCARD and ends it with END:VCARD. If you do not see those, it is not a valid vCard.
Why is my Excel or numbers file rejected?
Those are not CSV or vCard. Export or save the data as a proper .csv or .vcf file, then import that instead.
My CSV is rejected, what is wrong?
The columns or header may not match what the importer expects, or it may use semicolons instead of commas. Export in the destination's CSV template, or align the headers and use commas.
Could a broken download cause this?
Yes. A file cut off during download or email transfer is missing its final END:VCARD or last CSV row. Re-download a complete copy and import again.
What is the most reliable fix?
Re-export the contacts cleanly from the source app or account as vCard 3.0 or the destination's CSV format, which rebuilds a valid structure automatically.
Still not working?
If a re-exported, UTF-8 vCard or CSV is still rejected, open it in a contact tool or validator to catch a structural fault you cannot see in a text editor, such as an invisible character or a stray byte order mark. Converting the file through a dedicated vCard or CSV tool usually produces an import-ready result. You can also submit your error to us for a tailored fix.
