Swap tabs for commas so a TSV opens in a program that only reads CSV
Runs in your browser. Nothing you type is sent anywhere. Updated on 24 Oct 2026.The rows and the values are untouched; only the separator changes. Every value that contains a comma, a quote or a line break is wrapped in quotes on the way out, which is the part that hand-written find-and-replace gets wrong and then loses a column. Use it when the far end insists on a .csv file.
The page opens with TSV to CSV already chosen.
Paste tab-separated text, or a block of cells copied from a spreadsheet, into the input pane.
Check the Table preview to confirm every value sits in its own column.
Press Download CSV to save a .csv file, or Copy CSV to paste it elsewhere.
This converter moves structured data between JSON, YAML, XML, CSV, TSV, TOML and INI in every direction that makes sense: forty of the forty-two possible pairs. Paste the data or open the file and it works out which format it is from the content itself, not from the name on the end of it, then offers the conversion people usually want next. If the guess is wrong, one tap fixes it.
The difficult part is not parsing. It is being honest about shape. CSV and TSV are rows of columns; JSON, YAML, TOML and XML are values inside values; INI is one flat level of named sections. Moving between those shapes always decides something on your behalf, so every conversion prints one line saying what it decided: which list became the rows, which nested objects became dotted columns such as address.city, which keys were left out and why. A list inside a cell becomes JSON text rather than disappearing.
Excel is a way in and a way out rather than an eighth format. Open an .xlsx and one sheet is read in your browser and shown as CSV, so you can see exactly what will be converted; choose Excel in the To row and the result is saved as an .xlsx with typed cells, a bold header row and fitted column widths. XML to Excel is the common case: the repeating element becomes the rows, exactly as it does for CSV.
The rest of the article, and all 8 questions about Data Converter, are on the Data Converter page.
JSON, YAML, XML, CSV, TSV, TOML and INI, in forty of the forty-two possible directions. The two it refuses are CSV to INI and TSV to INI, because INI holds named sections and spreadsheet rows have no names, so every row would need an invented heading such as [row_1].
A spreadsheet needs rows, so the converter looks for the list that is the table. A JSON array of objects becomes one row per object. If the array sits inside an object, that array is used and the other top-level keys are named so you can see exactly what is not in the sheet. Nested objects become dotted columns such as address.city.
No, and the tool says so each time. YAML, TOML and INI allow comments; JSON, CSV and TSV have nowhere to put them, and nothing records which value a comment belonged to. XML comments go the same way. Everything else is kept, and anything that could not be written is named rather than quietly dropped.
Both. Drop or open a .json, .yaml, .xml, .csv, .tsv, .toml, .ini or .cfg file and it is read on your device. The format is worked out from the content rather than the extension, so a file saved with the wrong name is still read correctly, and the tool says when the name and the content disagree.
Still stuck? Ask about Data Converter and anybody who knows can answer. No account needed.
Same job, other tools: TSV to JSON – Convert tab-separated values, such as a paste from Excel, into JSON.
On the related tools: Convert Any File – Photos, documents, spreadsheets, archives: drop it and see what is possible.
In the collections JSON Tools · Developer Converters.