How to Change CSV Delimiter (Comma, Semicolon, Tab)

By CSV Editor Team · Last updated: 2026-03-16

If you need to change a CSV delimiter from comma to semicolon, semicolon to comma, or convert CSV to tab-separated format, parse the file correctly first, confirm what the destination system expects, then re-export with the new delimiter. That avoids one-column imports, shifted fields, and broken quoted text.

Delimiter changes are often required when you move data between spreadsheet tools, CRMs, ecommerce imports, accounting systems, or regional formats. If one system expects commas and another expects semicolons, the file can look broken even when the underlying data is fine.

When you should change a CSV delimiter

  • Your file opens as one long column because the reader expects a different separator.
  • A destination import spec explicitly requires semicolon-delimited or tab-delimited files.
  • You are consolidating exports from different systems and need one standard delimiter before import.
  • You want TSV output because text fields contain many commas and tabs are safer for that workflow.

Before you convert: check these three things

1. Know the target format. Some tools accept only comma-delimited CSV. Others expect semicolons in certain locales, or work better with tab-separated values. Always check the import template or documentation first.

2. Confirm quoted fields are handled correctly. A value like "Paris, France" contains a comma that belongs to the data, not the delimiter logic. If you swap commas blindly in a text editor, you can corrupt valid rows.

3. Review encoding at the same time. Delimiter problems and encoding problems often show up together. If the file also has weird characters or import warnings, review CSV delimiters and encoding before export.

Step-by-step: how to change a CSV delimiter safely

  1. Open the source file in a CSV-aware tool that previews rows and columns correctly.
  2. Identify the current delimiter so the file parses into the right table structure first.
  3. Check for quoted fields, embedded commas, semicolons, tabs, and line breaks inside cells.
  4. Choose the new delimiter: comma, semicolon, or tab, based on the destination requirement.
  5. Preview the converted table and confirm column counts stay consistent across multiple rows.
  6. Export as a new file rather than overwriting the original immediately.
  7. Run a quick test import in the destination app before replacing the old workflow file.

Comma vs semicolon vs tab: when each makes sense

Comma-delimited CSV: the most common default for web apps, APIs, and many import tools. Use this when the destination documentation simply says “CSV” and does not specify otherwise.

Semicolon-delimited CSV: common in spreadsheet workflows and regions where commas are used as decimal separators. If your spreadsheet or import wizard expects semicolons, this is usually the right export choice.

Tab-delimited (TSV): useful when data contains many commas and you want a cleaner visual split. Some legacy systems or manual QA workflows prefer tabs because text fields are less likely to contain them naturally.

Example: why raw find-and-replace breaks CSV

If your source row looks like this:

name,city,note
Ava,"Paris, France","Needs comma-delimited export"

A naive replace of every comma with a semicolon would also change the comma inside "Paris, France", which is real data. A CSV-aware export changes only the separators between fields and keeps quoted cell content intact.

Common delimiter conversion mistakes

Using find-and-replace on the raw file: this can replace commas inside quoted values and damage the dataset. Always convert through a parser-aware workflow.

Ignoring repeated header or schema issues: if you are standardizing multiple files first, make sure they share the same headers and column order before export. Otherwise the new delimiter will not fix structural mismatches.

Skipping test import: a file may look correct in a preview and still fail the destination system because of regional defaults, required encoding, or template-specific rules.

Delimiter change vs encoding fix

If the file opens as one column, the delimiter is the first thing to check. If the columns look correct but the text itself shows characters like à or �, that is usually an encoding issue instead.

For character problems, continue with CSV UTF-8 encoding guidance or garbled characters troubleshooting.

Quick QA checklist before export

  • Destination tool delimiter requirement confirmed
  • File parsed correctly before conversion
  • Quoted fields preserved during re-export
  • Column counts match after conversion preview
  • Test import completed on the final output

FAQ

Why does my CSV open in one column?

Usually because the app expects a different delimiter than the file uses. A semicolon-delimited file can appear as one column in a comma-based reader, and vice versa.

Can I convert comma-separated CSV to tab-separated TSV?

Yes. Parse the CSV first, then export using tabs as the separator. This is safer than editing the raw text because quoted commas inside values remain intact.

Should I also change encoding when I change delimiters?

Only if the destination tool requires it or the file already shows encoding problems. Delimiter and encoding are separate settings, but they are often validated together during import QA.

Related guides

CSV import/export workflow hubHow to combine multiple CSV files into oneCSV delimiters and encoding guide

Canonical: https://csveditoronline.com/docs/change-csv-delimiter