Use the free JSON to TSV Converter below: your data never leaves your browser — all work happens on your device, and nothing is uploaded to any server.
What this tool does
Data moves between programs in different formats, and the wrong format blocks the whole job. JSON is the format of web apps and APIs, but spreadsheets speak a different language: rows and columns separated by tabs. When you need to open API data in a spreadsheet, or hand a data export to someone who works in Excel or Google Sheets, you need to convert JSON to TSV. The JSON to TSV Converter does that conversion in your browser, with no upload and no account.
TSV stands for tab-separated values. Each row of your data becomes one line, and each field is separated by a tab character. Spreadsheets open TSV files directly, splitting each line into columns at the tabs. That makes TSV a simple, reliable bridge between the world of JSON and the world of spreadsheets, and it avoids the comma problems that plague CSV files when your data itself contains commas.
How to convert your data
Paste a JSON array of objects into the input box. An array of objects looks like this: [{“name”: “Ana”, “city”: “Madrid”}, {“name”: “Luis”, “city”: “Lima”}]. Each object is one row, and each key becomes one column. Press Convert, and the TSV appears in the output box, with the keys as the first line and one row per object after it. Press Copy TSV to copy the result, or Download TSV to save it as a .tsv file you can open in any spreadsheet.
If your data has objects with different keys, the tool collects every key it finds and uses the full set as columns. Rows that lack a key get an empty cell in that column, so no row loses its place. If your input is not a valid JSON array of objects, the tool tells you plainly, so you can fix the brackets or commas and try again. A common fix is wrapping a single object in square brackets, since the tool needs an array, not one bare object.
Why TSV instead of CSV
CSV uses commas to separate fields, which breaks when your data contains commas, as addresses, descriptions, and titles often do. CSV files handle this with quote marks, but different programs handle those quotes differently, and the result is a familiar mess: columns that split in the wrong place and data that lands in the wrong cell. TSV avoids the problem, because tab characters almost never appear inside real data. A tab-separated file is therefore far more likely to open correctly the first time, in any spreadsheet program.
TSV is also easier to inspect by eye. Tabs create clean columns in a plain text editor, while comma files blur into a run of text. When you need to check a conversion quickly, TSV lets you scan down a column and spot a missing value at once. For data that will be opened in a spreadsheet, TSV is the safer, simpler choice in most cases.
Common uses
Developers use this conversion to inspect API responses in a spreadsheet, where sorting and filtering are easier than in a raw JSON view. Analysts use it to turn a web export into a table they can chart. Shop owners use it to turn an order export into a stock list. Researchers use it to turn survey responses into a table for analysis. In each case, the job is the same: take structured data from a program, and make it readable in a table.
The tool handles everyday data shapes well: names, numbers, dates as text, true and false values, and empty fields. It does not flatten deeply nested objects into separate columns, because nested data rarely maps cleanly to a flat table. If your objects contain nested objects, consider flattening them first, or accept that the nested value will appear as text. For flat, table-shaped data, which is the vast majority of exports, the conversion is exact.
Tips for a clean conversion
First, check that every object uses the same key spellings. “Name” and “name” are different keys to a converter, and they will become two columns. Fix the spellings in your JSON before converting, and your table will come out clean. Second, keep numbers as numbers and dates in one format, so the spreadsheet can sort them correctly after import. Third, open the TSV file with the spreadsheet’s import step rather than double-clicking, when your program offers a choice, so you can confirm that tabs are the separator.
Fourth, save the original JSON as well as the TSV. The JSON is the exact record; the TSV is a working copy for the spreadsheet. If a spreadsheet edit goes wrong, you can always reconvert from the JSON. Fifth, if your data contains tabs inside a field, replace them before converting, since a tab inside a field would split that field into two columns.
Privacy and limits
Your data never leaves your browser. The conversion runs on your device, using the PapaParse library when it loads and a built-in converter as backup. That matters when your data contains customer names, order details, or internal figures. You can convert sensitive exports without sending them to a server, and without wondering who else might see them.