If your vCard file won't open, keep the original untouched and work on a copy. Check the filename, then the records, then import with the contacts app where you want the people saved.
A silent double click, a rejected import, and a preview showing one person when you expected twenty need different responses. Find out which failure you have before rewriting the file.
Check the filename
Archive the original download or export, then make a working copy. Open only the copy. For background on the format, see our guide to what a vCard file contains.
- Check the full filename. A fictional file named contacts.vcf.txt ends in .txt, even though "vcf" sits in the middle. Google Contacts on a computer expects the .vcf extension for vCards, and Microsoft says Outlook for Mac also requires a .vcf filename.
- If the copy contains recognizable vCard records, correct the filename. That gives the importer the extension it expects. It doesn't convert the contents.
- If the file really ends in .vcf but double clicking does nothing, use the destination app's import command. In Outlook for Mac, Microsoft documents Open With > Microsoft Outlook for this case.
Once the record checks below pass, the ordinary vCard opening walkthrough can take over. If they don't, another app association won't supply the missing data.
Check the records in a text copy
Open the working copy in a plain text editor. This complete example is fictional:
BEGIN:VCARD
VERSION:3.0
FN:Example Person
N:Person;Example;;;
TEL:+1-202-555-0100
EMAIL:[email protected]
END:VCARDWhat to look for:
- BEGIN:VCARD at the start and END:VCARD at the end of every contact.
- A VERSION line. RFC 2426 requires a vCard 3.0 object to contain VERSION, FN, and N.
- An N line with four semicolons, which separate the five name components. Leave those semicolons as they are; adding backslashes before them changes their meaning.
A vCard 4.0 record has VERSION immediately after BEGIN, includes FN, and closes with END:VCARD. Its telephone line declares a URI value, as in TEL;VALUE=uri:tel:+1-202-555-0100. Changing just VERSION:3.0 to VERSION:4.0 doesn't make the other changes a record needs, so a new version label isn't a conversion.
Fix a record with no END:VCARD
This fictional truncated version 4 record can still look convincing:
BEGIN:VCARD
VERSION:4.0
FN:Example Person
N:Person;Example;;;
TEL;VALUE=uri:tel:+1-202-555-0100
EMAIL:[email protected]The name, telephone, and email are all visible, but END:VCARD is missing, so the record never closes. If your copy looks like that, or has no recognizable record boundaries, request a fresh export or download from the sender or source contacts app. Don't guess which lines to add. Keep the original archive so you can compare it with the replacement.
Fix garbled names and odd lines
If an accented name is already garbled in the text copy, don't blindly save it under another encoding. Ask for a fresh export from the source. If the text looks right but the saved contact looks wrong, keep the source intact and use the one contact test below.
When you isolate a contact, keep continuation lines with the property they belong to. RFC 6350 specifies UTF-8 and folded lines for version 4.0, with a continuation beginning with one space or horizontal tab, so a physical line break doesn't necessarily mean a new field.
Leave unfamiliar properties alone, too. RFC 6350 permits registered and extension properties, so an unknown field isn't proof of corruption. Its text escaping rules also distinguish punctuation inside values from structural punctuation. Removing fields or changing every semicolon is a poor repair when the importer hasn't told you which data it rejects.
Import into your contacts app
Pick the address book you use, and import there. A convincing preview in whichever app happened to open doesn't settle where the people were saved.
iPhone and iCloud
Apple documents importing on iPhone by tapping a .vcf attachment in an email or message. Try that first. The full iPhone import procedure has the longer walkthrough.
If tapping does nothing and the copy has complete records, use a tablet or computer, open Contacts on iCloud.com, then choose Add > Import Contact and select the vCard. Apple says each contact in a file containing several contacts becomes a separate entry in All Contacts.
If the record is incomplete, get a replacement source first.
Mac Contacts
Apple Contacts on Mac supports three import routes: double click the .vcf, drag it into Contacts, or choose File > Import, select it, and then choose Add. Contacts indicates duplicates during import. Review that indication before treating repeated names as newly recovered people.
Google Contacts on Android or a computer
On Android, Google's documented path is Organize > Import from file. If you have multiple accounts, choose the destination account, then select the VCF.
On a computer, Google Contacts uses Import > Select file. If you can't find an imported detail, check the contact's Notes section.
Google says contacts saved to a Google Account sync with Android devices and Google Contacts. If the import seems to have vanished, check the account you selected.
Outlook for Mac
Use a .vcf file, and if double clicking doesn't open it, choose Open With > Microsoft Outlook. Microsoft says the window can show only the first contact while the contacts in the file are saved individually. Open the saved contacts before deciding the rest vanished.
Import one contact first
Keep the full source untouched. On a working copy, export or isolate one complete representative record, from BEGIN:VCARD through END:VCARD, keeping its continuation lines and unfamiliar fields. RFC 6350's record and property rules explain why cutting at a convenient visible line changes what you're testing.
- If the source contains accented names, include one in the sample.
- Import the sample through your destination's route above.
- Open the saved contact and compare its name, phone, email, and accented characters with the source.
If the app rejects the record, or the saved values differ, stop. Ask the sender or source app for a fresh export and keep the original archive.
Count the contacts in the file
After the sample passes, retry the full list. Count BEGIN:VCARD records in the source, not physical lines, and compare that number with the newly saved people. Don't use the total size of an address book that already held contacts. Apple says iCloud imports each contact separately, while Microsoft's Outlook for Mac instructions explain its first contact preview.
Then open a few saved contacts and compare their phone, email, and accented names. A matching count with damaged fields is still unfinished work.
Move iCloud contacts to Outlook on a PC
Microsoft documents a specific Windows Contacts to CSV route: import the iCloud VCF into Windows Contacts, export it as CSV, then import that CSV into Outlook.
- Check the export first. Microsoft warns that an iCloud export can contain only one contact when you meant to export them all. If the source only has one, go back and export the intended selection.
- Keep the CSV heading row and map its columns to the appropriate contact fields. This fictional row shows the idea; your export may use different headings:
First Name,Last Name,Mobile Phone,E-mail Address
Mira,Example,+1-202-555-0101,[email protected]- After import, check those values as you did for the VCF sample. Avoid uploading private contacts to an unvetted converter when a documented destination route is available.
Share your next card
Keep the archived original and the working copy until you've checked the newly saved people and their important fields. Recovery is complete when the intended people are in the intended account, with values that match the source.
For future sharing, Zapped offers a live digital card shared by link, QR code, or NFC tap, with shared paths that can keep pointing to the latest profile after edits.
