Step 1 / source
Choose the source
Drop one file here
Choose the header-based tsv table you want to turn into json record array.
Checking publication status...LOCAL DATA CONVERTER / TSV TO JSON
TSV to JSON
Convert a rectangular header-based TSV file into a formatted JSON record array with explicit empty-cell handling.
Processed in this browserOne UTF-8 .tsv or .tab file up to 5 MB, 50,000 records, 200 columns, 1,000,000 cells, and 20 MB output.
TSV - 50,000 records
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 .tsv or .tab file up to 5 MB, 50,000 records, 200 columns, 1,000,000 cells, and 20 MB output.
Plain-language method
How TSV to JSON works
The converter parses a rectangular tab-delimited table, normalizes blank or duplicate headers to stable unique property names, maps every non-empty data row to one object, applies the selected empty-cell rule, and serializes one standard JSON array.
- 01Choose a valid source
The first row must contain column names. Quoted tabs and line breaks are accepted when quotes are balanced.
- 02Review the conversion choices
Omit creates smaller objects; Null keeps a stable property shape. Indentation affects only whitespace.
- 03Inspect the separate result
The result ends in _nirmion_tools.json. Source cell values remain strings because TSV carries no dependable type metadata.
Useful when
Practical jobs this tool handles
- Prepare a TSV export for an API fixture.
- Turn a database text extract into record objects.
- Review empty-cell behavior before an import.
Before converting
Check the source and destination rules
- Verify the first row is the header.
- Choose the empty-cell contract expected downstream.
- Convert numeric strings explicitly in the receiving system if required.
Know the boundary
Know what the destination format cannot keep
All non-empty values remain JSON strings. The converter does not guess numbers, dates, booleans, or nested structures because regional and identifier values are easy to corrupt.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
Why is 0012 a string?
TSV does not say whether it is a number or an identifier, so the source text is preserved.
What happens to duplicate headers?
They receive stable numeric suffixes rather than overwriting another property.
Are blank rows included?
Rows with no values are skipped.