Convert JSON to TSV for spreadsheet handoffs

When TSV is better than CSV

CSV and TSV solve the same table problem with different delimiters. If your data contains many commas in names, addresses, notes, or lists, TSV can be easier to review as raw text. If your data contains tabs, TSV still needs quoting and a careful import check.

The export should start from an array. If your JSON root is an object with records at a nested path, create a query result first and export that array. The CSV guide covers the same row-shaping problem with comma-delimited output.

Copyable TSV example

This example starts with a realistic root object, then selects the array at .inventory.items. The shaped array includes a nested object, a literal tab inside one value, and a missing nested value. Nested object fields become path columns; the tab-containing cell is quoted.

{
  "inventory": {
    "items": [
      {"id":"sku-1","name":"Desk, oak","warehouse":{"bin":"A\t7"},"qty":12},
      {"id":"sku-2","name":"Lamp, brass","qty":5}
    ]
  }
}

.inventory.items

[
  {"id":"sku-1","name":"Desk, oak","warehouse":{"bin":"A\t7"},"qty":12},
  {"id":"sku-2","name":"Lamp, brass","qty":5}
]

id	name	warehouse.bin	qty
sku-1	Desk, oak	"A	7"	12
sku-2	Lamp, brass		5

Export and import

1. Open the JSON source locally in JSON All-in-One.
2. Select or query the array that should become rows, such as .inventory.items for the example above.
3. Choose Export, then TSV.
4. Save the file with a .tsv extension so the receiver has a useful hint.
5. In the spreadsheet or database import flow, choose tab as the delimiter and review text columns before accepting automatic type detection.

Tabs and newlines are data too

A tab inside a JSON string is not a separator chosen by the exporter; it is part of the cell value. The output quotes that cell so the row still has the right number of columns. Newlines can also exist inside quoted cells, which means a raw line count is not always the same thing as a record count.

If your receiver cannot handle quoted tabs or multiline cells, reshape the value first. For example, replace tabs with spaces or project a shorter note field before exporting.

A practical review is to open the saved file in a plain text editor before importing it. Turn on visible whitespace if your editor supports it. You should see one tab between ordinary cells, quotes around any cell that contains a tab or newline, and the same number of logical fields in each record.

TSV does not remove spreadsheet coercion

TSV avoids comma ambiguity, but it does not stop a spreadsheet from converting dates, long IDs, or formula-like text. Treat cells beginning with =, +, -, @, tabs, or newlines as spreadsheet-sensitive; a value such as @danger or -42 may be apostrophe-prefixed for safer import.

That protection is a safety behavior, not a guarantee that the receiving app will preserve every value exactly. Review the imported table, especially identifier, amount, and date columns.

Choose another format when needed

Choose CSV for a comma-delimited handoff, Markdown table for documentation, or HTML table for a report people will read in a browser.

If the receiver wants records instead of a table, TSV is the wrong shape. NDJSON keeps every row as JSON, a better match for pipelines that already work with nested objects.

• Compare all JSON export formats
• Export a documentation table
• Export a browser-readable table