If your vCard file won't open, keep the original untouched and inspect a copy. Check the real filename, the declared version, and complete BEGIN:VCARD through END:VCARD records. Then use the importer for the contacts app where you want the people saved. Before retrying a whole list, test one complete representative contact and compare its saved name, phone, email, and accented characters with the source.
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.
A filename problem needs an importer, not a rewrite
Archive the original download or export, then make a separate working copy. Open only the working copy in a plain text editor. If you need the broader format context, our guide to what a vCard file contains explains the record behind the attachment.
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 working copy contains recognizable vCard records, correcting its filename gives the documented importer the extension it expects. It doesn't convert the contents.
If a file really ends in .vcf but double clicking it does nothing, use the destination app's import command. In Outlook for Mac, Microsoft specifically documents Open With > Microsoft Outlook when double clicking fails. That tells Outlook to handle the file; it doesn't show that the contact data is broken.
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.
Read the record before changing the version
In the text copy, find the declared version and the beginning and end of each record. RFC 2426 requires a vCard 3.0 object to contain VERSION, FN, and N, framed by BEGIN:VCARD and END:VCARD. 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:VCARDBEGIN and END frame one contact. VERSION declares 3.0. FN supplies the displayed name, while N separates the family name Person, given name Example, and three empty components for additional names, prefix, and suffix. TEL and EMAIL hold fictional contact values.
RFC 6350 specifies that a vCard 4.0 has VERSION immediately after BEGIN, includes FN, and closes with END:VCARD. Here is the complete fictional counterpart:
BEGIN:VCARD
VERSION:4.0
FN:Example Person
N:Person;Example;;;
TEL;VALUE=uri:tel:+1-202-555-0100
EMAIL:[email protected]
END:VCARDThe telephone line in this example declares a URI value and uses a tel: address. Changing just VERSION:3.0 to VERSION:4.0 doesn't perform the changes needed elsewhere in a record. A new version label isn't a conversion.
In both examples, N:Person;Example;;; contains exactly four unescaped semicolons. RFC 6350 defines the five name components they separate. Keep those structural separators literal; adding backslashes before them changes their meaning. Use these fictional examples to recognize the structure, then check your own export.
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 displayed name, structured 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.
Garbled names are a reason to stop editing
A continuation line isn't a stray line. RFC 6350 specifies UTF-8 and folded lines for version 4.0, with CRLF line breaks and a continuation beginning with one space or horizontal tab. When isolating a contact, keep those continuation lines with the property they belong to. A physical line break doesn't necessarily mean a new field.
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 representative contact test below to check the destination's result.
Leave unfamiliar properties alone, too. RFC 6350 permits registered and extension properties; 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 strategy when the importer hasn't told you which data it rejects.
Choose where the contacts should live
Pick the address book you use before importing. The goal is to save the people there. A convincing preview in whichever app happened to open doesn't settle that.
iPhone and iCloud
Apple documents importing on iPhone by tapping a .vcf attachment in an email or message. Use that route first for a structurally complete attachment. The full iPhone import procedure handles that platform's longer walkthrough.
If tapping does nothing and the copy has complete records, Apple's iCloud Contacts route gives you another documented destination. 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.
Apple documents importing here, not repairing malformed content by importing and exporting again. 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. Choose the account where you want those people saved.
On a computer, Google Contacts uses Import > Select file. Google also advises checking a contact's Notes section if you can't find an imported detail. Inspect the saved contact before concluding that the importer discarded a field.
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. Importing again into a different account won't explain where the first result went.
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. One preview card isn't a head count. Open the saved contacts before deciding the rest vanished.
Retry one contact before the whole address book
Keep the full source untouched. On a working copy, export or isolate one complete representative record, from BEGIN:VCARD through END:VCARD, retaining its continuation lines and unfamiliar fields. RFC 6350's record and property rules explain why chopping at a convenient visible line or dropping an unknown property changes what you're testing.
The sample needs the details you care about. If the source contains accented names, include one in that sample. Import it through the documented destination route, then open the saved contact and compare its name, phone, email, and accented characters with the source.
If the app rejects that complete-looking record, or the saved values differ, stop. Ask the sender or source app for a fresh export and keep the original archive. A larger retry only repeats an unresolved failure.
After the sample passes, retry the full list. Compare the newly saved people with the intended number of source records, counting BEGIN:VCARD records rather than physical lines. 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. Those are good reasons to judge the saved result rather than the window that opened.
Open representative saved contacts again and compare their phone, email, and accented names. A matching count with damaged fields is still unfinished work.
For iCloud contacts going 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. Use this when your source is an iCloud export and your destination is Outlook on a PC.
Check the export before converting anything. Microsoft warns that an iCloud export can contain only one contact when you meant to export them all. Compare the source record count with the people you intended to move. If the source only has one, the importer can't recover the rest; go back and export the intended selection.
In the CSV route, keep the heading row and map its columns to the appropriate contact fields. This fictional row shows how the headings correspond to contact values; your export may use different headings:
First Name,Last Name,Mobile Phone,E-mail Address
Mira,Example,+1-202-555-0101,[email protected]The headings identify the given name, family name, mobile number, and email supplied by the row. Check those values after import, just as you checked the VCF sample. Avoid uploading private contacts to an unvetted converter when a documented destination route is available.
Finish the recovery, then change how you share
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. Use that for the next introduction. For the contacts you're recovering now, finish checking the source export and the saved result first.
