CorrectVCF

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. The error message is a starting point, not proof that the file is broken.

If the file itself may be malformed, check it with CorrectVCF:

Check this VCF for import-blocking file problems

“This vCard cannot be imported because it contains invalid contact data”

This message is a general import rejection, not a diagnosis of one specific field. The importer may have found malformed vCard structure, an invalid or unsupported property, damaged text encoding, missing BEGIN:VCARD or END:VCARD boundaries, or data that its own contact format cannot accept.

Start with the structural guides below—especially VCF File Won’t Open? How to Fix and Missing BEGIN:VCARD / END:VCARD—then use the relevant platform guide if the file works elsewhere. To identify the first concrete blocker instead of guessing from the generic message, check the VCF file.

“Couldn’t import vCard” or “format not supported”

These messages may mean the app cannot parse the VCF, but they can also mean that its version, file location, or import workflow is unsupported. If the file fails in more than one app, validate its structure and formatting. If it works elsewhere, follow the destination-specific iPhone/iCloud, Google Contacts, or Outlook guidance before trying a repair.

Partial import or contacts missing after import

First confirm that the source VCF actually contains the missing contacts. If only the first contact imports, use the one-contact guide to check both the file and the app’s multi-contact support. If contacts or fields are missing from several apps, check the file for malformed records. If just one app drops them, consult its platform guide; a repaired file cannot force an importer to support fields or workflows it lacks.

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

2) Platform-specific import failures

Common root causes overview

Most failed VCF imports stem from a few predictable categories:

  1. 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.
  2. Missing required fields: Missing VERSION tags (e.g., VERSION:3.0), display names (FN), or structured names (N).
  3. Line folding errors: Long property lines wrapped without the required leading space on continuation lines.
  4. Multi-contact truncation: Broken record boundaries can stop an import early; some apps also limit how they import otherwise valid multi-contact files.
  1. Keep a backup copy of your original .vcf file.
  2. If the file may be malformed, validate it with CorrectVCF.
  3. Review any structural or formatting problems and repair supported issues where applicable.
  4. Retry with the corrected .vcf. If the file checks out, follow the destination app’s import instructions instead.

For software engineers exporting vCard files from custom applications, see our Quick Checklist for Developers and Developer API Documentation.

Related help articles

Apple Contacts & iCloud VCF Help Hub Guides for iPhone, iPad, Mac, and iCloud vCard imports. Outlook VCF Help Hub Guides for Outlook Desktop, Outlook.com, and Windows People app. VCF File Won't Open? Fix vCard Errors Troubleshoot unopenable VCF files and structural corruption. Invalid vCard: Missing BEGIN/END Markers Fix record wrapper syntax and line ending errors.

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