JSON to TSV Converter — Free Online JSON→TSV Tool

How to use

1. Paste or type your JSON into the left box — a sample is already loaded on first visit.
2. The right side updates live as you type (debounced ~250 ms), or press the Convert button.
3. Use Copy to copy the TSV to your clipboard, or Download .tsv to save it locally.
4. The output is tab-separated with CRLF line endings; commas inside fields need no escaping, and Excel, Google Sheets and Numbers all open it correctly.
5. The left input is remembered in your browser, so you can come back and keep editing.

What is it

JSON is a nested, typed data format used by APIs and programs, while TSV is a flat rectangular table with tab-separated columns, loved by both spreadsheet software and Unix text tools. This tool parses your JSON with the built-in JSON.parse and rebuilds it as TSV with the open-source papaparse library: an array of objects becomes a table with a header row, a single object becomes a one-row table, and scalar values become a single column. Nested objects are flattened into dot-notation headers (such as user.name) and nested arrays are stored as JSON text — so fields containing commas are never split apart by mistake.

Notes & fun facts

Here is a neat piece of trivia: TSV is as old as CSV, yet it became popular almost purely to solve one of CSV's embarrassments. CSV separates fields with commas, but the comma happens to be the most common punctuation in human language — addresses like "Wangjing Street, Chaoyang District, Beijing", product descriptions like "red, large", English sentences full of commas everywhere. So CSV had to invent quote-escaping rules: a field containing a comma must be wrapped in quotes, and quotes inside quotes must be doubled again — parsing gets messy and error-prone. TSV's idea is much simpler: separate fields with the tab character. Tabs almost never appear in everyday data, so the vast majority of TSV needs no escaping at all — what a column looks like is exactly what you get when you copy it. That is the beauty of what-you-see-is-what-you-get: as long as a field contains no tab, TSV needs no quotes, and parsers never have to guess which pair of quotes is the real boundary; quotes are only needed when a field truly contains a tab or a newline. That is why the old Unix tools cut, awk and sort naturally love tab-separated text; bioinformatics gene-expression matrices and machine-learning competition datasets also use TSV heavily — because gene names, sample names and annotation text often contain commas of their own, and comma separation would be impossible. In fact, you deal with it every day: when you copy a range of cells from Excel or Google Sheets and paste it elsewhere, the clipboard exchange format is often tab-separated text; many people first meet it when choosing "tab-separated" in the "save as text file" dialog of a spreadsheet. In data science, TSV is also regarded as the text table format least likely to go wrong, and many toolchains use it as their default interchange format. This tool is built for exactly this scenario: it flattens your JSON into a TSV table where however many commas a field contains, they will never be split apart — paste it straight into your spreadsheet.

Origin & history

TSV's roots go back to the punched-card era of the 1950s and 1960s, when early Fortran and COBOL programs already organized records with fixed-width fields or delimiters. In 1972, the FORTRAN textbook "A FORTRAN Primer" by E. I. Organick described exchanging data through comma-separated output, bringing CSV into the mainstream. But commas are too common in natural language, and as spreadsheets spread, the chaos of quote-escaping drove more and more programs to look for a more reliable delimiter. Because the tab character almost never appears in ordinary text, it became the natural choice: in 1993 the Internet Assigned Numbers Authority (IANA) formally registered the text/tab-separated-values media type — interestingly, the registration was done by the Gopher team at the University of Minnesota, and Gopher, the once-popular internet protocol of the early 1990s, itself used tab-separated text extensively in its server configuration and data files. TSV has had an official identity ever since. Through the 1990s and 2000s, the "export as tab-delimited text" option in spreadsheet software brought TSV into everyday office work; in the Unix world, commands like cut -d '\t', awk and sort made tab-separated text processing the norm; database exports, mail merge and gene-expression matrices (such as TCGA datasets) also adopted the format widely. In data science, many classic datasets ship in TSV, and both R's read.delim and Python's pandas.read_csv can read it in one line with the right separator. What is more, TSV, like CSV, is plain text — any editor can open it and version-control tools like Git can diff it line by line, which makes it especially popular wherever data needs human review. Today TSV remains irreplaceable in bioinformatics, machine-learning datasets and cross-system data exchange. The papaparse library used by this tool was open-sourced in the mid-2010s under the MIT license: it is one of the most widely used CSV/TSV libraries in the JavaScript ecosystem, zero-dependency, ESM-friendly, and serializes JavaScript objects to TSV entirely in the browser with no server round-trip.

Related keywords