JSON to TSV
Turn JSON records into tab-separated values that paste straight into a spreadsheet or load into databases and scientific tools. Columns are collected from every object, nested objects become dotted columns or JSON text, and tabs, line breaks and backslashes inside values are escaped so every record stays on one line, as TSV requires.
- Runs in your browser
- No sign-up
- Free to use
How to use JSON to TSV
- Paste a JSON array of objects or JSON Lines.
- Choose how special characters and nested values are written.
- Keep or drop the header row.
- Copy the TSV into a spreadsheet or download it.
JSON to TSV features
Any JSON records
Arrays of objects, single objects or JSON Lines.
All columns
Union of keys across records.
Valid TSV
Tabs and line breaks escaped or replaced, so rows never break.
Nested data
Flattened to dotted columns or kept as JSON.
Paste-ready
Spreadsheets split the pasted text into cells automatically.
Local
Converted in your browser.
When to use JSON to TSV
- Pasting API results into Google Sheets or Excel.
- Loading JSON data with PostgreSQL COPY or MySQL LOAD DATA.
- Creating input files for command-line tools such as cut and awk.
- Sharing records in a format that opens in any text editor.
JSON to TSV FAQ
Why escape tabs and line breaks?
TSV has no quoting, so a tab inside a value would start a new column and a line break a new row. Escaping writes them as \t and \n, the convention used by databases and many tools.
When should I replace them with spaces?
When the file is meant for people or for spreadsheets, which do not decode escapes. Replacing keeps the text readable on one line.
How are nested objects handled?
Flattening writes {"dims": {"w": 20}} as a dims.w column. Arrays are always written as JSON text.
Can I paste the result into Excel?
Yes. Copy the output and paste it into a cell; Excel and Google Sheets split tab-separated text into columns.
Can I convert TSV back to JSON?
Yes, with the TSV to JSON tool.
Is my data uploaded?
No. The conversion runs in your browser.
Writing JSON as TSV
Tab-separated values are a natural target for JSON records that need to reach a spreadsheet, a database loader or a command-line tool. Unlike CSV, TSV needs no quoting rules: fields are separated by tabs and records by line breaks. The price of that simplicity is that values themselves must not contain tabs or line breaks.
The converter therefore takes care of special characters. In escape mode, a tab inside a value is written as \t, a line break as \n and a backslash as \, the convention understood by PostgreSQL’s COPY text format, MySQL’s LOAD DATA and many data tools. In replace mode, tabs and line breaks become spaces, which suits files read by people or pasted into spreadsheets.
Columns come from all records, so objects with optional fields still align, and missing values are written as empty fields. Nested objects can be flattened into dotted column names, which keeps each value in its own cell, or written as JSON text when the structure should be preserved; arrays are always written as JSON.
The input can be a JSON array, a single object or JSON Lines, and the output has a header row by default. Without the header, the file contains only data rows, which some loaders expect when column order is specified separately.
Because the result is plain text with tabs, it can be pasted directly into a spreadsheet: copy the output, click a cell and paste, and the values land in separate columns.