Semicolon vs Comma CSV: Which Should You Use?

Comma vs Semicolon: The Real Difference

A CSV file uses a field separator to split values on each line. In much of the US, UK, Canada, and Australia the separator is a comma. In many European locales, Excel saves "CSV" with semicolons because the comma is already used as the decimal mark (2,50).

Both files are valid delimited text. Neither is wrong. Trouble starts when a comma-expecting reader opens a semicolon file—or vice versa.

Why This Matters

Delimiter mismatch is the #1 reason CSV files open in one column. It is also the #1 cause of failed imports that a manager assumes is "bad data."

• US teams open EU exports and see everything smashed into column A.
• EU teams open US exports and Excel treats semicolons as literal text.
• Automation scripts silently misread rows if the separator is wrong.
• Portals that require comma CSV reject semicolon exports.

How to Tell What You Have

Do not trust the extension. Inspect the actual bytes.

• Open a copy in a plain text editor and look at line 1.
• Count commas vs semicolons in the header.
• Preview in the Online CSV Editor with each delimiter setting.
• Confirm decimal values look right (2,50 vs 2.50).

Step-by-Step: Convert Between Semicolon and Comma CSV

Do quote-aware conversion, not blind find-and-replace.

• Preview the source and confirm the actual separator.
• Decide the target separator based on the destination.
• Use the CSV to Delimited Converter and pick the correct output separator.
• Preview the converted file for split columns and untouched decimal values.
• Download the file and re-verify in Excel or the target tool.

product;price;currency
Tea;2,50;EUR
Coffee;3,20;EUR

product,price,currency
Tea,"2,50",EUR
Coffee,"3,20",EUR

import csv

with open("input.csv", newline="", encoding="utf-8") as inp, \
     open("output.csv", "w", newline="", encoding="utf-8") as out:
    reader = csv.reader(inp, delimiter=";")
    writer = csv.writer(out, delimiter=",")
    for row in reader:
        writer.writerow(row)

Excel Locale Settings

Excel derives its list separator from the operating system region. Changing the OS list separator changes what Excel writes as "CSV."

Prefer explicit workflows: Data > Get Data > From Text/CSV, and CSV UTF-8 exports. That way the delimiter is a choice, not a locale accident.

Real-World Examples

The mismatch is old but never stops appearing.

Common Mistakes

Instincts betray you here.

• Find-and-replace commas with semicolons, destroying decimal values.
• Renaming files without changing delimiters.
• Assuming EU or US style based on team, not on the actual bytes.
• Ignoring encoding as a compounding issue.

Best Practices

Make the separator explicit.

• Prefer comma CSV UTF-8 for US/UK-facing interchange.
• Prefer semicolon CSV UTF-8 for EU-facing interchange when required.
• Document delimiter in file names or README.
• Convert with quote-aware tools.
• Preview before every upload.

Why Use Convert CSV Online?

Delimiter conversion is where browser tools shine. Convert CSV Online is free, browser-based, and needs no account for everyday conversions. Use the CSV to Delimited Converter to switch separators safely, and use the Online CSV Editor to verify. Client-side workflows run on Windows, macOS, and Linux browsers.

Conclusion

Semicolon vs comma is a locale story, not a bug. Detect the real separator, convert deliberately, and preserve decimal values as intended.