TSV to JSON Converter

How TSV-to-JSON conversion works

TSV (Tab-Separated Values) is a flat text format where columns are separated by a tab character (\t) and rows by newlines. It's structurally identical to CSV, just with a different delimiter. The tab character is the key advantage: it almost never appears in real text, which means you rarely need quoting or escaping.

The converter reads your first row as column headers and maps those to JSON object keys. Every subsequent row becomes one object in the output array, with each cell value assigned to the corresponding key. After mapping, it runs a type pass: cells that look like integers or floats become JSON numbers; cells containing true or false (case-insensitive) become JSON booleans; everything else stays a string.

The result is a JSON array you can use directly in JavaScript without parsing strings after the fact. No extra transformation step.

Input and output — a concrete example

This is what the conversion looks like end to end. Notice that score becomes a number, is_active becomes a boolean, and location (which contains a comma) stays intact without any escaping.

user_id	location	is_active	score
101	Houston, TX	true	95.5
102	London, UK	false	88
103	Sydney, AU	true	

[
  {
    "user_id": 101,
    "location": "Houston, TX",
    "is_active": true,
    "score": 95.5
  },
  {
    "user_id": 102,
    "location": "London, UK",
    "is_active": false,
    "score": 88
  },
  {
    "user_id": 103,
    "location": "Sydney, AU",
    "is_active": true,
    "score": ""
  }
]

Row 3 has an empty score cell — two consecutive tabs. The key is still present in the output with an empty string value. Your application code decides whether to treat that as null, zero, or something else.

TSV vs CSV — when to use which

Both formats store tabular data as plain text. The difference is just the delimiter, but that choice has real consequences depending on what's in your data.

The practical rule: if your data includes addresses, descriptions, product names, or any free-text field that might contain commas, use TSV. If your data is purely numeric or tightly controlled (stock prices, sensor readings), CSV is fine and more universally supported by spreadsheet tools.

Where this converter gets used

TSV shows up in more places than people expect. Here are the scenarios where converting it to JSON saves real time.

How type inference works

By default, every value in a delimited file is a string. The converter runs a type pass so you get native JSON types instead of having to parse them yourself after the fact.

Strings with leading zeros (like zip codes 00123 or product codes 007) stay as strings — converting them to numbers would drop the leading zero and corrupt the value.

Known limitations

The converter handles the common cases well, but there are edge cases worth knowing before you run large or unusual datasets through it.

Frequently asked questions