Fix: CSV Opens in One Column in Excel

Why this happens

When you double-click a .csv, Excel splits columns using the "list separator" defined by your Windows regional settings, comma in US/UK-style locales, semicolon in many continental European locales (where comma is already the decimal separator). If the file's actual delimiter doesn't match what your system expects, Excel can't find any of "its" delimiter in the row and dumps the whole line into one cell.

The fix: import with an explicit delimiter

1. Open a blank workbook (don't double-click the file).
2. Data → Get Data → From File → From Text/CSV.
3. Select the file. In the preview, check the Delimiter dropdown, Excel usually auto-detects it correctly here even when double-click doesn't. If it's wrong, pick the actual one (Comma, Semicolon, Tab, or Custom).
4. Click Load.

If the file already imported wrong and is sitting in column A

1. Select column A (or the range).
2. Data → Text to Columns.
3. Choose Delimited, click Next.
4. Check the box for the actual delimiter used in your data (or enter it under "Other").
5. Finish. The columns split in place, no re-import needed.

A second, less common cause: unescaped delimiters inside a field

If most rows split correctly but a few don't, or columns shift right partway through a row, the delimiter itself isn't the problem, a text field (like an address or description) contains the delimiter character without being wrapped in double quotes. A properly formed CSV wraps any field containing the delimiter in "double quotes": "Smith, John",42,"123 Main St, Apt 4". If the source export skipped quoting, Excel has no way to know that comma was part of the data rather than a column boundary.

Our Column Validator flags rows with an inconsistent field count so you can find exactly which lines are affected before re-importing anywhere.

If you'd rather change the Windows setting anyway

For a machine that only ever opens comma-delimited files and never needs to double-click a semicolon-delimited one, changing the system list separator can be the simpler fix, just know it's system-wide, not per-file:

1. Open Control Panel → Region → Additional settings (Windows 10/11: search "Region" in Start).
2. Change List separator from ; to , (or vice versa).
3. Apply, then re-open the CSV, double-click now splits correctly.

This affects every application that reads the Windows list separator, not just Excel, including some scripts and other CSV-consuming tools on the same machine. If you regularly work with files in both delimiters, the explicit import method above is safer than a system-wide change.

Preventing this for files you export yourself

If you control the code or tool that generates the CSV, standardizing on comma as the delimiter avoids the whole class of problem for whoever opens it next, comma is the delimiter most import tools and libraries assume by default when none is specified. If your data or locale requires semicolon (common where comma is already the decimal separator), say so explicitly in the filename or accompanying documentation rather than leaving it for the recipient's Windows settings to decide.

Doing this in How To CSV

If you'd rather fix the file itself than repeat the import wizard every time, Auto Fix detects the real delimiter and re-saves the CSV in a normalized, standard-comma format, entirely in your browser. To check for the unescaped-delimiter problem specifically, paste the file into CSV Lint for a line-by-line report before you decide which fix applies.