CSV Opens With All the Data in One Column in Excel: 4 Ways to Fix It

Updated July 24, 2026 · By the CSVUndo team · 6 min read · Applies to Excel 2016–365 on Windows and Mac

You double-click a CSV and instead of a spreadsheet you get a wall of text: every row crammed into column A, semicolons and all, with columns B through Z completely empty. Müller;Hamburg;20457;1.499,00 sits in a single cell, and sorting or filtering anything is impossible.

Nothing is corrupted. Every column is still in the file — Excel just never split them, because the file's field separator is not the one your copy of Excel was told to look for. Here are four fixes, safest first, plus a way to convert the delimiter outright so the problem stops following the file around.

The symptom: one endless column A

The file opens without any error message, but the grid looks like this:

          A                                      B      C      D
1   name;city;zip;amount                       (empty)
2   Müller;Hamburg;20457;1.499,00              (empty)
3   Fournier;Lyon;69003;2.150,50               (empty)

Classic tells: the header row is one long cell with separators visible inside it, and AutoFilter puts a single dropdown on column A. Often the same file opens perfectly on a colleague's machine — that detail is the whole diagnosis.

Why Excel refuses to split the file

Despite the name, “comma-separated” files are frequently not separated by commas. In most of continental Europe and South America the comma is the decimal separator — one thousand four hundred ninety-nine euros is written 1.499,00. A comma can't do both jobs, so Excel in those locales reads and writes CSV files delimited by semicolons. Other systems export tab- or pipe-delimited files and still call them CSV.

When you double-click a CSV, Excel does not sniff the file to figure out its delimiter. It uses the list separator defined in Windows regional settings — comma on a US or UK system, semicolon on a German or French one. Ship a semicolon file to a comma machine (or the reverse) and Excel finds zero occurrences of “its” separator on each line, so every line stays whole in column A.

Two quirks complete the picture. Some exporters write sep=; as the file's first line — a hint only Excel understands (more in Fix 3). And quoting matters: "Smith, John" is correctly one field because the comma sits inside quotes, but an exporter that wraps entire lines in quotes, or leaves a quote unclosed, produces the same one-column mess even when the delimiter is right.

Fix 1: Data → From Text/CSV and pick the delimiter

The cleanest fix, because you tell Excel the delimiter explicitly instead of letting Windows decide.

  1. Open a blank workbook — don't double-click the CSV.
  2. Go to Data → From Text/CSV and select the file.
  3. In the preview dialog, check the Delimiter dropdown. Excel usually detects semicolons here on its own; if the preview still shows one column, switch it to Semicolon (or Tab, or --Custom-- and type |). The preview re-splits instantly.
  4. While you're there, glance at File Origin: 65001: Unicode (UTF-8) cures accented characters arriving as é — see our guide to é showing up instead of é.
  5. Click Load, or Transform Data first to set ZIP or SKU columns to Text.

Fix 2: Text to Columns on the already-open file

Already double-clicked and don't want to start over? Split column A in place.

  1. Select column A by clicking its header.
  2. Go to Data → Text to Columns, choose Delimited, click Next.
  3. Check Semicolon (and uncheck Tab if it's ticked). Make sure Text qualifier is " so quoted fields survive. The preview updates live.
  4. In step 3, click each column holding codes or IDs and set Column data format to Text, then Finish.
Step 3 is not optional busywork. The split runs through Excel's type-guessing engine, so a freshly separated ZIP column can lose its leading zeros and a barcode column can collapse into scientific notation the moment it finally becomes a column. Anything already sitting in columns B, C, D… gets overwritten, too.

Fix 3: Add a sep=; hint line

Excel honors a special first line that declares the delimiter. Open the CSV in Notepad, add one line at the very top, and save:

sep=;
name;city;zip;amount
Müller;Hamburg;20457;1.499,00

Now double-clicking works: Excel reads the hint, splits on semicolons, and swallows the line so it never appears in the grid. sep=, and sep=| work the same way.

Two real caveats. First, the hint collides with the UTF-8 byte order mark: in most Excel builds, a file that begins with a BOM followed by sep=; gets one or the other, not both — either the hint is ignored, or Excel drops out of UTF-8 mode and every é arrives as é. If the file contains accented text, prefer Fix 1. Second, only Excel understands the line: Google Sheets, Python and every database importer treat sep=; as a data row, so strip it before the file goes anywhere else.

Fix 4: Change the Windows list separator (last resort)

If semicolon files land in your inbox every single day and you can't change the sender, you can change what Excel expects: Control Panel → Region → Formats tab → Additional settings → List separator, replace , with ; (or the reverse), click OK, and restart Excel.

Treat this as the nuclear option. The setting is system-wide: it changes the delimiter Excel writes into every CSV you save from now on, and it flips the argument separator in formulas (=SUM(A1,B1) becomes =SUM(A1;B1)). You may fix the incoming files and quietly break every outgoing one.

Or skip the dialogs: convert the delimiter itself

All four fixes above teach your Excel to cope; the file is still a time bomb for the next person who opens it. The durable fix is converting it to the delimiter its destination expects.

Re-delimit the file in your browser — free, nothing uploaded

CSVUndo auto-detects whether your file uses commas, semicolons, tabs or pipes, shows you the correctly split preview, and re-exports it with the delimiter you need. Everything runs locally — the file never leaves your device.

Open the CSV repair tool →
  1. Drop the one-column CSV onto the tool. The delimiter is detected automatically and the preview shows your data split into proper columns.
  2. Pick the output delimiter your target system wants — comma for US Excel and most APIs, semicolon for a European recipient.
  3. Download the converted file. Quoted fields and embedded separators survive the trip intact.

Frequently asked questions

Why does my CSV use semicolons instead of commas?

It was exported on a system with a European regional format. Where 1.499,00 is how you write a price, the comma is busy being the decimal separator, so exporters in those locales delimit fields with semicolons instead. The file is valid — it just disagrees with a US copy of Excel about what “separated” means.

The same file opens fine on my PC but lands in one column on a colleague's. Why?

Different Windows list separators. Double-clicking uses whatever separator each machine's regional settings define, so a semicolon file splits perfectly on a German-format PC and stays whole on a US-format one. Data → From Text/CSV behaves identically everywhere, because the delimiter is chosen in the dialog, not by Windows.

Does Google Sheets have the same one-column problem?

Rarely. The File → Import dialog defaults to Detect automatically and handles commas, semicolons and tabs well, with a manual override if it guesses wrong. One catch: Sheets does not understand the sep=; hint from Fix 3 and will show it as a stray first row you have to delete.