JSON to TSV Converter
Convert JSON to TSV in your browser, with no upload and no sign-up.
In-depth guide
JSON to TSV: tab-separated output, quoting and compatibility
How the converter writes tab-separated text from JSON records: column union, nested values, which cells get quoted (and why that goes beyond the IANA definition), line endings, and what to do when the receiver cannot read quotes.
Key figures at a glance
- Accepted input
- An array of objects, or one object
- Scalars, arrays of scalars, arrays of arrays and arrays containing null are rejected.
- Delimiter
- Tab between cells, line feed between rows
- No final newline is added.
- Source: IANA — text/tab-separated-values
- Quoting
- Only cells containing a tab, double quote or line break
- Commas and spaces never trigger quoting. Quoted cells use CSV-style doubling of ".
- Nested values
- Compact JSON text in one cell
- Because JSON text contains double quotes, such cells are quoted.
What goes in, what comes out
Paste JSON and the right-hand box shows tab-separated text, updating as you type. A Download link (converted.tsv) appears when there is output; nothing is uploaded. You can also copy the result and paste it into a spreadsheet, which typically places each tab-separated value in its own cell.
The input must be an array of objects or one object (a single row). The first line is the header. Example: [{"name":"Mei","city":"Singapore","age":30},{"name":"Ali","city":"Johor","age":25}] gives the following, where → stands for a tab:
name→city→age
Mei→Singapore→30
Ali→Johor→25
Other inputs (5, "text", null, [1,2], [[1,2]], [{"a":1},null]) stop with "Only an array of objects (or a single object) can become a table. Nested arrays have no rows and columns to map onto." An empty array gives empty output.
Columns and cell values
Columns are the union of all keys in first-seen order; a record without a key gets an empty cell ([{"a":1,"b":2},{"b":3,"c":4}] gives header a→b→c, then 1→2→ and →3→4). Integer-like keys come first, ascending, because that is how JavaScript orders object keys.
| JSON value | Cell |
|---|---|
| string | the text |
| number | JavaScript printing (1.50 becomes 1.5, 12345678901234567890 becomes 12345678901234567000) |
true / false |
true / false |
null |
empty cell (same as "") |
| object or array | compact JSON text, e.g. [1,2] |
Quoting: where this tool goes beyond the standard
The IANA registration for text/tab-separated-values says each record is one line, fields are separated by tabs, and fields that contain tabs are not allowable. It has no quoting at all. This tool needs some way to write values that contain tabs or line breaks, so it borrows the CSV convention: a cell containing a tab, a double quote, a line feed or a carriage return is wrapped in double quotes, with inner quotes doubled. Verified outputs:
| Value | Cell written |
|---|---|
has<TAB>tab |
"has<TAB>tab" |
say "hi" |
"say ""hi""" |
l1<newline>l2 |
"l1<newline>l2" |
a,b |
a,b (commas do not matter in TSV) |
pad |
pad (unquoted) |
array [1,2] |
[1,2] (no double quotes inside, so unquoted) |
object {"k":1} |
"{""k"":1}" |
A nested value that contains strings, such as ["a","b"], contains double quotes, so it is written as "[""a"",""b""]". A reader that does not understand quoting will show those quote marks literally. If your receiver is a strict IANA-style TSV reader, it will also be confused by cells with embedded tabs or line breaks; clean those values first or use another format.
Line endings are LF with no trailing newline, and non-ASCII text is written as is (the file is UTF-8 without a byte-order mark).
Formula safety
Cells are written as they are. A value that begins with =, +, - or @ can be treated as a formula when the text is pasted into a spreadsheet (OWASP calls this CSV injection and also lists a leading tab, carriage return and line feed). The tool does not neutralise them. If the data is untrusted, sanitise those values yourself, accepting that the data then changes.
Tip: Prefer TSV over CSV when your values contain many commas (addresses, sentences) and no tabs. Almost nothing needs quoting, which keeps the output readable and keeps naive splitters working.
Common mistakes
- Expecting
\twritten inside a string to appear as an escape; a real tab inside a value triggers quoting instead. - Feeding nested data and expecting columns; nested values stay as JSON text.
- Losing the difference between
nulland"". - Using a simple
split('\t')on output that contains quoted cells. - Passing an object whose values are the records; it becomes one row.
Related tools
Convert back with TSV to JSON, write comma-separated output with JSON to CSV, check the input with the JSON validator, or see the paths in your data with JSON to text.
Frequently asked questions
Is my data uploaded anywhere?
No. The conversion runs entirely in your browser using JavaScript. Nothing you paste leaves your device, is logged, or is stored on a server.
How large a document can it handle?
The limit is your browser's memory rather than any server quota. Documents of a few megabytes convert without trouble; very large files may make the page briefly unresponsive while it works.
What happens to nested data?
Formats that have no concept of nesting store nested values as a JSON string inside the cell, so nothing is silently discarded and the structure can be recovered.
Does it handle quotes and commas inside fields?
Yes. Parsing follows RFC 4180, so quoted fields containing commas, escaped double quotes, and line breaks inside a field are all read and written correctly.
Sources
- IANA — Media type text/tab-separated-values — Lines, tab separators, header line; fields containing tabs are not allowable.
- IETF — RFC 4180, Common Format and MIME Type for CSV Files — The quoting convention this tool borrows.
- IETF — RFC 8259, The JSON Data Interchange Format
This guide explains published rules in plain language. It is not financial, legal or official advice — rules change, so confirm with the agency linked above before you commit.