Excel Saving CSV with Semicolons? How to Get Commas Instead

You open a CSV in your database tool, import it into Python, or try to load it in another program — and everything lands in one column. No split, no structure. Just a wall of text with semicolons between values.

This is one of the most common and confusing Excel gotchas: in European countries and several other locales, Excel saves CSV files using semicolons as delimiters instead of commas. The file extension is .csv, but what is inside does not match what most software expects.

This guide explains why it happens and how to convert Excel to a proper comma-delimited CSV without changing any system settings.

Why Excel Uses Semicolons Instead of Commas

The short answer: Windows regional settings control the list separator character, and Excel follows them when exporting CSV.

In most English-speaking countries, the decimal separator is a period (3.14) and the list separator is a comma. CSV stands for "comma-separated values" and that is what you get.

In Germany, France, the Netherlands, Spain, and many other countries, the decimal separator is a comma (3,14). If Excel used a comma as the CSV delimiter, it would conflict with decimal numbers — the file would be impossible to parse correctly. So Excel switches to semicolons as the list separator.

The problem cascades when you share files across regions. A German Excel user exports a CSV and sends it to a US developer. The developer's CSV parser reads comma as the delimiter, finds no commas in the file, and dumps everything into column A. Debugging this takes far longer than it should.

The same issue appears when:

• Your Windows system locale is set to a European region, even if you use English Excel
• A client or coworker in a different country sends you their "CSV" export
• You are working on a corporate machine with regional settings you did not configure yourself

The Fast Fix — Browser Conversion Ignores Locale

The browser-based Excel to CSV converter reads the raw .xlsx or .xls file structure directly. It does not use Excel, does not read your Windows regional settings, and does not inherit any locale configuration. The output is always standard comma-delimited CSV.

Here is what to do:

1. Open the converter at /spreadsheet-tools/excel-to-csv/
2. Drag your Excel file onto the converter — the file stays in your browser, nothing is uploaded
3. Select the sheet you want if you have multiple sheets
4. Click Download CSV

The downloaded file uses commas as delimiters, UTF-8 encoding, and standard line endings. It will load correctly in Python, R, SQL import tools, Tableau, Google Sheets, and any other tool that expects standard CSV format.

You do not need to change your Windows regional settings, open the file in a text editor and do a find-replace on semicolons, or write any conversion script.

Sell Custom Apparel — We Handle Printing & Free Shipping

How to Spot a Semicolon CSV Before You Import It

Before running an import that might fail, check the raw file contents. On Windows, right-click the CSV file, choose Open With, Notepad. On Mac, right-click and choose Open With, TextEdit (make sure it is in plain text mode).

Look at the first line. If your column headers are separated by semicolons like this:

Name;Email;City;PostalCode

you have a semicolon-delimited file. If they look like this:

Name,Email,City,PostalCode

you have a standard comma-delimited CSV and no fix is needed.

Some tools give you the option to specify the delimiter during import (Python's pandas read_csv has a sep= parameter, and most database import wizards let you choose). If you have that option, setting sep=';' or choosing semicolon as the delimiter in the import wizard is a valid alternative to converting the file. But if the tool expects standard CSV and does not let you change the delimiter, converting first is the cleaner path.

Delimiter and Encoding Together — Getting Both Right

Two things can go wrong at once: semicolon delimiters AND incorrect character encoding. If your spreadsheet contains non-ASCII characters — accented letters like é, ü, ñ, or symbols like © — encoding matters too.

The standard is UTF-8. Most modern tools expect UTF-8, and the converter outputs UTF-8 by default. This means your accented characters will survive the conversion intact.

Where things break: Excel on Windows sometimes saves CSV files as Windows-1252 (also called Latin-1) instead of UTF-8. When another tool reads that file expecting UTF-8, the accented characters turn into garbage characters. The browser-based converter bypasses this entirely — it reads the underlying Excel binary, not Excel's own CSV export, so it always produces UTF-8 output.

If you need UTF-8 encoding AND comma delimiters, converting through the browser tool gives you both in a single step.

When the Root Cause Is Your System Settings

If you regularly create CSV files from Excel for other people and they frequently complain about semicolons, the permanent fix is to change your Windows list separator setting:

1. Open Control Panel
2. Go to Clock and Region, then Region
3. Click Additional settings
4. Find List separator and change it from ; to ,
5. Click OK and restart Excel

Be aware that changing the list separator also affects other applications that read this setting. And if your locale uses a comma as the decimal separator, you may create a new conflict — numbers like 3,14 in your cells would break the CSV parser that now uses commas as delimiters.

For occasional one-off conversions, the browser converter is simpler and safer. For permanent workflow fixes, the system setting change makes sense — but test it with a few files before relying on it in production.

Frequently Asked Questions

My CSV has semicolons but I cannot edit the file. What should I do?

If you have the original Excel file, use the browser converter to produce a comma-delimited version. If you only have the CSV, you can open it in a text editor and do a global find-replace of semicolons with commas — but be careful if any of your data values contain semicolons, since those would also be replaced incorrectly.

Does this affect Mac users too?

Yes, but less commonly. Mac Excel uses the system locale separator setting too. Most Macs sold in English-speaking markets default to comma as the list separator. But corporate Macs or machines configured for European regions can produce semicolon CSV files the same way Windows machines do.

Can I convert a semicolon CSV directly without going back to the Excel file?

Our converter works from .xlsx and .xls Excel files — not from CSV files directly. If you only have the semicolon CSV and not the original Excel file, the text editor find-replace approach is the fastest path. Just open the file in Notepad or TextEdit, use Find and Replace (Ctrl+H / Cmd+H) to replace semicolons with commas, and save.