Fix "The File You're Importing Isn't Formatted" in Google Contacts

Few errors are as frustrating as Google Contacts telling you "the file you're importing isn't formatted correctly" and then refusing to say why. The message gives no detail, but the causes are a short, fixable list. Here's how to get your contacts in cleanly.

Cause 1: Header Row Doesn't Match

Google Contacts maps your columns to its fields using the header row. The most common failure is a mapping mismatch — your headers don't line up with what Google expects, usually because the file came from another system with creative column names like "E-mail Address 1" or "Mobile." The reliable fix is to start from Google's own template: export an existing contact (or a sample) from Google Contacts, then paste your data under those exact headers.

Cause 2: Wrong Encoding

Google Contacts expects a UTF-8 CSV. A file saved from Excel in the default encoding can fail or import names with corrupted accents. Re-save using "CSV UTF-8 (Comma delimited)" in Excel, or round-trip the file through Google Sheets (import, then download as CSV), which always outputs UTF-8.

Cause 3: Not a True CSV

Sometimes a file has a .csv extension but is actually an Excel file or uses semicolons instead of commas. If Google keeps rejecting it, open it in Excel or Sheets and explicitly export to CSV again to guarantee it's genuinely comma-separated plain text.

Cause 4: Too Many Contacts at Once

Google recommends importing no more than 3,000 contacts at a time. Larger imports can fail or partially complete. Split big lists into batches of 3,000 or fewer and import them one after another.

Step-by-Step: Prep a Google-Ready File

The Faster Way: Automated Cleanup

Matching headers, fixing encoding, and de-duplicating by hand is slow. PipeSheets can normalize headers, re-encode to UTF-8, trim whitespace, and remove duplicate contacts in one pass, then export a clean comma-delimited CSV ready for Google Contacts. Save the steps as a pipeline and reuse them on every list.