Why won't my .vcf import on iPhone?

The import workflow may be wrong for the app, or the VCF may have formatting, encoding, or record-boundary problems. Follow Apple's import steps first, then validate the file if it is rejected or imports incompletely.

Does iPhone Contacts support vCard 4.0?

iOS generally supports vCard 3.0 and 4.0, but exporters and importers vary; compatibility issues are usually about formatting and encoding rather than the version number alone.

What’s the fastest way to fix iPhone vCard import errors?

If the file is rejected or contacts are missing after using the supported import steps, validate it, repair supported file issues, and retry. Validation cannot fix an unsupported app workflow.

VCF won’t import on iPhone / iOS Contacts — how to fix

First: import instructions or file failure?

You need to import a valid VCF: Follow Apple’s instructions for importing contacts on iPhone or the CorrectVCF Apple Contacts help hub for iCloud and Mac paths. An unfamiliar opening method does not mean the file is corrupt.
You followed the import steps, but the file is rejected or contacts are missing: Check the VCF for structural and formatting problems. CorrectVCF can identify issues such as broken contact boundaries or malformed fields and repair supported file problems before you retry.
Only one contact imports: Use the one-contact diagnostic to check the number of records and whether the same file works in another app.

If a valid file works elsewhere but the Apple import route still fails, check the destination app’s instructions and limitations. File repair cannot fix permissions, file location, or an unsupported workflow.

1) Quick checks

Make sure the filename ends in .vcf
Open it in a text editor and confirm you see BEGIN:VCARD / END:VCARD
Confirm each contact has VERSION, FN, and N

2) iCloud’s “invisible character” problems (encoding/BOM)

Some exporters add hidden bytes at the start of the file (like a UTF‑8 BOM). Some iCloud flows are sensitive to this and will reject the file.

If you exported from a tool you don’t control (or concatenated multiple files), validation can help determine whether encoding is part of the file problem.

3) Record boundary problems (multi-contact files)

A multi-contact .vcf should look like a sequence of records:

BEGIN:VCARD
...
END:VCARD
BEGIN:VCARD
...
END:VCARD

If there’s an END:VCARD missing, an importer may reject the file or stop before all contacts are added.

4) Line folding (long properties)

iOS importers can be strict about RFC folding rules. If a line wraps without the required leading space on the continuation line, the whole record can fail.

Recommended workflow

Follow the supported iPhone or iCloud import steps for the app you are using.
If the VCF is rejected or incomplete, validate it and inspect any reported file issues.
Repair supported structural or encoding problems, then retry the import.

Check this contact file

If validation finds a repairable file issue, CorrectVCF can provide a corrected .vcf to try again. If the file checks out, return to the app’s import instructions.

Fix your .vcf file in seconds

Upload a vCard and get a clean, import-ready file for Google Contacts, Outlook, iPhone, Android, and CRMs.

Try the CorrectVCF Autofix Tool Back to Help