Private, local-first data tools

TSV to JSON

Convert tab-separated TSV files or pasted tables to JSON. Review delimiter detection, preserve identifiers and export objects, arrays or JSON Lines locally.

Processed in your browserNo account requiredEncoding and delimiter controlsIncomplete exports are blocked
JSON export options
Empty cells can be converted to null only when type inference is enabled.
Drop a file, paste data, load a CORS-enabled URL, or try the sample.
Rows0
Columns0
EncodingAuto
DelimiterAuto
Issue groups0

Open a data file to start

The parser runs off the main thread. Once loaded, you can search, sort, validate, repair and export without an account.

Compare the input and output

This synthetic table checks leading-zero IDs, punctuation and empty values. For Excel, use these values in a worksheet; for TSV, separate the three fields with tabs.

id	name	note
00123	Ada	A&B
00456	Grace	

Select objects with type inference off. Empty cells remain empty strings.

[
  {
    "id": "00123",
    "name": "Ada",
    "note": "A&B"
  },
  {
    "id": "00456",
    "name": "Grace",
    "note": ""
  }
]

Open the downloaded file in the destination and verify two records with identifiers 00123 and 00456.

What this tool does

TSV to JSON

TSV uses tabs between fields. Open the original file or paste a table copied from a spreadsheet. Verify that tab is selected before converting; spaces used to visually align a report are not tabs. Quoted delimiters and embedded line breaks must form valid delimited records.

How to use it

  1. Choose the source file and inspect the headers and column boundaries.
  2. Select the available settings or worksheet and check identifiers, empty cells and punctuation.
  3. Confirm the export row scope, download the result and inspect it in the destination.

Common tasks

  • Keep type inference off to retain strings such as 00123. JSON Lines writes one object per line rather than a surrounding array.
  • Inspect identifiers and empty cells before using TSV to JSON for a downstream import.
  • Choose the required records and download the TSV to JSON result without uploading local files.

Privacy and local processing

Local files are read by a dedicated browser worker and are not uploaded to an application server. File contents and filenames are not included in analytics events. Loading a public URL is an explicit direct request from your browser and may fail when the remote server blocks CORS.

Supported edge cases

  • Keep type inference off to retain strings such as 00123. JSON Lines writes one object per line rather than a surrounding array.

Frequently asked questions

Are local files uploaded?

Local files are processed in your browser. Loading a public URL makes a direct request from your browser to that URL.

What output limitations should I check?

Keep type inference off to retain strings such as 00123. JSON Lines writes one object per line rather than a surrounding array.