Open huge JSON files instantly. Free & private.🔒 Your data never leaves your browser

Why Your CSV Opens in One Column in Excel (and How to Fix It)

You double-click a CSV file and Excel shows everything squashed into column A, like name,email,city in a single cell. Or the columns are fine, but names like José or Müller appear as José and Müller. Both problems have simple causes and reliable fixes.

Cause 1: The delimiter does not match your region

"CSV" means comma-separated, but when you double-click a file, Excel actually uses the list separator from your computer's regional settings. In many European and other regions the comma is the decimal separator (3,14), so the list separator is a semicolon. Excel then looks for semicolons, finds none, and puts the whole line in one column.

That is also why a CSV made on one computer opens correctly there and breaks on a colleague's computer in another country.

Cause 2: The text encoding is not detected

Most modern tools save CSV as UTF-8. Some versions of Excel assume an older encoding unless the file starts with an invisible marker called a byte order mark (BOM). Without it, every non-English character is shown as two or three strange symbols.

Fix 1: Convert to a real Excel file (most reliable)

An .xlsx file has no delimiter or encoding to guess, so it opens the same way everywhere. Paste your CSV (or JSON) into CSV to Excel and download the workbook. Numbers are stored as real numbers, so formulas and charts work right away.

Try it: CSV / JSON to ExcelTurn CSV or JSON into an .xlsx file that opens correctly in any region.
Open CSV / JSON to Excel →

Fix 2: Import instead of double-clicking

Excel's import wizard lets you choose the delimiter and encoding yourself:

  1. Open an empty workbook and go to Data → From Text/CSV (on older versions: Data → Get External Data → From Text).
  2. Select the file.
  3. Set File Origin to 65001: Unicode (UTF-8) and set Delimiter to Comma (or whatever your file uses).
  4. Click Load.

On a Mac, use File → Import → CSV file and choose the same options.

💡 In the import preview you can set columns like zip codes, phone numbers and IDs to Text. That keeps their leading zeros and stops long numbers from turning into 1.23457E+15.

Fix 3: Change the delimiter to match Excel

If the file is only for people in a semicolon region, save it with semicolons. CSV Cleaner detects the input delimiter automatically and lets you choose Semicolon as the output delimiter. JSON to CSV has the same option.

name;email;city
José;jose@mail.com;Madrid

Fix 4: The "sep=" line (Excel only)

Adding this as the very first line tells Excel which delimiter to use, whatever the regional settings:

sep=,
name,email,city
Ann,ann@mail.com,Cairo

This is an Excel-only trick. Other programs, such as databases, Python and Google Sheets, will read sep=, as data, so only use it for files that are meant just for Excel.

Which fix should you use?

SituationBest fix
Sending a file to people who use ExcelSend .xlsx (Fix 1)
You received a CSV and want to open it nowImport wizard (Fix 2)
All users are in one semicolon regionSemicolon delimiter (Fix 3)
The file is also read by other softwareKeep a standard comma CSV and use Fix 1 or Fix 2 for Excel users. Don't add sep=.

Related

Tools used in this guide

More guides