English
العربية
Deutsch
Español
Français
Italiano
Português
Русский
Türkçe
Tiếng Việt
JSON to TSV Converter
Convert JSON to tab-separated values for pasting straight into a spreadsheet.
Copy a block of cells out of Excel and paste it somewhere else, and what actually moves through your clipboard is tab-separated text. TSV is not an obscure alternative to CSV — it is the format spreadsheets speak natively when you copy and paste.
The one problem TSV mostly avoids
CSV’s biggest headache is that its delimiter, the comma, shows up constantly inside real data: prices, names with suffixes, addresses. Every one of those fields then needs quoting, and every quote mark inside the data needs escaping. It works, but it is fiddly, and a lot of hand-written CSV in the wild gets it wrong.
A tab character almost never appears inside ordinary data. Nobody types a tab into a product name or an email address. So converting JSON to TSV sidesteps the entire quoting problem for the vast majority of real-world values, which is the main reason the format exists at all.
TSV versus CSV, in practice
| CSV | TSV | |
|---|---|---|
| Delimiter | Comma | Tab |
| Needs quoting for typical text | Often, for commas and quotes | Rarely |
| Pastes cleanly into a spreadsheet | Usually, but commas can misalign | Yes, this is its native format |
| Formal specification | RFC 4180 | No single formal standard |
| Readable in a plain text editor | Fairly | Columns often misalign visually |
Converting JSON to TSV
- Paste your JSON array of objects into the converter.
- Convert it — each object becomes one tab-separated row, each key becomes a column.
- Copy the output directly.
- Paste it into a spreadsheet cell A1; the tabs will land each value in its own column automatically.
- No need to configure a delimiter on import, which CSV sometimes requires.
JSON to TSV questions
Why choose TSV over CSV for a spreadsheet paste?
Because pasting works immediately with no import dialog. Spreadsheet applications treat tab characters as the native cell separator for clipboard data, so a TSV block dropped into a sheet splits into columns on its own.
Can a tab character still appear inside my data?
It is possible but rare, since tabs are not something people normally type into a name, price or address. When it does happen, a proper converter still needs to escape or remove it, the same way CSV must handle a stray comma.
Is TSV standardised the way CSV is?
Not to the same degree. CSV has RFC 4180 as a widely referenced specification; TSV has informal conventions that vary slightly between tools. For most flat data this rarely causes a problem in practice.
What happens to nested JSON objects?
The same flattening rules apply as with any tabular export: nested objects get dotted column names, and arrays get joined or expanded, because TSV is just as rectangular as CSV underneath the different delimiter.
Is the conversion done locally?
No. Your JSON is sent to the server for conversion, but it is not retained once processed.
