Overview
Switch between CSV → TSV and TSV → CSV with a single click, converting between comma-separated and tab-separated formats while correctly handling quoted fields - a comma inside a quoted CSV field, or a tab inside a quoted TSV field, is preserved as literal content rather than being misread as a delimiter. The parser and re-escaping logic is the same quoted-field approach already built for the CSV/JSON converter, generalized to accept either delimiter rather than being rewritten from scratch. Fields are only wrapped in quotes on output when they actually need it - when a field contains the target delimiter, a double quote, or a newline - keeping the output clean rather than quoting every field defensively. Useful when a tool or spreadsheet expects tab-separated input but your data is in CSV, or vice versa. Runs entirely client-side.
Best for: Converting a CSV export into the tab-separated format a specific tool or import expects
How to use this tool
- Pick a direction. Switch between CSV → TSV and TSV → CSV with a single click.
- Paste your data. Quoted fields containing commas, tabs, or quotes are handled correctly either way.
- Read the converted result. Output updates live, with row and column counts shown for a quick sanity check.
- Copy or swap. Grab the result, or use swap to feed it straight back in as new input.
Why use this tool
Real quoted-field parsing
A delimiter character inside a quoted field is preserved as content, not misread as a column break.
Only quotes fields that need it
Output stays clean - fields are only wrapped in quotes when they actually contain the delimiter, a quote, or a newline.
Works in both directions
One tool instead of two, whichever direction your data needs to go.
Row and column counts shown
A quick sanity check that the conversion picked up the shape of your data correctly.
Frequently asked questions
It's preserved exactly as-is - since a comma isn't the TSV delimiter, it doesn't need escaping in the output and the quotes around that field are dropped entirely unless the field also contains a tab, a double quote, or a newline, in which case it still needs quoting for the new delimiter's sake.
Some tools and import formats specifically expect tab-separated values - it's common in bioinformatics data formats, some database bulk-import tools, and any dataset where the values themselves are likely to contain commas, which would otherwise require quoting nearly every field in a CSV.
No - the header row is treated like any other row and converted the same way as the data rows beneath it, since both CSV and TSV are just delimited text without a special header marker. Whatever your first line contains carries through as the first line of the output.