Why this happens
Delimiter problems usually happen because CSV is not always comma-separated in practice. Many European spreadsheet setups export semicolon-delimited files. Some systems emit tabs or pipes. If the receiving tool assumes the wrong separator, it will still read the file, just in the wrong shape.
The root cause is therefore not always a bad file. It is often a mismatch between the file’s actual delimiter and the parser’s assumption. Users then start editing the data itself when the only defect was the separator setting used during import.
A delimiter mismatch example
This file is valid as a semicolon-delimited export, but it will look broken in a tool that assumes commas.
account_id;customer;region;status 1001;Acme GmbH;DE;active 1002;Beta SA;FR;paused 1003;Cora SpA;IT;trial
Open that file with comma settings and each row appears as one cell. The data is not malformed; the parser is simply looking for the wrong separator.
What a corrected version looks like
account_id,customer,region,status 1001,Acme GmbH,DE,active 1002,Beta SA,FR,paused 1003,Cora SpA,IT,trial
A repaired workflow either imports the original semicolon file with the correct setting or converts it into a comma-delimited CSV for tools that require commas.
Step by step: diagnose and repair
Step 1. Look at the first few raw lines
Do not start in a spreadsheet. Open the file as plain text and see which character repeats between fields most consistently.
Step 2. Count candidate separators against the header width
Check commas, semicolons, tabs, or pipes and compare the result with the number of columns you expect. The correct delimiter usually produces the most consistent field count across several rows.
Step 3. Watch for delimiters inside quoted text
If a field contains commas inside quotes, those commas should not count as separators. A simple visual count can be misleading if quote rules are already broken.
Step 4. Import or validate with the suspected delimiter
Use a tool that lets you override the separator and confirm whether the preview now aligns correctly.
Step 5. Standardize the file for the next consumer
If the receiving system only accepts commas, convert the delimiter once after validation instead of asking every user to remember a special import setting.
How to fix it manually
The manual fix depends on whether you want to preserve the original delimiter or convert it. If the downstream tool supports semicolons or tabs, simply import the file with the correct setting. If not, convert the file to the required delimiter while respecting quoted text so you do not replace separators inside actual field values.
Be careful with search-and-replace in a text editor. A global replace of semicolons to commas is only safe when semicolons are truly acting as delimiters and never appear inside quoted text fields. If there is any doubt, use a parser-aware tool rather than blind text replacement.
Delimiter confusion often travels with encoding or Excel issues, so compare this repair with encoding troubleshooting and Excel CSV import fixes when the symptoms overlap.
How CSVDoctor fixes this automatically
CSVDoctor can detect the likely delimiter and reparse the file with that choice, which is much faster than manually testing commas, semicolons, tabs, and pipes one by one. It also validates row widths afterward so you can tell whether the delimiter was the only problem or whether quotes and malformed rows are involved too.
That makes delimiter repair much safer than repeated spreadsheet guessing. Use CSVDoctor to identify the separator automatically, preview the parsed rows, and export a cleaned file in the format your next tool expects.
Open CSVDoctor to inspect the CSV in your browser, repair the structural defects, and download a cleaner file for the next import or review.
When delimiter issues are really locale issues
Many delimiter problems trace back to locale defaults rather than user error. In countries where the comma is used as a decimal separator, spreadsheet software often exports semicolons so numeric values remain readable. The receiving system then assumes commas because it was built with a US-centered default. The file is technically fine, but the workflow is not aligned.
The long-term fix is to document the expected delimiter at both ends of the exchange. If a vendor always sends semicolons and your app only accepts commas, convert the file intentionally in one controlled step instead of asking every user to guess the correct import setting every time.
A good operational habit is to store one sample export per source system and note the delimiter beside it. That way new team members can compare a fresh file with a known-good sample in seconds instead of opening the CSV in three different tools and guessing which view is correct.
Related fixes and next checks
If the file opens as one column in Excel, the spreadsheet-specific workflow in csv-to-json.html shows how to import with the right separator. If the wrong delimiter also created uneven rows, continue with row length mismatch troubleshooting afterward.
FAQ
Is a CSV always comma-separated?
No. Many files use semicolons, tabs, or pipes depending on locale and export settings.
Why do semicolon CSV files exist?
They are common in locales where the comma is used as a decimal separator, so spreadsheets export semicolons instead.
Can I replace every semicolon with a comma manually?
Only if semicolons never appear inside quoted text. Otherwise you risk changing actual data values.
What is the safest way to confirm the delimiter?
Inspect the raw text and test a parser or validator with the suspected separator instead of relying on spreadsheet guesses.