Logo
Back to Blog
Tools August 16, 2026 7 min read

Importing a VCF File to iPhone and Android

O

OmniWebKit Team

Tooling

Share:
Article Cover Image

Search for how to get contacts onto a phone and every result recommends downloading software. Most are data-recovery products with a free trial that stops before it finishes the job.

You do not need any of it. Both platforms import a contact file with tools already on the device, and the whole thing takes about two minutes.

How to import a vcf file to iPhone

The simplest route is email. Send the file to an address you can open on the phone, tap the attachment, and choose to add the contacts.

For anything over about fifty contacts, use iCloud instead. Sign in at icloud.com on a computer, open Contacts, and use the import option in the settings menu. The contacts sync to your phone within a minute or two.

iCloud is more reliable on large files, and it has an advantage nobody mentions: the same settings menu can archive your contacts first. That archive is the closest thing to an undo button either platform offers, and it takes ten seconds.

Make the archive. We have watched people import the wrong file and spend an evening deleting contacts one at a time.

How to add contacts to Android from vcf

Email works here too. Open the attachment and Android offers to import it.

The Contacts app has a proper import option as well: open it, find Settings or Manage contacts, then Import, and pick the file from storage.

Watch the account it asks about. Contacts saved to a Google account sync everywhere and survive a lost phone. Contacts saved to the device do neither, and they vanish with a factory reset.

Choosing an account here is the single decision that matters, and it is easy to tap past.

Why did my import create duplicates?

This is the most common complaint, and the cause is structural rather than a bug.

Address books identify a contact by a unique identifier called UID. Freshly generated cards usually have none, so the app falls back to comparing names.

Name matching is fragile. “Ada Lovelace” and “Ada K. Lovelace” are two different people as far as the comparison is concerned, and importing the same file twice reliably doubles everything.

There is no setting that prevents it. Cleaning up afterwards is part of the job, which is why checking what you are about to import is worth the ten seconds.

How to merge duplicate contacts after import

Both platforms have a tool for this and neither advertises it.

On iPhone, the Contacts app surfaces a “Duplicates Found” banner at the top of the list when it detects them. Tapping through offers to merge them in one action.

On Android, the Google Contacts app has a Merge and fix section that lists suggested pairs. It works well and it does guess, so read the list before accepting all of them.

Merge from a computer if you have hundreds. Both platforms expose the same tools through their web interfaces, and reviewing a long list of suggestions is far easier with a mouse.

Check the file before you import it

Importing is all or nothing on both platforms. There is no screen offering to take these three hundred and leave those hundred.

So look first. The vcf viewer opens the file in a browser and reports the contact count, which is where most surprises live — a file named after one person very often holds an entire exported address book.

It also flags cards with no name. Those get refused silently, which is why an import of 400 sometimes produces 388 and no explanation at all.

When the file needs fixing first

Two problems are worth fixing before importing rather than after.

Missing country codes are the first. If numbers lost their leading plus, the contacts import fine and fail the moment someone travels. That damage almost always happened in a spreadsheet, and fixing it there and rebuilding the file with the CSV to VCF converter beats editing hundreds of contacts on a phone.

Very large files are the second. Embedded photos push a contact file into megabytes, and phones time out on large imports more often than web interfaces do. Splitting into batches of a few hundred is more reliable than one hopeful attempt.

If you are building the file yourself, the vcard generator writes one card correctly, escaping and all.

A short checklist

Archive your existing contacts first, on either platform. It is the only real undo.

Open the file and check the count before you commit. Import through the web interface for anything large, and pick the right account on Android.

Then expect duplicates and deal with them in one pass using the built-in merge tools. That order turns an afternoon of cleanup into about five minutes.

Frequently Asked Questions

Do I need to install an app to import contacts?

+
No, on either platform, despite most search results recommending one. Emailing the file to yourself and opening the attachment works on both. The paid installers exist because the search term is valuable, not because the job needs them.

Can I choose which contacts to import from a file?

+
Almost never. Address books treat a .vcf as all or nothing, which is why checking the file first matters. Splitting it beforehand is the only reliable way to import part of a list.

Why did my import create duplicates?

+
Address books match contacts on a unique identifier called UID, and freshly generated cards usually have none. Without it, apps fall back to comparing names, and any small difference makes a second entry. Importing the same file twice reliably doubles everything.

The import said it finished but some contacts are missing.

+
Cards with no name are refused silently by most address books, so a file of 400 can produce 388 with no error. Opening the file in a viewer first shows how many nameless cards it contains.

Where do imported contacts actually go on Android?

+
To whichever account you picked during the import, usually a Google account. Contacts saved to the device rather than an account do not sync and disappear with a factory reset, which is the trap worth avoiding.

Can I undo an import?

+
Not as a single step on either platform. On iPhone, restoring an iCloud contacts archive rolls the whole address book back to an earlier point. On Android, deleting by account is easier if you imported into a fresh one.

Should I import through iCloud or straight onto the phone?

+
iCloud for anything over about fifty contacts. The web interface handles large files more reliably than the phone, and the results sync down. It also gives you the archive feature, which is the closest thing to an undo.

Do photos survive the import?

+
Usually yes, if they are embedded in the file. They also make it very large, and a few address books refuse cards past a certain size. If an import fails for no obvious reason on a big file, photos are the first thing to check.

Why do my contacts show without country codes after importing?

+
The plus was lost before the file was created, most often by a spreadsheet treating the number as a number. Importing does not remove it. Fix the source data and re-import rather than editing hundreds of contacts by hand.

Is there a size limit on what I can import?

+
Nothing published, and practical limits exist. Very large files with embedded photos time out on phones more often than through a web interface. Splitting into batches of a few hundred is more reliable than one large attempt.

Tags

#vCard#Contacts#iPhone#Android#How-To