Why Your CSV Opens in One Column

When you double-click a CSV, Excel does not ask how to parse it — it silently uses your operating system's regional "list separator" setting. On US-configured systems that separator is a comma. On most European systems, where the comma is the decimal separator (3,14), the list separator is a semicolon instead.

So the mismatch works both ways: a semicolon-delimited file (common from European colleagues and many export tools) opened on a US system, or a comma-delimited file opened on a European system, both fail the same way. Excel looks for its expected separator, does not find it, concludes each line is one single value, and dumps everything into column A. Tab-delimited files saved with a .csv extension trigger it too.

A ten-second diagnosis: open the file in Notepad or any text editor and look at the first line. Whatever character actually sits between the values — comma, semicolon, or tab — is your delimiter, and now you know exactly what to tell Excel.

Fix 1: Text to Columns (Repair What's Already Open)

If the file is already open and glued into column A, you can split it in place:

• Step 1 — Click the column A header to select the entire column of crammed data.
• Step 2 — Go to the Data tab and click Text to Columns.
• Step 3 — Choose Delimited and click Next.
• Step 4 — Tick the delimiter you found in the text editor (Semicolon, Comma, or Tab) — the preview pane instantly shows the data splitting into columns.
• Step 5 — Click Finish. Your values spread across real columns, ready to sort and filter.

Fix 2: Import Instead of Opening (From Text/CSV)

Text to Columns fixes the layout but not the deeper issue: double-clicking a CSV also lets Excel mangle your data types — stripping leading zeros from ZIP codes, rewriting product codes like 4E5 as scientific notation, and reformatting dates. The professional habit is to never double-click a CSV you care about.

Instead, open a blank workbook and use Data, then Get Data, then From Text/CSV. Excel previews the file, auto-detects the delimiter (and lets you override it), and lets you control column types before anything is committed to the grid. Click Transform Data for full control, or Load if the preview already looks right. It is a few more clicks, but nothing gets silently altered.

Fix 3: Convert the CSV to a Real Excel File Online

The wizard-free option is to stop feeding Excel raw CSVs altogether. Upload the file to the free CSV to Excel converter, click convert, and download a native .xlsx where the columns are already split correctly — the delimiter is detected automatically, so semicolon files from European systems and standard comma files both come out as proper tables. There is no sign-up, no watermark, and files up to 50 MB are supported.

This route shines when you receive CSVs regularly from the same source, when you need to forward the data to someone who will absolutely double-click it, or when the file needs UTF-8 characters preserved. And it works in both directions: when a system demands CSV back, the Excel to CSV converter produces clean, UTF-8 comma-delimited output, and if a developer wants the data instead, the CSV to JSON converter turns the same file into API-ready JSON.

Keeping Leading Zeros and Other Data Intact

One final trap: even with the delimiter fixed, opening a CSV directly converts anything that looks like a number into a number — so 02139 becomes 2139 permanently the moment you save. If your data contains ZIP codes, phone numbers, or ID codes, either use the From Text/CSV import and set those columns to Text in the preview, or convert to .xlsx online before opening. Once data is in genuine Excel format, its types are stored in the file and stop depending on whoever opens it — which is exactly why converting properly once beats re-fixing the same file forever.

Frequently Asked Questions