Why does my vCard (.vcf) import fail?

Common causes include encoding problems, malformed contact records, missing required name fields, broken line wrapping, or client-specific import quirks.

Why does Outlook import only one contact from a multi-contact VCF?

Many Outlook flows are unreliable with multi-contact vCards. The file may need validation, normalization, splitting, or conversion before bulk import.

What is the fastest way to fix a .vcf import error?

Validate the file, repair the first import blocker, and retry with a cleaned .vcf.

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:

Fix VCF import errors

Find the guide for your specific VCF error

Identify your specific symptom below to jump to the detailed guide:

1) File structure and syntax errors

File will not open on any device: If your .vcf file fails everywhere or shows “file corrupted”, see VCF File Won’t Open? How to Fix.
Missing BEGIN:VCARD or END:VCARD: If your file is missing required wrapper markers or has syntax errors, see Invalid vCard: Missing BEGIN:VCARD / END:VCARD.
Only one contact imports: If your file contains hundreds of contacts but your app imports only the first one, see VCF Only Imports One Contact.
Duplicate contacts created: If re-importing created duplicate entries, see Fix Duplicate Contacts After VCF Import.

2) Platform-specific import failures

Google Contacts & Gmail: If Google Contacts rejects your file or drops fields, see VCF Won’t Import into Google Contacts.
iPhone, iPad & iOS Contacts: If iOS Mail or Files app won’t open your contact file, see VCF Won’t Import on iPhone / iOS Contacts or visit the Apple Contacts & iCloud Help Hub.
iCloud Web UTF-8 BOM: If iCloud web rejects your file due to hidden byte order marks, see iCloud vCard Import UTF-8 BOM Fix.
Outlook & Microsoft 365: If Outlook Desktop or Outlook.com fails to import your vCard, see Outlook VCF Import Issues, How to Import VCF Files into Outlook, or visit the Outlook VCF Help Hub.

Common root causes overview

Most failed VCF imports stem from a few predictable categories:

Hidden encoding problems: Non-UTF-8 encodings (Windows-1252, UTF-16) or byte order marks (BOM) at the start of the file that break strict web parsers like iCloud.
Missing required fields: Missing VERSION tags (e.g., VERSION:3.0), display names (FN), or structured names (N).
Line folding errors: Long property lines wrapped without the required leading space on continuation lines.
Multi-contact truncation: Missing END:VCARD markers between records causing importers to stop parsing at the first error.

Recommended repair workflow

Keep a backup copy of your original .vcf file.
Upload the file to the CorrectVCF Autofix Tool.
Review the diagnostic report to identify structural blockers.
Download the cleaned, import-ready .vcf file and retry your import.

For software engineers exporting vCard files from custom applications, see our Quick Checklist for Developers and Developer API 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.

Try the CorrectVCF Autofix Tool Back to Help