What is the difference between TSV and CSV?

Both store a table as plain text, one row per line. CSV puts a comma between columns; TSV puts a tab. The practical win of TSV is that real text rarely contains tabs, so you almost never need quoting or escaping — a sentence with commas like 'Doe, John' breaks naive CSV but sits fine in TSV. That is also why copying a selection out of Excel or Google Sheets gives you tab-separated text, not commas. This tool defaults to the tab separator and turns each line into one JSON object.

How do I convert data copied from Excel or Google Sheets?

Select the cells in your spreadsheet, press Ctrl+C (or Cmd+C), then paste straight into the input box. Spreadsheets copy to the clipboard as TSV — a tab between every column, a newline between every row — so it lands here already in the right shape. Keep the header switch on if your top row holds column names like name, age, email, and you get a JSON array where each object uses those names as keys. No save-as, no file upload needed.

What happens if my data has no header row?

Turn off the 'first row is header' switch. The tool then treats every line as data and names the columns col_1, col_2, col_3 and so on, left to right. So a line like 42 blue true becomes {"col_1": "42", "col_2": "blue", "col_3": "true"}. This is handy for raw log dumps or machine output that ships values without labels. You can rename the keys later in your editor or with a quick find-and-replace.

Should I turn on automatic type inference?

Turn it on when you want numbers to be numbers. With inference off (the default), every value stays a string, so 42 becomes "42" — which is exactly right for IDs, phone numbers and zip codes where a leading zero must survive. Turn it on and 42 becomes the number 42, true and false become booleans, and an empty cell or the word null becomes JSON null. Pick off for fidelity, on for data you will do math on.

What if a field itself contains a tab or a line break?

Wrap that field in double quotes, the same way CSV does. The parser follows RFC 4180 rules but with a tab as the delimiter, so "a\tb" is read as the single value a b rather than two columns, and a quoted field may span multiple physical lines. A literal double quote inside such a field is written as two double quotes (""). If your fields never contain tabs or newlines, you can ignore quoting entirely.

Turn a copied spreadsheet selection into JSON

You have a chunk of rows in Google Sheets and an API that wants a JSON body. Select the cells, copy, paste here, leave the header switch on, and the column titles become object keys. Copy the pretty-printed array straight into your request and skip the save-as-CSV round trip entirely.

Seed a database or test fixture from a table

A colleague hands you a tab-separated dump of sample records. Paste it, turn on type inference so the numeric and boolean columns land as real numbers and booleans, and you have a ready-to-import JSON array for your seed script or a fixtures file your tests load.

Feed log lines into a JSON pipeline

A legacy job emits headerless tab-delimited lines. Turn the header switch off so the fields come out as col_1, col_2, col_3, then pipe the JSON into whatever expects structured records. You keep the raw values as strings, which is safer for IDs and timestamps.

Hand non-technical teammates a no-install converter

Someone in ops needs JSON but only knows Excel. Send them the link, they copy their cells and paste, and they get JSON without touching a terminal or installing anything. The result lives in their browser tab and nothing leaves their machine.

TSV to JSON Converter: Tab-Separated Values to JSON

Tab-separated data to JSON, header detection, type inference, quoted tab/newline fields, browser-only

Runs locally
Category Format Converter
Best for Turning pasted content or local files into a handoff-friendly format.

Output shapeFirst row is headerInfer types (number / boolean / null)

Input (tab-separated)

JSON

What this tool does

Free online TSV to JSON converter. TSV is the tab-separated cousin of CSV — it is exactly what you get when you copy a range straight out of Excel, Google Sheets or Numbers, because spreadsheets put a tab between columns and a newline between rows. Paste that block here and get back a clean JSON array of objects, with the first row read as field names. Turn the header switch off when your data has none and the columns become col_1, col_2 and so on. Flip type inference on and bare 42, true and null stop being strings and become real numbers, booleans and nulls; leave it off to keep every value as text, which is what you want for zip codes or IDs with leading zeros. Fields that themselves contain a tab or a line break work too — wrap them in double quotes and the parser reads them RFC 4180 style, just with a tab as the separator instead of a comma. Pretty-printed output, one-click copy, shareable URL. 100% client-side, nothing is uploaded.

Tool details

Input: Text + Numbers + Structured content; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: Shareable URL state; Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget: Initial JS <= 9 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Format Converter · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How TSV to JSON Converter fits into your work

Use it when the main problem is getting content from one practical format into another.

Conversion jobs

Turning pasted content or local files into a handoff-friendly format.
Previewing a conversion before you use it in a larger workflow.
Cleaning small format mismatches without opening a full editor.

Conversion checks

Try a small sample first when the source format is messy.
Check character encoding, separators, and line endings after conversion.
Keep the source until the converted output has been reviewed.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Turn a copied spreadsheet selection into JSON
You have a chunk of rows in Google Sheets and an API that wants a JSON body. Select the cells, copy, paste here, leave the header switch on, and the column titles become object keys. Copy the pretty-printed array straight into your request and skip the save-as-CSV round trip entirely.
Seed a database or test fixture from a table
A colleague hands you a tab-separated dump of sample records. Paste it, turn on type inference so the numeric and boolean columns land as real numbers and booleans, and you have a ready-to-import JSON array for your seed script or a fixtures file your tests load.
Feed log lines into a JSON pipeline
A legacy job emits headerless tab-delimited lines. Turn the header switch off so the fields come out as col_1, col_2, col_3, then pipe the JSON into whatever expects structured records. You keep the raw values as strings, which is safer for IDs and timestamps.
Hand non-technical teammates a no-install converter
Someone in ops needs JSON but only knows Excel. Send them the link, they copy their cells and paste, and they get JSON without touching a terminal or installing anything. The result lives in their browser tab and nothing leaves their machine.

Common pitfalls

Pasting comma-separated text and expecting columns. This tool splits on tabs, not commas, because that matches what spreadsheets copy. If your data uses commas, it is CSV — use the CSV to JSON tool instead, or convert the delimiter first.
Leaving type inference on for IDs with leading zeros. With inference on, 00042 is read as the number 42 and the zeros vanish. For zip codes, phone numbers and account IDs, turn inference off so every value stays a string.
Forgetting to turn off the header switch for headerless data. If your first real data row gets eaten as field names, you lose a record and your keys look like values. Flip the switch off and the columns become col_1, col_2 instead.

Privacy

Parsing, type inference and JSON formatting all run as plain JavaScript inside your browser tab. Your pasted table never reaches a server and nothing about it is logged. One thing to know: the shareable URL encodes your input in the query string, so a link pasted into chat will leave that data in the recipient server's access log. For anything sensitive, use the copy button and paste the JSON instead of sharing the URL.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Developer

Browse all tools for this role

TSV to JSON Converter: Tab-Separated Values to JSON

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How TSV to JSON Converter fits into your work

Conversion jobs

Conversion checks

Good next steps

Real-world use cases

Turn a copied spreadsheet selection into JSON

Seed a database or test fixture from a table

Feed log lines into a JSON pipeline

Hand non-technical teammates a no-install converter

Common pitfalls

Privacy

FAQ

YAML ⇄ JSON Converter

JSON Formatter & Validator

CSV ⇄ JSON Converter

TSV to CSV Converter

JSON to CSV Converter

CSV to TSV Converter

Angle Converter

Base64 Encoder & Decoder

Base64 to File Converter

BBCode to HTML Converter

Chinese Numeric Converter

Chinese Pinyin Converter