CSV Delimiter Converter
Convert CSV to TSV or between comma, semicolon, tab, pipe and custom delimiters with RFC 4180 quoting, chosen quoting rule, line endings and optional trimming.
The re-delimited text, the detected input delimiter, row and column counts, how many cells needed quotes, and any ragged rows.
Example: "a,b,c / 1,"x, y",3" to tab-separated → the quoted cell no longer needs quotes; to semicolon a cell "x;y" gets quoted; with quoting off, unsafe cells are counted and flagged.
Parse first,
then write.
Why a delimiter change is a parse and a write, not a search and replace.
Why not replace
Replacing every comma with a tab breaks any field that contains a comma inside quotes, and leaves the quotes in place that were only there because of the comma. The page parses the input with the RFC 4180 rules — quoted fields may hold the delimiter, line breaks and doubled quotes — then writes each field afresh for the new delimiter.
Quoting rules
“When needed” quotes a field only if it contains the output delimiter, a quote, a line break or leading/trailing spaces; “always” quotes every field; “never” writes fields bare and counts the ones that would not survive a round trip, so you know before you send the file somewhere. The input delimiter is detected from the first ten lines by counting candidates, or set explicitly.
What is not changed
Field contents are kept as they are unless you turn trimming on; ragged rows (a different field count) are reported, not padded or cut; empty lines are skipped by default. Line endings are written as LF or CRLF as chosen. Nothing leaves the browser; the same four anonymous usage counts as the rest of the site apply.
SOURCES
- RFC 4180 (CSV): fields containing the delimiter, quotes or line breaks are quoted and quotes doubled; leading/trailing spaces are quoted so they survive
Last reviewed 21 September 2026. How results are checked: How we verify.