Skip to content
NDJSONTSV

Convert NDJSON to TSV Online

File Converter

Your files. The format you need.

Use Other Converter

Make your files fit.

Drop your files here, or choose them below.

Up to 50 files · Up to 100 MB per file

Loading converter…

GEEDITOR / NDJSON → TSV

About this conversion · NDJSON → TSV

Prepare NDJSON data as TSV for an importer or script. Match the destination’s expected delimiter, row structure and treatment of identifiers before exporting the full dataset.

Use an array of objects or an array of row arrays. Object keys become columns; missing values become empty cells. Nested objects and arrays become JSON text inside a cell, not extra columns. Normalize a deeply nested structure before importing it as a flat table.

CSV and TSV export prefix formula-like text with an apostrophe to reduce spreadsheet formula execution risks. Inspect such cells during import; the prefix is deliberate, not a missing character in the source.

Worked example
Input

{"id":"0012","name":"A, B","meta":{"size":"M"}}
{"id":"0013","name":"C"}

Output

id	name	meta
0012	A, B	"{""size"":""M""}"
0013	C	

How to convert

  1. Click “Choose files” and select the original NDJSON file. Start with one file when comparing settings.
  2. Check that the output selector shows TSV. The instructions here describe this choice; changing the output can change which settings apply.
  3. Click “Convert files”, then save the result from its file row. “Download all” puts completed files into a ZIP; it does not combine their contents.
  4. Open the TSV result and compare row counts, headers, empty cells, dates and identifiers with the NDJSON source. Preserve codes such as 00123 as text in the receiving application; do not assume its automatic type detection is correct.

Frequently asked questions

How are nested data and missing values handled?

Use an array of objects or an array of row arrays. Object keys become columns; missing values become empty cells. Nested objects and arrays become JSON text inside a cell, not extra columns. Normalize a deeply nested structure before importing it as a flat table. For JSON, use an array of objects or an array of row arrays; do not mix those row types. Nested objects are written as JSON text inside cells, not expanded into new columns. NDJSON needs one valid object or row array per nonblank line.

What should I check after converting NDJSON to TSV?

CSV and TSV export prefix formula-like text with an apostrophe to reduce spreadsheet formula execution risks. Inspect such cells during import; the prefix is deliberate, not a missing character in the source.