JSON to Excel Converter

There is no file picker on this page — the input is a text box, so open the .json file in an editor or a browser tab, select all of it, and paste. Press Create Excel file and a download link for data.xlsx appears beneath the button. While the box is still empty, a link reading Use an example fills it with two records, which is the fastest way to see the shape being asked for before you go hunting through your own file. Editing the box afterwards clears the result, so the file you download always matches the text on screen rather than something you changed since.

That is the usual shape of an API response: an outer object carrying a status, a count and paging information, with the records under a key such as data, results, items or rows. Only that inner array converts here, so select from its opening square bracket to its closing one and paste that alone. A formatter makes this far easier than reading minified text — collapse the outer object, find the one key whose value is a list, copy it. At a terminal, jq .data file.json prints the same thing. Paste the wrapper as it stands and you are told plainly that it is not an array.

Because every value is turned into text before it is written, so a cell holding 1815 is four characters as far as the workbook is concerned. Excel usually marks these with a green triangle and a note that a number is stored as text. Clearing it takes a moment: select the column and either use that warning menu's convert option, or Data, then Text to Columns, then Finish on the first screen, which re-reads every cell. Dates deserve more care than numbers, because a value written as 07/08/2026 is read according to your regional settings and can quietly become a different day.

Not into columns, no — and no converter can manage it without inventing a rule about how deep to go and what to call the results. A cell holds one value, so a key whose value is another object comes out as the literal text [object Object], and a key whose value is a list comes out as its items joined with commas. One of those is still useful: a list of tags reads perfectly well as a comma-joined string. An object does not. Flatten before converting, giving each inner field a top-level key of its own, and what you get back is a sheet you can sort and filter.

A JSON Lines file holds one complete object per line, with no commas between them and no brackets around the whole thing — a common shape for logs and for anything written as it happens, because a writer can append a line without rewriting the file. As a document it is not valid JSON, so it is refused here. The conversion is mechanical: a square bracket at the top, a comma at the end of every line except the last, a closing bracket at the bottom. Any editor with multiple cursors does it in a few keystrokes, and at a terminal jq -s . file.jsonl performs the same wrap.

No. The text is parsed in the page by the browser's own JSON parser, the rows are assembled there, and the .xlsx is written there too, by a library the tab fetches and runs itself. The download link points at data held in your browser's memory rather than a file on a server, and it is released when you leave. That matters more here than for most conversions, because what people convert is API responses, database dumps and export files — customer records, order histories, email addresses. There is no account, no server-side limit on how much you paste, and no copy of the data anywhere but your own machine.

Two separate places do this, and both are worth knowing about. JSON is parsed by JavaScript, which holds numbers as doubles and carries only about fifteen or sixteen significant digits exactly, so a nineteen-digit order id written as a bare number is rounded before anything else touches it. Excel then applies a fifteen-digit limit of its own, and will show a long run of digits in scientific notation once it decides the cell is a number. The remedy is the same in both cases: long identifiers should travel as strings, in quotation marks, in the JSON that produced them. If you control the export, quote them at source.

The parser is the browser's own, which follows the specification strictly and forgives nothing. The recurring causes are a trailing comma after the last item in a list or object, keys and strings wrapped in apostrophes instead of quotation marks, comments, and an unescaped line break inside a string. Anything copied out of a JavaScript file usually fails on the first two, because JavaScript allows both and JSON does not. Copying from a terminal brings its own hazard: a response wrapped across lines by the terminal, or cut off where the scrollback ran out. When the message says the JSON is invalid, a formatter will point at the exact character.