Step 1 / source
Choose the source
Drop one file here
Choose the flat json record array you want to turn into utf-8 tsv table.
Checking publication status...LOCAL DATA CONVERTER / JSON TO TSV
JSON to TSV
Project a flat JSON record array into UTF-8 tab-separated columns without flattening nested values or guessing spreadsheet types.
Processed in this browserOne UTF-8 .json file up to 5 MB. The root must be a non-empty array of flat scalar objects within 50,000 records, 200 columns, 1,000,000 cells, and 20 MB output.
JSON - flat record array
No file upload
This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
Original stays unchanged
The converter creates a separately named output. It never writes back into the source file.
Bounded work
One UTF-8 .json file up to 5 MB. The root must be a non-empty array of flat scalar objects within 50,000 records, 200 columns, 1,000,000 cells, and 20 MB output.
Plain-language method
How JSON to TSV works
Nirmion validates one array of objects, builds a stable union of property names in first-seen order, preserves string, number, boolean, and null values as cell text, quotes tabs and line breaks, and writes one object per row.
- 01Choose a valid source
Each array item must be an object whose values are strings, numbers, booleans, or null. Flatten nested objects and arrays before conversion.
- 02Review the conversion choices
Keep formula protection enabled for spreadsheet destinations. It applies only to text that starts with a formula trigger.
- 03Inspect the separate result
The TSV starts with the union header row and ends in _nirmion_tools.tsv. Missing or null properties become empty cells.
Useful when
Practical jobs this tool handles
- Inspect application records in a tabular editor.
- Prepare JSON fixtures for a TSV import.
- Create a diff-friendly table from flat API data.
Before converting
Check the source and destination rules
- Confirm the root is an array.
- Flatten nested properties before conversion.
- Compare object count with the reported output rows.
Know the boundary
Know what the destination format cannot keep
TSV cannot distinguish null from a missing property and cannot preserve nested JSON structures or original numeric types. Use JSON when those distinctions matter.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
Are nested objects flattened automatically?
No. Automatic flattening can create ambiguous column names, so nested values are rejected.
How are headers ordered?
By the first appearance of each property across the source records.
Are booleans retained?
Their values are written as the text true or false.