TSV to JSON Converter
Converts tab-separated values to a JSON array, or JSON back to TSV. The delimiter is fixed to a tab -- no picker needed.
Private by architecture:
All processing is 100% client-side memory. Your data never leaves this browser tab.
TSV input
0 lines · 0 charsTSV
JSON output
0 charsJSON
About This Tool
"TSV to JSON" and "CSV to JSON" are different search queries for the same underlying problem, so this is a
dedicated page for the tab-delimited case -- it's CSV to JSON's parser and
stringifier with the delimiter wired to '\t' and the delimiter picker removed, since there's
only one correct choice here.
Need comma, semicolon, or pipe instead? Use CSV to JSON, which exposes all four.
Key Features
- Bidirectional conversion: one Direction dropdown (or the ⇌ swap button) switches between TSV → JSON and JSON → TSV.
- Optional header row: toggle whether the first row is field names or data.
- Type inference toggle: on by default; numeric, boolean, and null-looking cells convert to their native JSON type.
- Quoted-field handling: correctly parses tabs and newlines embedded inside quoted fields.
- File upload: load a
.tsvor.jsonfile directly instead of pasting.
Example
name age active Ada 30 true Grace 28 false
produces:
[
{ "name": "Ada", "age": 30, "active": true },
{ "name": "Grace", "age": 28, "active": false }
] Frequently Asked Questions
Is this different from the CSV to JSON tool?
Not under the hood -- it runs the same parser as CSV to JSON with the delimiter fixed to a tab character, so there is nothing to misconfigure. Use this page when your data is already tab-separated; use CSV to JSON if you need comma, semicolon, or pipe instead.
Why would data be tab-separated instead of comma-separated?
TSV is common for exports where field values routinely contain commas (database dumps, bioinformatics datasets, some spreadsheet "Save As" options), since a tab is less likely to appear inside a value than a comma is.
How are tabs or quotes inside a field handled?
Quote a field with embedded tabs or newlines in double quotes, exactly like CSV; a doubled double-quote ("") inside a quoted field becomes a literal quote.
What does "infer types" do?
When on, cells that look like a number, true/false, or null convert to that JSON type instead of staying strings.
