Google Contacts Import Failed? Fix Every VCF Error

Google Contacts is one of the most forgiving VCF import tools there is. It reads vCard 2.1, 3.0 and 4.0, tolerates properties outside the standard and quietly strips data it cannot process instead of rejecting the whole file. So when Google Contacts does fail to import a VCF, the problem is real. The file is too large, the account is full or the structure is broken badly enough that even Google’s parser gives up.

We build contact file tools at Univik and have tested Google’s import behaviour against VCF files from iPhones, Samsung phones, Outlook, Salesforce and HubSpot exports since 2013, including the failure cases this guide maps. Every error message below is quoted exactly as Google shows it, so you can match yours and jump straight to the fix. And if you have not attempted the import yet, start with our Google Contacts import walkthrough instead. This page is for imports that already failed.

Google Contacts Import Error Messages Explained

Google shows different messages for different failures, and the exact wording narrows the cause immediately.

“Select a CSV or vCard file under 20 MB” means the file exceeds Google’s upload cap. Embedded contact photos are the usual culprit, since Base64 photo data inflates a 500 contact file past 50 MB with ease.

“Can’t import contacts” is the generic failure. It covers structural problems, missing BEGIN:VCARD or END:VCARD tags, invalid property syntax and contacts that break Google’s field limits, and it also appears when the account quota is full.

“Gmail is temporarily unable to access your Contacts” points at Google’s side, not your file. It shows up during service hiccups, sync conflicts and backend overload, and the VCF itself is fine.

“The file you’re importing isn’t formatted for Google Contacts” means the upload is not a valid VCF or CSV at all. A renamed file extension, a download that corrupted or a file that is not really a vCard produces this one. The same message fires on CSV imports when the file uses Outlook’s CSV layout instead of Google CSV format, a separate problem behind identical wording.

Import reports success but the count is wrong. This is the silent partial failure. Google imported what it could parse and skipped the rest without naming a single skipped contact. The partial import section below covers hunting them down.

8 Reasons Google Contacts Rejects a VCF File

Behind those messages sit eight concrete causes, and Google’s own limits explain most of them.

1. File Exceeds 20 MB

Google rejects any import file over 20 MB before parsing a single contact. Embedded photos cause almost every oversized VCF, since each PHOTO property stored as Base64 adds 30 to 100 KB per contact. A 500 contact file with photos reaches 25 to 50 MB, well past the cap.

2. Over 3,000 Contacts in One Import

Google documents this limit itself. An import takes up to 3,000 contacts at a time, and a file beyond that fails or imports partially. In our testing, even files approaching the limit slow down noticeably, and batches of about 1,000 import cleanly every time, which is why the fixes below use that batch size.

3. Account Quota Reached at 25,000 Contacts

Each Google account stores a maximum of 25,000 contacts. An account holding 20,000 that receives a 10,000 contact file fails once the ceiling hits, and Google does not name the quota in the failure. You get the generic “Can’t import contacts” instead, which is why the quota check belongs in every diagnosis.

4. Invalid VCF Structure

Every valid entry starts with BEGIN:VCARD, ends with END:VCARD and carries at least a VERSION and an FN name property, per the vCard standard RFC 6350. Mismatched tags, missing required properties and broken syntax make Google’s parser drop entries or reject the file. The common sources are buggy export tools, hand edits in a text editor and files truncated during download or email transfer. Two quieter breakers hide in the same category. A UTF-8 byte order mark, invisible bytes some Windows editors write before BEGIN:VCARD, fails the parse even though the file looks perfect. And folded lines corrupt silently, since a long property continues on the next line only when that line starts with a space, so an editor that strips leading spaces breaks every folded property in the file.

5. A Contact Exceeds the Field Limits

Google enforces per contact limits stricter than people expect, 128 KB total, 500 fields and 1,024 characters per field with Notes excepted. CRM exports break these constantly because they pack activity histories and custom fields into each entry. One contact with a meeting transcript in its NOTE property blows the size limit on its own.

6. Encoding or Character Issues

Google reads files as UTF-8. A VCF in a legacy encoding such as Shift-JIS, EUC-KR or Windows-1252 with quoted-printable text fails for the affected entries, which produces the classic symptom, ASCII only names import while names in other scripts vanish or arrive garbled.

7. Network or Browser Problems

The import runs through a browser, so the browser can be the problem. Unstable Wi-Fi, corporate proxies that touch uploads, extensions that interfere with Google’s JavaScript and aggressive ad blockers all kill imports that have nothing wrong with the file. The tell is that the same file imports fine on another machine or network.

8. Google Workspace Admin Restrictions

On a Workspace account run by an employer or school, the admin controls contact import. A disabled import button or a permission error on a managed account means the restriction is policy, not the file, and the fix runs through your administrator.

Diagnose Your Import Failure in One Minute

Four checks identify the cause before you edit anything. Right click the file and open Properties on Windows or Get Info on Mac to read the size. Anything over 20 MB makes size the issue. Open the file in a text editor and count occurrences of BEGIN:VCARD, which equals the contact count, and on Mac or Linux grep -c "BEGIN:VCARD" yourfile.vcf gives the number in one command. Compare the BEGIN:VCARD and END:VCARD counts, and a mismatch means structural damage. And search for PHOTO, because long Base64 blocks under that property are what inflate a small address book past the size cap. For the quota, open contacts.google.com and read the total in the sidebar against the 25,000 ceiling.

8 Fixes for Google Contacts VCF Import Failures

Fix 1. Split the VCF File into Smaller Batches

For files over 20 MB or past 3,000 contacts, splitting is the reliable fix. Keep each batch to about 1,000 contacts and import the batches at contacts.google.com a few minutes apart so Google’s backend keeps up.

Manual splitting works for small jobs. Cut contacts at END:VCARD boundaries into separate files, and make sure every file opens with BEGIN:VCARD and closes with END:VCARD. Past a few hundred contacts the manual route stops being worth it, and the Univik VCF Splitter cuts a file of any size into clean batches by contact count in one run. Our VCF splitting guide walks both routes.

Fix 2. Strip Embedded Photos

Removing PHOTO properties shrinks a photo heavy VCF by 80 percent or more. Open the file in an editor with regex support such as Notepad++ or VS Code, enable regex in Find and Replace and use a pattern that matches the PHOTO line plus its continuation lines. In Notepad++ the pattern PHOTO[^\r\n]*\r?\n(\s[^\r\n]*\r?\n)* matches the full multi line entry. Replace with nothing, save and import. The contacts arrive without pictures, which you can add back by hand later, and if the photos have to survive, split the file with Fix 1 instead so each batch stays under 20 MB.

Fix 3. Validate and Repair the VCF Structure

When BEGIN:VCARD and END:VCARD counts differ, repair before importing. A file that ends abruptly lost its final END:VCARD to truncation, so add it. If the very first line shows anything before BEGIN:VCARD, or the import fails on a file that looks flawless, convert the encoding in Notepad++ with Encoding, then Convert to UTF-8, which also removes a hidden byte order mark. Entries missing an FN name line fail silently, so give each one a name or delete the broken entry. And properties with empty values, a bare TEL line with no number, are worth removing. For damage past what a text editor handles, our guide on fixing VCF file errors covers the deeper repairs.

Fix 4. Convert the Encoding to UTF-8

Open the file in Notepad++ or VS Code and read the encoding in the status bar. Anything other than UTF-8, whether ANSI, Windows-1252, Shift-JIS or ISO-8859-1, needs converting. In Notepad++ use Encoding, then Convert to UTF-8. In VS Code click the encoding name, reopen with the correct source encoding so the characters render, then save with UTF-8. Our VCF encoding error guide goes deeper when the garbling survives the conversion.

Fix 5. Trim Oversized Contact Fields

CRM exports from Salesforce, HubSpot or Zoho break Google’s per contact limits routinely, and the NOTE property is the usual offender because CRMs stuff conversation histories into it. Search the file for NOTE entries running to thousands of characters and trim them under 1,024 or remove them. Dozens of custom X properties per contact are also worth deleting, since Google ignores them anyway and they burn the 500 field budget for nothing.

Fix 6. Clear Account Quota

Near the 25,000 ceiling, free space before importing. Delete contacts you no longer need at contacts.google.com, then empty the Trash at contacts.google.com/trash with Delete forever, because deleted contacts keep counting against quota for 30 days until purged. Check the Other contacts section too at contacts.google.com/other. Google auto creates those from people you have emailed, they count against the quota and they run into the thousands on old accounts.

Fix 7. Switch Browser or Clear the Path

For network and browser failures, disable extensions first, ad blockers and privacy tools above all, and retry. Then try a different browser entirely. A file that imports in Firefox after failing in Chrome had a browser problem, not a file problem. The phone app is the third path. On Android, open the Google Contacts app, tap your profile icon, then Contacts app settings, then Import and pick the VCF. The mobile route uses a different upload mechanism and succeeds in cases where the web interface fails, with the same size and quota limits applying either way.

Fix 8. Normalize the File with a Converter

When encoding problems, oversized fields and structural errors overlap in one file, fixing them one at a time is an afternoon gone. The Univik VCF Converter rebuilds the file in one pass. Load the broken VCF, choose vCard 3.0 with UTF-8 as the output and every entry comes out with valid structure, clean encoding and standard properties that meet Google’s requirements. This is the route for CRM exports, legacy email client files and anything from enterprise tools that write their own flavour of vCard.

Match the Error Message to the Fix

Only Some Contacts Imported to Google? Find the Skipped Ones

Partial imports are the trickiest failure because Google never names the skipped contacts. Export everything from Google Contacts as a vCard immediately after the import, then count BEGIN:VCARD in the original file and in the export. The difference is the number of skipped contacts. To find which ones, search the export for each name from the original, and the names that come up missing are your skipped entries.

Examine those entries in the original VCF for the usual suspects, an oversized NOTE field, encoding damage in the FN line, a missing required property or a malformed number. Fix them, save just those contacts into a new small VCF and import it on its own. If any of them turn out to already exist in Google, the Merge and fix tool in the sidebar cleans up the overlap after the import.

Frequently Asked Questions

What are the exact import limits for Google Contacts?

Google caps accounts at 25,000 contacts, import files at 20 MB and single imports at 3,000 contacts. Each contact stays under 128 KB, 500 fields and 1,024 characters per field, with the Notes field excepted. Batches of about 1,000 contacts import most reliably, so split large files rather than pushing the per import limit.

Why does my VCF import work on iPhone but fail on Google Contacts?

The two enforce different rules. Google applies per contact limits of 128 KB and 500 fields that the iPhone Contacts app does not, and Google’s import runs through a browser where network conditions and extensions interfere, while the iPhone imports on the device. A file that works on iPhone and fails on Google is hitting Google specific limits rather than a format problem.

Can I import multiple VCF files to Google Contacts at once?

No. Google Contacts takes one file per import. For several VCF files, either merge them into one file under 20 MB and 3,000 contacts, or import them one at a time with a minute between uploads so Google’s backend processes each batch. The multiple file limitation applies on both the web interface and the mobile app.

Does Google Contacts support vCard 4.0 imports?

Yes. Google accepts vCard 2.1, 3.0 and 4.0, though 4.0 specific features such as MEDIATYPE parameters and some structured value types get stripped silently during import. vCard 3.0 is the safest format for a Google import, and converting a stubborn 4.0 file down to 3.0 resolves failures on its own in some cases.

Why did Google import my contacts but all the names are garbled?

The file uses an encoding other than UTF-8. Google reads it as UTF-8 regardless, so names with characters beyond ASCII arrive as garbage when the real encoding is Windows-1252 or Shift-JIS. Convert the original file to UTF-8, delete the garbled contacts from Google and import the corrected file.

The import succeeded but I see duplicate contacts. How do I fix this?

Use Google’s merge tool. At contacts.google.com, open Merge and fix in the sidebar and review the suggested merges, or use Merge all if you imported the same file twice. To stop duplicates before they happen, run the Univik vCard Duplicate Remover on the VCF before importing, so one clean record per person goes in.

The Bottom Line

The fix follows the error. Size errors want photos stripped or the file split. Format errors want structural repair. Quota errors want a cleanup of existing contacts and the trash. Network errors want a different browser or a half hour of patience. And a file with several problems at once wants a converter to rebuild it in one pass rather than an afternoon of hand edits.

Run the three checks before touching anything. File size under 20 MB, contact count under 3,000 per batch and account total under 25,000. Those three checks resolve most Google Contacts import failures before a single line of the file needs editing.