01
Upload your file
Drop your .vcf into the fixer at /fix. Validation is free, so you can see what is wrong first.
VCF rescue for broken contact files
Your contacts file is broken. Let’s fix it now.
Upload your .vcf file and get a repaired download fast — no manual edits, no subscription required for a one-time rescue.
Processed in memory, not stored Works with Outlook, Apple & Google One-time fix available — no subscription
Does this sound familiar?
These are the most common failure cases we fix. If yours is here, you’re in the right place.
🟦 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 throws an error on the file entirely.
🍎 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
You have hundreds of contacts in the file but only the first one makes it through.
☁️ 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
Something structural is wrong with the file, such as missing headers, malformed cards, or bad line endings.
How it works
02
We find the problems
Every property is checked against the vCard spec and against real-world client behavior in Outlook, Apple, Google, and iCloud.
03
Download a fixed file
Get a repaired .vcf immediately. The one-time rescue 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
Your contacts are processed in memory and are not stored as uploaded files.
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