DataSwitch Pro Private, in-browser data converter

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

By the DataSwitch Pro team · · 4 min read

You double-click a CSV file and instead of a neat table, Excel shows every row squeezed into column A: id,name,city,total in one cell, then 1,Amina,Fes,120 in the next. Nothing is wrong with the data. Excel simply split the file on a different character than the one the file uses.

Why it happens: the list separator

CSV has no built-in way to declare its delimiter. When you open a CSV by double-clicking it, Excel does not inspect the file; it splits each line on the list separator defined in your operating system's regional settings.

The problem appears whenever the two sides disagree. A comma-separated export from a web app opened on a French-configured PC lands in one column, and a semicolon file saved by a European colleague does the same on an American PC. The same mismatch explains why Save As → CSV in Excel produces semicolons on some computers and commas on others.

Fix 1: Import the file instead of double-clicking it

Importing lets you tell Excel which delimiter to use, and it is the fix that works on any computer without changing settings.

  1. Open a blank workbook in Excel.
  2. Go to Data → From Text/CSV and select the file.
  3. In the preview window, set Delimiter to Comma, Semicolon or Tab until the columns look right.
  4. Check File Origin: choose 65001: Unicode (UTF-8) if accented or Arabic characters look wrong.
  5. Click Load — or Transform Data if you need to set column types, for example to keep leading zeros.

In older versions of Excel, the same option is under Data → From Text (the Text Import Wizard), where you pick Delimited and then the separator.

Fix 2: Split the column you already have

If the file is already open with everything in column A, select column A, go to Data → Text to Columns, choose Delimited, tick the correct delimiter and click Finish. This is quick for a one-off file, but be careful: fields that contain the delimiter inside quotes are handled correctly, while line breaks inside quoted fields are not, because Excel has already split those rows apart.

Fix 3: Convert the file to the delimiter Excel expects

If you send files to people with different regional settings, the most robust solution is to give each of them a file that matches their Excel — or skip CSV entirely and send an .xlsx workbook, which has no delimiter problem at all.

Fix 4: The sep= line (use with care)

Excel recognises a special first line that declares the separator:

First line of the CSV file

sep=,
id,name,city,total
1,Amina,Fes,120

With that line, Excel splits the file on commas regardless of regional settings. It is an Excel-only convention, though: databases, Python, Google Sheets and most other tools treat sep=, as a data row, and in some Excel versions it interferes with UTF-8 detection. Use it only for files that will exclusively be opened in Excel.

Changing the system list separator

On Windows you can change the list separator itself under Control Panel → Region → Additional settings → List separator. This affects every program on the computer and changes how Excel saves CSV files too, so it is rarely the best choice on a shared or work computer. Prefer importing (Fix 1) or converting the file (Fix 3).

How to avoid the problem when you create CSV files

Summary

A CSV in one column is a delimiter mismatch between the file and Excel's regional list separator. Import the file with Data → From Text/CSV and choose the delimiter, convert it to the separator your audience uses, or send an Excel workbook instead.

Try it on your own file. Free, private, and processed in your browser.

Frequently asked questions

Why does the same CSV open correctly on my colleague's computer?

Their Windows or macOS region uses a list separator that matches the file. Excel follows the computer's regional settings, not the file.

Is a semicolon-separated file still a CSV?

Informally, yes. Many tools call any delimited text file a CSV. Strictly, RFC 4180 describes comma-separated files, so for software and APIs a comma is the safer choice.

Does Google Sheets have the same problem?

Less often. Google Sheets' import dialog detects the separator automatically and also lets you choose it.

More guides