Google Sheets CSV Import: Fix Encoding, Delimiter, Formula Errors

Quick Answer

Google Sheets CSV imports fail for four main reasons: semicolon delimiters from European-format files, wrong character encoding producing garbled text, automatic number formatting that strips leading zeros, and Google Sheets' 10-million-cell or 100MB import limits.

The fix: Convert European semicolon-delimited CSVs to comma-delimited before importing. Re-encode ANSI or Windows-1252 files to UTF-8. Import ZIP codes and IDs as text, not numbers.

Why it happens: Google Sheets auto-detects delimiter and encoding but uses locale-based rules that don't always match the file's actual format. When detection fails, it opens all data in one column or displays corrupted characters.

---

What Google Sheets' Import Behavior Actually Means

File opens with all data in column A, separated by semicolons — Your CSV uses semicolons as delimiters (common in European exports from Excel, SAP, or Salesforce). Google Sheets detected the wrong delimiter. Fix: re-export as comma-delimited or use File → Import and specify the delimiter manually.

Names and special characters show as question marks or boxes — Encoding mismatch. Your file is saved as ANSI, Windows-1252, or ISO-8859-1 but Google Sheets is reading it as UTF-8. Re-encode the file to UTF-8 before importing.

ZIP codes, phone numbers, or employee IDs are missing their leading zeros — Google Sheets automatically converts columns that look like numbers into Number format, stripping leading zeros. Format the column as Plain text after import, or pre-format your CSV to protect these values.

Formulas display as text strings — Cells starting with = in your CSV are being treated as text. This is correct behavior — Google Sheets does not execute formulas imported from CSV files for security reasons.

Import fails silently or hangs on large files — Your file exceeds Google Sheets' 10-million-cell limit or 100MB import limit. Split the file before importing.

---

Fast Fix (90 Seconds)

If your Google Sheets CSV import just failed or looks wrong, try this first:

1. Check your delimiter — Open the CSV in Notepad or TextEdit. If columns are separated by semicolons, you have a European-format file.
2. Fix via File → Import — In Google Sheets, go to File → Import → Upload → select your file → choose "Custom" separator → enter ; or , depending on your file.
3. Fix encoding — If you see garbled characters, go to File → Import → change encoding to "UTF-8".
4. Protect leading zeros — After import, select the affected column → Format → Number → Plain text, then re-import.
5. Split large files — If import hangs, your file likely exceeds 100MB or 10M cells. Use SplitForge CSV Splitter to divide it first.

For persistent encoding or delimiter issues, continue below.

---

TL;DR: Google Sheets misreads semicolons (European CSVs) as broken data, strips leading zeros automatically, and garbles non-UTF-8 characters. Fix delimiter issues at import time via the custom separator option. Fix encoding by re-exporting as UTF-8. Run your file through SplitForge Delimiter & Encoding Fixer to convert both in one step before importing.

---

Your marketing team exported a contact list from your EU-based CRM. You open it in Google Sheets and the entire dataset lands in column A, each row a single string of text separated by semicolons. Or you import a customer file from your accounting software and names like "Müller" appear as "M??ller." Or you import a product database and every SKU starting with 0 is now missing its leading zero.

None of these failures produce an error message. Google Sheets opens the file and shows you data — just wrong data.

Each error type was reproduced using Google Sheets' File → Import feature, March 2026.

---

---

Diagnose Your Import Problem in 30 Seconds

Match what you see on screen to the root cause before reading further.

If you see semicolons in column A: that's a delimiter problem (Fix 1), not an encoding problem — even if it looks like garbled data.

---

How Google Sheets Compares to Other Import Systems

Google Sheets is the most forgiving platform here — it coerces values silently rather than erroring. The tradeoff is precision loss: a ZIP code 01234 silently becomes 1234 with no warning. Use it for exploration and cleaning, not as a final validation step.

---

Table of Contents

• Diagnose Your Import Problem in 30 Seconds
• How Google Sheets Compares to Other Import Systems
• Why Google Sheets Misreads CSV Files
• Fix 1: Semicolon Delimiter (European CSV)
• Fix 2: Encoding Errors and Garbled Characters
• Fix 3: Leading Zeros Disappearing
• Fix 4: Date Format Issues
• Fix 5: Large File Import Limits
• Common Scenarios
• Additional Resources
• FAQ

---

This guide is for: Data analysts importing exports from European systems, operations teams working with SAP or Salesforce exports, finance teams importing transaction data, anyone whose CSV "worked yesterday" and now looks wrong in Google Sheets.

---

Why Google Sheets Misreads CSV Files

Google Sheets auto-detects delimiter and encoding when you open a CSV file by double-clicking. This auto-detection uses your Google account's locale setting, not the file's actual content.

A user in the United States with a US locale will have comma auto-detected as the delimiter. A user in Germany with a German locale will have semicolon auto-detected. If the file and the locale don't match — which is common with international data exports — the import fails silently.

The bypass: always use File → Import (not double-click) when importing CSVs. The Import dialog lets you specify delimiter, encoding, and conversion behavior manually, bypassing locale-based auto-detection entirely.

Fix 1: Semicolon Delimiter (European CSV)

European versions of Excel, SAP, and many accounting platforms export CSVs using semicolons as delimiters instead of commas. This is because the comma is used as the decimal separator in European number formatting (1.000,50 instead of 1,000.50).

When Google Sheets' auto-detection expects commas and finds semicolons, all data lands in column A as a single concatenated string.

Method A — Fix at import time (recommended):

1. In Google Sheets, go to File → Import.
2. Click Upload and select your CSV file.
3. On the import settings screen, change Separator type to Custom.
4. Enter ; in the separator field.
5. Click Import data.

Method B — Convert before importing:

If you need to do this regularly, convert semicolon-delimited CSVs to comma-delimited before they reach Google Sheets. Run your file through SplitForge Delimiter & Encoding Fixer to convert semicolons to commas in seconds without uploading the file to any server.

Verification: After import, your data should be spread across multiple columns with each field in its own cell. If column A still shows semicolons, the separator was not changed.

Fix 2: Encoding Errors and Garbled Characters

Garbled characters — question marks, boxes, or ü instead of ü — mean your CSV was saved in a non-UTF-8 encoding and Google Sheets is interpreting it incorrectly.

Common encodings that cause this problem: Windows-1252 (ANSI), ISO-8859-1 (Latin-1), and UTF-16. These encodings handle accented characters (é, ü, ñ, ç) differently than UTF-8.

Method A — Specify encoding at import time:

1. Go to File → Import → Upload → select your file.
2. On the settings screen, look for the Character set / Encoding dropdown.
3. Try Windows-1252 or ISO-8859-1 if your file came from Excel on Windows.
4. Check the preview — if names and special characters look correct, proceed with import.

Method B — Re-encode the file first (more reliable):

Re-encoding before importing produces cleaner results and prevents mixed-encoding issues in the sheet.

1. Open your CSV in Notepad++ (Windows) or TextWrangler (Mac).
2. Go to Encoding → Convert to UTF-8.
3. Save the file.
4. Import the UTF-8 file into Google Sheets with encoding set to UTF-8.

Method C — Use SplitForge:

Run your file through SplitForge Delimiter & Encoding Fixer to detect and convert encoding in your browser. The file is never uploaded — encoding conversion runs client-side.

Fix 3: Leading Zeros Disappearing

Google Sheets converts any column that looks like a number into Number format on import. This strips leading zeros from ZIP codes (01234 becomes 1234), employee IDs (00847 becomes 847), and phone numbers with country code prefixes.

This is not a bug — it's Google Sheets treating numeric-looking strings as numbers. The solution is to tell Google Sheets to treat those columns as text before the conversion happens.

Method A — Format column after import:

1. Import your CSV normally.
2. Select the affected column.
3. Go to Format → Number → Plain text.
4. The zeros are already gone at this point — you need to re-import.

Method B — Protect values before import (correct approach):

Before importing, wrap the affected values in your CSV with a leading apostrophe or format them as text in your source spreadsheet. Google Sheets treats cells with a leading apostrophe as text strings and preserves leading zeros.

In Excel: select the ZIP/ID column → Format Cells → Text → save as CSV.

Alternatively, use SplitForge Data Cleaner to prefix affected columns with a text qualifier before import, preventing Google Sheets' auto-format from firing.

Method C — IMPORTDATA formula approach:

Use Google Sheets' IMPORTDATA or IMPORTCSV functions with explicit formatting applied to the column after data loads.

For more on this issue, see our guide on CSV leading zeros disappearing.

Fix 4: Date Format Issues

Google Sheets interprets dates using your account locale. A US account expects MM/DD/YYYY. A UK account expects DD/MM/YYYY. A file with 03/05/2026 reads as March 5 in the US and May 3 in the UK.

Common date problems:

• Dates importing as text — Format doesn't match what Google Sheets expects for your locale.
• Dates importing as wrong values — MM/DD ambiguity between locales.
• Numbers showing as dates — Google Sheets misidentifies numeric patterns as dates (e.g., 2026-03 read as a date).

Fix:

1. Standardize all dates to ISO format YYYY-MM-DD before importing. Google Sheets recognizes this format regardless of locale.
2. Use File → Import and set the locale explicitly if your dates are in a non-default format.
3. After import, verify a sample of dates against your source data.

For complex date format issues, see our guide on fixing mixed date formats in CSV.

Fix 5: Large File Import Limits

Google Sheets enforces two limits on CSV imports: 10 million cells total per spreadsheet, and 100MB maximum file size. A 100MB CSV with 10 columns hits the file size limit. A 100MB CSV with 50 columns hits the cell limit much sooner.

Signs you've hit the limit: Import hangs indefinitely, import completes but rows are missing, or Google Sheets shows an error about file size.

Fix: Split your CSV before importing. For the complete split workflow, see our guide on how to split large CSV files. SplitForge CSV Splitter divides large files by row count, file size, or both — processing locally in your browser without uploading.

Common Scenarios

Exporting from Salesforce to Google Sheets

Salesforce CSV exports use UTF-8 encoding and comma delimiters by default. The common problem is column count — Salesforce reports can export 100+ columns. Strip unused columns before importing to avoid Google Sheets performance issues.

European Accounting System Exports

SAP, DATEV, and many European accounting platforms export semicolon-delimited files with Windows-1252 encoding. These files need both delimiter conversion and encoding conversion before Google Sheets handles them correctly. Do both conversions in one step with SplitForge Delimiter & Encoding Fixer.

Many CSV tools process these files by uploading them to a remote server. For accounting exports that contain financial data, using a client-side tool means your transaction data never leaves your browser.

Google Sheets as Intermediary Before Another Platform

A common workflow: clean data in Google Sheets, then export as CSV for import into a CRM or database. When re-exporting from Google Sheets, go to File → Download → Comma Separated Values (.csv). This produces a UTF-8, comma-delimited file that imports cleanly into most platforms. For more on what to verify before uploading, see our CSV import errors complete guide.

Additional Resources

Google Documentation:

• Import data into Google Sheets — Official Google Sheets import help including encoding and delimiter options
• Google Sheets file size limits — Official cell and file size limits

Standards:

• RFC 4180: CSV Format Specification — Official CSV delimiter and structure standard
• Unicode UTF-8 Standard — Character encoding reference for international data
• IANA Character Set Registry — Official registry of encoding names including Windows-1252 and ISO-8859-1

FAQ