Convert delimited data between commas, semicolons, tabs and pipes. The source delimiter is detected for you, and the file is genuinely parsed and rebuilt rather than search-and-replaced — which is the whole point, because a comma inside a quoted field is part of the value, and replacing it blindly splits one field into two and shifts every column after it. Quoting is recalculated for the new delimiter, so fields that no longer need quotes lose them and fields that now contain the new delimiter gain them. This is the tool for a European export where semicolons separate fields because commas are decimal points, and for turning a CSV into a TSV you can paste straight into a spreadsheet. Whole folders convert at once and come back as a ZIP; nothing is uploaded.
| Delimiter | Where you meet it |
|---|---|
| Comma | The default almost everywhere |
| Semicolon | European exports, where , is the decimal point |
| Tab | Pasting into spreadsheets without a dialog |
| Pipe | Data full of commas and quotes |
Because a comma inside a quoted field is part of the value, not a separator. Replacing every comma turns that one field into two and shifts every column after it for the rest of the row — a corruption that often is not noticed until the import. The file has to be parsed and rebuilt, which is what happens here.
By counting each candidate outside quoted regions across the first several lines. Counting over raw text instead lets a comma inside a quoted semicolon-separated field win the vote, which is exactly how European exports get misread. You can also set the source manually.
They are quoted. Quoting is recalculated from scratch for the new delimiter rather than copied across, so fields gain quotes where they now need them and lose them where they do not.
Yes. A newline inside a value keeps its quoting whichever delimiter you choose, because an unquoted newline would end the row.
No. Parsing and conversion happen in your browser and nothing is transmitted.
Changing a delimiter is not a find-and-replace, and treating it as one is how data gets corrupted. A comma inside a quoted field is part of the value, not a separator, so replacing every comma turns one field into two and shifts every column after it. The file has to be genuinely parsed and then re-serialised. Detection counts candidate delimiters outside quoted regions across the first several lines rather than over the raw text, which is what stops a comma inside a quoted semicolon-separated field from winning the vote — precisely the case that breaks European exports, where the decimal separator is a comma and the field separator is a semicolon. On the way out, quoting is recalculated rather than preserved: a field that needed quotes under the old delimiter often does not need them under the new one, and a field that was safe before may now contain the new delimiter and need them. Quotes inside a value are doubled per RFC 4180, and embedded newlines keep their quoting in every case, because a bare newline inside an unquoted field would end the row. A UTF-8 BOM is stripped first so it does not end up inside the first header. Everything happens in your browser and no file is uploaded.