How to Open Semicolon-Delimited CSV Files

You double-click a CSV that came from a colleague in Germany, a French web app, or a bank export, and instead of neat columns you get one long mess crammed into a single cell. The file is not broken. It is semicolon-delimited, and the tool you opened it with assumed commas. This guide explains why so many CSVs use semicolons, why that jams everything into one column in an English-locale spreadsheet, and how to open, view, edit, and optionally convert the file the right way.

Why so many CSV exports use semicolons

CSV stands for comma-separated values, so the separator should be a comma — except in a large part of the world it is not. The reason comes down to how numbers are written.

In the United States and other English-locale regions, a period is the decimal point and a comma groups thousands: 1,234.56. In much of Europe and many other locales, those roles are swapped. The comma is the decimal separator and a period (or a space) groups thousands, so the same value is written 1.234,56.

Now picture exporting a spreadsheet full of numbers in one of those locales. If the file used a comma to separate fields, every decimal comma inside the data would look exactly like a field separator. A price of 1.234,56 would split into two columns. To avoid that collision, software in those locales exports CSVs using a semicolon as the field separator instead. The decimal commas stay safely inside their fields, and the semicolons mark the real boundaries between columns.

That is why a CSV from a European version of Excel, a French SaaS app, or a German bank so often arrives semicolon-delimited. It is a perfectly valid delimited file; it simply uses a different delimiter than the name "comma-separated" implies. If you want the wider picture of which characters get used and why, CSV delimiters explained covers the full set.

Why it opens as one column in English-locale Excel

Here is the frustrating part. An English-locale spreadsheet defaults to assuming the delimiter is a comma. When you hand it a semicolon file, it dutifully looks for commas to split on — and finds none, because the separators are all semicolons.

With nothing to split, the entire row is treated as a single value. Every column collapses into column A, and each cell holds the whole line:

Name;City;Amount
Müller;Köln;1.234,56

Open that in a comma-expecting tool and row two becomes one cell reading Müller;Köln;1.234,56 instead of three tidy fields. The data is all there; it is just not parsed. Worse, a naive workaround — telling the tool to split on semicolons — can still mangle the decimal commas depending on locale settings, which is its own headache. The clean answer is to use a tool that detects the actual delimiter for you.

Open a semicolon CSV correctly with CEESVEE

CEESVEE is a free, open-source CSV and delimited-file viewer and editor for Windows, macOS, and Linux. It is built to detect what a file actually is, including semicolon-delimited exports, so you never have to fight an import wizard.

1. Drag the file onto CEESVEE. Drop your .csv (or .txt) into the window. On open, CEESVEE inspects the contents and auto-detects the delimiter — semicolon, comma, tab, or pipe — along with the text encoding.
2. Check the columns. The grid loads with the semicolon file already split into proper columns: Name, City, Amount. No single-column pile-up, no manual splitting. This glance is your confirmation that the file parsed correctly.
3. Confirm the encoding looks right. Files from other locales often arrive as Windows-1252 or UTF-16 rather than UTF-8. CEESVEE detects UTF-8, UTF-16 LE/BE, and Windows-1252 and handles the byte order mark, so accented names like Müller and Köln show up correctly instead of as garbled characters. If anything looks off, you can override the encoding; fixing CSV encoding goes deeper on this.
4. Override the delimiter only if needed. Detection is automatic, but if a file is unusual you can set the delimiter to semicolon manually so the grid re-parses instantly.

That is all it takes to view a semicolon CSV the way it was meant to look.

View and edit the file

Once the columns are aligned, the file behaves like any other table. You can scroll through it, edit cells in place, sort columns, run find and replace, and read live stats about the data. The Rust core and virtualized grid keep things responsive even on large files — up to a million rows and 100 MB or more — so a heavy export from a bank or analytics tool stays smooth. And because CEESVEE is 100% local with no accounts or uploads, sensitive data never leaves your machine. If you mainly need to make changes without a spreadsheet, editing CSV without Excel walks through that workflow.

Optionally convert the semicolon CSV to comma

Sometimes you need to hand the file to a tool that expects a standard comma CSV. Converting is a clean, explicit step:

1. Open the semicolon file so the grid is correctly parsed.
2. Choose Save As to bring up the export options rather than overwriting in place.
3. Set the delimiter to comma. This single setting does the conversion.
4. Pick the encoding, quoting style, line endings (LF or CRLF), and BOM if the destination is picky; otherwise leave the defaults.
5. Save. CEESVEE re-serializes every field with commas and automatically quotes any value that now contains a comma, so nothing splits or merges.

Because the editor parses the file into real fields first and then writes them back, the conversion is faithful — never a blind search-and-replace that would corrupt fields containing the delimiter. For the full reasoning and the reverse direction, see changing a CSV delimiter.

The bottom line

A semicolon-delimited CSV is not a corrupt file — it is a normal export from a locale where the comma is the decimal separator. It only looks broken because an English-locale spreadsheet assumes commas and pours every column into one. Open it in a tool that detects the real delimiter and the columns snap into place, ready to view, edit, or convert to comma.

Download CEESVEE for free to open semicolon CSVs (and comma, tab, and pipe files) with the delimiter and encoding detected for you. It is open source under the MIT license, and you can read the code on GitHub.