01
Upload your file
Drop your .vcf into the fixer at /fix. Validation is free, so you can see what is wrong first.
Fix vCard import errors and download a repaired .vcf
VCF import failing? Check the file and fix supported problems.
CorrectVCF checks contact files for import-blocking problems and repairs supported issues. Validate your .vcf first, then choose a one-time repair if the file needs it.
Ordinary validation processed in memory Checks files for Outlook, Apple & Google imports One-time fix available — no subscription
Does this sound familiar?
Start with your symptom to see whether the file needs repair or the destination app needs a different import method.
🟦 Google Contacts
VCF won't import into Google Contacts
File uploads but contacts do not appear, or Google rejects it with a vague error.
🟪 Outlook
Outlook VCF import fails or is incomplete
Only some contacts import, or Outlook rejects the file. Check whether the file or the import workflow is responsible.
🍎 iPhone / iCloud
iPhone won't open the .vcf file
iOS says the file is invalid, or it opens but nothing gets added to Contacts.
1️⃣ Multi-contact
Only one contact imports instead of all
Check whether the file has multiple valid records or the importer handles only one at a time.
☁️ iCloud
iCloud rejects the vCard because of encoding
A hidden byte-order mark or encoding mismatch can trigger silent failures in stricter importers.
📂 General
The file won't open on any platform
Check for structural problems, then rule out a device or app import issue.
How it works
02
We find the problems
Validation checks vCard structure and supported issues that can block contact imports.
03
Download a fixed file
If the file has a supported repair, download a corrected .vcf. The one-time repair option includes 5 fixes for $20, with credits that never expire.
What we fix automatically
- Missing or malformed VERSION, FN, and N fields
- A common reason importers silently reject a VCF or import only partial data.
- UTF-8 BOM and encoding issues
- The hidden encoding problems that often break iCloud and Apple Contacts imports.
- Line folding and line ending errors
- Long lines and incorrect CRLF handling can break strict parsers.
- TEL and EMAIL normalization
- Phone and email fields are brought into cleaner, more standards-friendly shapes where safe.
- Multi-contact structure problems
- Malformed BEGIN:VCARD / END:VCARD blocks can cause only one contact to import.
Privacy
Processed in memory
Ordinary validation runs in memory. History, repair downloads, and large jobs use temporary storage only when needed.
Minimal logging
Logs contain request IDs and operational status only, not contact payloads.
Encrypted in transit
All uploads and downloads happen over HTTPS.
Building something with vCards?
CorrectVCF also has an API for developers who need validation and autofix in production workflows.
Simple REST API
POST a raw .vcf, get validated results and a fixed file in one response.
curl -X POST "https://api.correctvcf.com/api/validate-vcf?autofix=1" \
-H "Authorization: Bearer $CORRECTVCF_KEY" \
-H "Content-Type: text/vcard" \
--data-binary @contacts.vcf