If the .vcf is already attached to an email or message on your iPhone, tap the attachment. If it is on a computer or tablet, or contains a batch of people, use iCloud Contacts on iCloud.com and choose Add > Import Contact.
That is the first decision, not the finish line. A VCF is imported only when the expected people reach the right account or list and their important fields still match the original file.
Pick the route from where the file is
For one contact sent through Mail or Messages, open the message and tap the .vcf attachment. That is Apple's documented attachment route, and it is the shortest path when someone has sent you one contact. An Outlook vCard export can arrive as a .vcf email attachment too, so an Outlook origin does not require a separate iPhone import method.
Apple documents the tap, but not the destination account, a bulk confirmation control, or a documented batch importer in Files. After the attachment opens, check where the contact landed. The preview is not proof that the import reached the place you intended.
If you first need the format explained, what a VCF file can contain is the useful next stop. The file format and the import job are related, but they are not the same question.
For a file sitting on a Mac, Windows PC, or tablet, or for a file with many people, use iCloud Contacts on a tablet or computer. Open iCloud Contacts, choose Add, choose Import Contact, and select the vCard. Apple says an imported vCard with more than one person produces separate entries in All Contacts. That makes iCloud the route that lets you see a batch as a batch. Follow the Add and Import Contact steps, then inspect the result instead of importing the same file again from the phone.
Choose the account before you repeat anything
An iPhone can hold contacts from iCloud, Google, Microsoft Exchange, Yahoo, and other accounts. The default account setting controls where new contacts are created. It does not prove where a tapped VCF landed. An account's contacts can also be hidden from the Contacts view without being removed from the online account. Check the visible account or list first. Apple's guide on multiple Contacts accounts explains why that distinction matters.
For an iCloud destination, confirm that the iPhone uses the same Apple Account as iCloud Contacts. In Settings, open your name, iCloud, See All, and Contacts, then make sure Contacts is enabled. That connection lets entries imported through iCloud Contacts appear on the phone, as Apple's iCloud setup instructions describe.
Google is a different destination, not a reason to import the same file into iCloud as well. On a computer, open Google Contacts, choose Import, Select file, choose the .vcf, and choose Import. Then add Google on the iPhone through Settings > Apps > Contacts > Add account > Google and enable Contacts synchronization. If an imported detail seems absent, Google says to check Notes. Google's contact import steps cover the computer import, while its Google account sync path covers the iPhone setting.
Decide where the contacts should live before repeating an import. A second import can make the count harder to read and create duplicates without fixing a hidden account.
Set the expected count before importing a batch
One vCard entity can contain one vCard or several. One .vcf file can therefore produce one contact or a group of separate contacts. Before selecting Import, write down the number you expect. Afterward, compare it with the entries in All Contacts, not just with the file preview. The RFC 6350 specification permits one or more vCards in one entity, and Apple's iCloud result is the useful operational part: each person becomes a separate All Contacts entry.
If your source began as a spreadsheet, keep the header row and treat it as the map from columns to contact fields:
First Name,Last Name,Phone,Email
Mina,Patel,tel:+14165550142,[email protected]This is a fictional mapping example, not a device result. First Name and Last Name identify the person, Phone supplies the phone value, and Email supplies the address. The header row is part of the mapping, as Google's contact import guidance indicates, so do not delete it before an import that expects named columns.
The file can also be easier to understand in its vCard form. Here is a fictional RFC 6350 vCard 4.0 fixture:
BEGIN:VCARD
VERSION:4.0
FN:Mina Patel
TEL;VALUE=uri:tel:+14165550142
EMAIL:[email protected]
END:VCARDBEGIN:VCARD and END:VCARD mark the record's boundaries. VERSION:4.0 declares the format version. FN gives the record its required formatted name. TEL carries a phone URI, and EMAIL carries the address. Those lines describe the input. They do not prove that an iPhone displayed every field after import.
Confirm a real import, not a preview
Search Contacts for a recognizable name, phone number, or email address, then open the record. Apple's contact search supports those details, so use whichever value is least ambiguous. For a fictional test of the process, search for Mina Patel and the phone or email from the examples above. For a real import, use a person you can recognize without guessing.
Compare the opened record with an untouched copy of the .vcf. Check the name, phone, email, and any other field that matters to you. A property present in the file is expected input, not proof that iPhone displayed the field in the same place after import. Apple's iCloud import instructions do not promise identical mapping. That small distinction catches the most annoying kind of success: the file opened, some people appeared, and one important detail quietly went missing.
If the Files app only previews the VCF or does not expose a documented import action, keep the original file and send or forward it to an email or message on the iPhone. Then use the attachment route above. The fallback is deliberately boring. Boring is good when the alternative is editing the only copy.
If names appear twice, open Contacts > View Duplicates and review the records one at a time. Two linked cards from different accounts can look like one unified card without being merged underneath. Distinguish that view from a true duplicate before choosing Merge or Merge All. Apple's duplicate review and merge controls let you inspect the individual records first.
Once the import is verified, Zapped is a useful future sharing alternative: its shareable digital card can hold contact details and links and keep the same public URL alias after you update the content. It complements a static VCF for future sharing. It does not import or repair the file.
When the result still looks wrong
If an iCloud batch is missing, check the same Apple Account, confirm iCloud Contacts is enabled, and look at the relevant list or account before importing again. A missing contact can be a visibility or destination problem, not a failed file.
If the count is wrong, compare it with the number you wrote down before import. If a field is wrong, compare the saved record with the untouched file. If names are duplicated, review View Duplicates individually rather than merging a whole batch on sight.
If the file itself appears malformed, keep the original and follow VCF troubleshooting to check the file before trying another import.
The shortest useful summary is: tap a received attachment, use iCloud Contacts for a file on another device or a batch, choose Google only when Google is the intended home, and verify destination, count, and fields against the original. Opening the VCF is the handoff. The checks are the import.
