How to fix a vCard or CSV that is too large to import
This happens when the contact file, or a single contact inside it, is bigger than the service allows. Large photos and bloated CRM fields are the usual cause. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~6 min Updated Jun 2026 91% found this helpful
Error message
File too large. Your CSV or vCard file is over the size limit and cannot be imported.
Summary
A contact import fails for size when the file as a whole, or an individual contact within it, exceeds the service's limits. Google Contacts, for example, enforces strict per-contact limits of 128 KB per contact, 500 fields, and 1,024 characters per field, and other services cap the overall file size or the number of contacts in one import. The usual offenders are large embedded photos, long notes, and the many custom fields that CRM exports pack into each contact. The fix is to make the file smaller and import it in pieces: split the .vcf or .csv into batches at contact boundaries, strip embedded photos and oversized notes, remove non-standard CRM fields, and keep each contact under the limits. Importing in chunks and checking the count after each pass gets a large address book in reliably.
What this error means
Contact services protect themselves with size limits at two levels: the whole file or import, and each individual contact. Google Contacts caps a single contact at 128 KB, 500 fields and 1,024 characters per field, and rejects imports that go over. Other services set an overall file-size or contact-count ceiling.
Most over-limit files are not too many simple contacts, they are a few heavy ones. A contact with a high-resolution embedded photo, pages of notes, or dozens of CRM custom fields can blow past the per-contact limit on its own. Trimming that weight and splitting the file is what gets the import through.
Common causes
The whole file exceeds the service's overall size cap.
There are more contacts than one import allows.
A single contact is larger than 128 KB.
A contact has more than 500 fields or over 1,024 characters in a field.
Embedded PHOTO data makes contacts very large.
Long notes or descriptions bloat individual contacts.
A CRM export packed many custom fields into each contact.
Expert insight
“People assume too large means too many contacts, but it is usually a handful of heavy ones. One contact with a giant embedded photo or a CRM dump of custom fields can break the per-contact limit by itself. So I do two things: rip the embedded photos out, because they are the biggest culprit, and split the file into batches at the END:VCARD boundaries. Import the batches one at a time, check the count after each, and a forty-thousand-line address book goes in without drama.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Split the file into batches
1Open the .vcf in a text editor and split it into smaller files at an END:VCARD boundary, so no contact is cut in half.
2Aim for a few hundred contacts per batch.
3Import each batch in turn.
Method 2
Remove embedded photos
1Embedded photos are the biggest size driver. Search for PHOTO; and delete each PHOTO block, the PHOTO line plus its base64 lines.
2Re-add photos in the contacts app afterwards if you need them.
3This alone often brings the file under the limit.
Method 3
Trim notes and CRM fields
1Shorten very long notes, and remove non-standard CRM custom fields and activity history.
2Delete lines starting with vendor X-properties such as X-SALESFORCE or X-HUBSPOT.
3This shrinks the heavy contacts that break the per-contact limit.
Method 4
Stay under the per-contact limits
1For Google Contacts keep each contact under 128 KB, 500 fields and 1,024 characters per field (the Notes field is more generous).
2Split any single mega-contact across the right fields rather than overfilling one.
3Check the destination's own documented limits, which vary by service.
Method 5
Slim down a CSV
1For CSV, remove unused columns and any empty rows.
2Split the rows into batches the same way you would split a vCard.
3Keep the column set to what the importer needs.
Method 6
Import in chunks and verify
1Import each batch, then check the contact count and a few records before the next.
2If a batch fails, split it again to find the heavy contact.
3This staged approach gets large address books in reliably.
Too large is usually a few heavy contacts, not too many simple ones, so strip embedded photos first, they are the biggest size driver. Then split the file at END:VCARD boundaries and import in batches. Checking the count after each batch makes it easy to spot and isolate any single contact that is still over the limit.
Frequently asked questions
Why is my contact file too large to import?
Either the whole file exceeds the service's cap, or a single contact is over the per-contact limit. Large embedded photos and bloated CRM fields are the usual cause.
What are Google Contacts' import limits?
Each contact must stay under 128 KB, 500 fields, and 1,024 characters per field, with the Notes field more generous. Imports over the file or contact-count cap are also rejected.
How do I split a vCard file?
Open it in a text editor and break it into smaller files at an END:VCARD boundary so no contact is cut in half, then import each part.
Do embedded photos cause this?
Often, yes. Embedded photos are the biggest size driver. Removing the PHOTO blocks usually brings the file well under the limit, and you can re-add photos later.
Why does one contact break the limit?
A single contact with a high-resolution photo, long notes, or dozens of CRM custom fields can exceed the per-contact size on its own. Trim that contact's data.
How do I import a very large address book?
Split it into batches of a few hundred contacts, strip embedded photos, and import the batches one at a time, checking the count after each.
Still not working?
If batches still fail after removing photos and trimming fields, a single contact may have a runaway field such as an enormous note or a malformed property. Isolate it by splitting the failing batch further, or run the file through a converter that enforces the destination's per-contact limits automatically. You can also submit your error to us for a tailored fix.
