TanodTools
EN

Contacts CSV import checker

Review a CSV against Google's current Contacts template before importing. Your contacts stay in this browser; nothing is uploaded or imported.

Runs entirely in your browser

Local review only. Google Contacts current template. No upload, account connection or import. Warnings are suggestions to review, not an acceptance verdict.

No file selected. You can also paste CSV below.
Not saved to browser storage. Use Clear or close the tab to remove the page's working copy.

Current Google Contacts template only. UTF-8 CSV; local safety guards: 5 MB, 30,000 data rows, 500 columns and 256,000 characters per field. The report shows at most 500 findings, with complete counts. These are checker limits, not Google import-file limits. No Outlook validation, live account check, automatic repair or duplicate-merge prediction.

How to check a contacts CSV

  1. Export a UTF-8 CSV using Google's current Contacts template. Keep your original file as a backup.
  2. Choose the CSV locally or paste its contents, then select Check CSV. File reading and checks happen in this browser.
  3. Review header, field and row-limit warnings. Make changes in your original spreadsheet, export comma-separated UTF-8 CSV, and check again before importing.

Use the current Google Contacts template

The current template uses First Name, Middle Name, Last Name, Email 1 - Label, Email 1 - Value, Phone 1 - Label and Phone 1 - Value. Repeated groups use positive numbers: for example, Email 2 - Value. Header spelling, spaces and capitalization matter to this template check. No name column is documented as mandatory.

Quoted commas, doubled quotes, quoted newlines, UTF-8 BOM and CRLF line endings are supported. Semicolon and tab delimiters are recognized for review and warned about; export comma-separated CSV before using Google's template. Malformed quoting or non-UTF-8 files are stopped rather than silently guessed. Empty records are ignored; rows with any data count toward the import-row check.

Sources and limits

Official Google Contacts Help, checked : Import your contacts into Google Contacts (template, field formats and 3,000-contact import limit); Google Contacts size limits (account and per-contact limits). Open those sources yourself when needed; the checker never fetches them or the template.

The account limits are 25,000 contacts or 20 MB excluding photos. Per-contact limits are 128 KB, 500 fields and 1,024 characters per field except Notes. The report does not claim that a CSV byte count equals Google's stored-contact size. The cited pages do not state a CSV import-file byte limit; this checker's 5 MB limit is a browser safety guard. Existing contacts, account capacity, duplicates and how any import is applied are outside this check.

Questions

Do my contacts leave my device?

No. The page reads the selected file locally, makes no processing requests and does not store contacts in browser storage. It does not connect to Google or import anything. Clear removes the working text and report; close the tab when finished.

Are name columns required by Google?

Google's current instructions do not require a name field: each row with any data creates a contact. This checker recommends First Name, Middle Name or Last Name and flags missing name columns for review, not as an import blocker.

What Google limits are checked?

Google documents a maximum of 3,000 contacts per import. It also documents 25,000 contacts or 20 MB excluding photos per account, 128 KB per contact, 1,024 characters per field except Notes, and 500 fields per contact. This checker counts nonempty rows and checks field length, but cannot know your account's remaining space or measure Google's internal contact representation. The cited pages do not specify a maximum CSV import-file size.

What if my CSV uses older Google or Outlook headers?

This version checks the current Google Contacts template, with headers such as First Name and Email 1 - Value. Older exports may use Given Name or E-mail 1 - Value; those are identified as unrecognized current-template headers with suggestions, not declared invalid in every importer. Outlook's format is not validated.

Are phone, email and date warnings definitive?

No. Email checks only inspect shape, not existence or delivery. Phone checks are broad heuristics, not numbering-plan validation. Google documents YYYY-MM-DD or --MM-DD for Birthday and Event values. Unusual values deserve review, not a judgment about the person or a promise of import success.

Will Google merge duplicate contacts?

This checker does not predict duplicate handling, merges or account changes. It does not remove any row or edit the CSV.