TabEdit
Open the editor
All conversions

JSON → TSV

Convert JSON to TSV online

An API response is rarely a clean rectangle. Some objects have keys the others do not, values are nested, and a table needs one shape. The conversion takes the union of every key as the header, so nothing is dropped just because it appeared late.

How to do it

  1. Paste or open the JSON. The top level must be an array of objects or an array of arrays; a single object is rejected.
  2. Check the header row. Keys appear in the order they were first seen, and every object contributes.
  3. Export as TSV, or keep editing first: reordering and deleting columns here is faster than doing it after the fact.

Do it in the editor

What usually goes wrong

  • Nested objects and arrays

    A table cell holds text. Nested values are serialised back to JSON inside the cell rather than being flattened into invented column names.

  • Missing keys

    An object without a key gets an empty cell, not a shifted row. This is the single most common way a hand-rolled conversion corrupts a file.

Newline characters inside a string value are preserved and quoted on export, so a multi-line description survives the trip. TSV downloads use UTF-8 and tabs; CSV downloads use UTF-8 and commas. Review the effective record line endings, BOM and final line break in the export dialog. Quotes are rebuilt, and mixed record endings become uniform. Unsafe output is blocked; explicit quoting conversion is offered when it preserves the table, and ambiguous input requires confirmation.