VCF import errors: iCloud, Google Contacts, and Outlook
vCard importers are inconsistent. A .vcf file can look normal in a text editor and still fail in iCloud, Google Contacts, Outlook, Android, iOS, or a CRM.
If you want the fastest path to a clean, import-ready file, use CorrectVCF:
Common causes
Most failed imports come from one of these categories:
- hidden encoding problems or unexpected bytes at the start of the file
- missing or malformed contact boundaries
- missing display-name fields
- multi-contact files that a target app cannot handle reliably
- wrapped lines or long fields that the importer reads incorrectly
- address, phone, email, date, or photo fields exported in a format the target app does not expect
Symptoms by app
Google Contacts may reject the file, skip blank contacts, or drop fields. Outlook may import only one contact from a larger file. iCloud and iPhone imports may fail silently or appear to do nothing.
When that happens, do not keep retrying the same file. Validate it first, repair structural blockers, then import the cleaned version.
Repair path
- Keep a backup of the original
.vcf. - Validate the file before importing again.
- Repair structural and encoding blockers.
- Retry the cleaned file in the destination app.
- Verify the final contact count and a few representative records.
CorrectVCF checks the file, identifies the import blockers, and generates a cleaned .vcf when safe repairs are available.
Upload the broken VCF and get a cleaned file back
Developer docs
Detailed field-format notes, mapping examples, and developer-oriented export guidance are kept in authenticated Developer documentation:
Fix your .vcf file in seconds
Upload a vCard and get a clean, import-ready file for Google Contacts, Outlook, iPhone, Android, and CRMs.