JSON to Excel moves values, not the whole workbook
An API dump is JSON and you want to filter it in a spreadsheet.
An array of objects becomes rows. A single object uses its first array property. Nested lists of unknown length will not become a clean sheet.
Dates and extra sheets after JSON to Excel
If the converter says the JSON must be an array of row objects, flatten the export first. Dates and leading zeros need a look after Excel opens the file.
A related step, if you still need one, is Excel to JSON.
When JSON to Excel is the right page
JSON to Excel sits on this site because JSON and XLSX are not interchangeable, even when they look similar in a file list. An API dump is JSON and you want to filter it in a spreadsheet. Developers convert JSON when a payload must become a sheet, XML, or CSV. Spreadsheets, charts, and CSV exports start here for most offices in 2026.
An array of objects becomes rows. A single object uses its first array property. Nested lists of unknown length will not become a clean sheet.
What you give up by leaving JSON
JSON is the text format APIs and web apps use. It can nest, which a single spreadsheet cannot. Nested lists of unknown length will not become one tidy sheet.
Keep the original payload until you have checked the shape of the output.
What you gain, and do not gain, with XLSX
The download has to be XLSX, because that is the format the next step named. Spreadsheets, charts, and CSV exports start here for most offices in 2026. Values, dates, and several sheets can travel when the tool writes a real workbook.
Afterward, check dates, leading zeros, and whether a second sheet was left behind.
A test that matches the real file
Start from the question the other software asked. If it asked for XLSX, JSON to Excel is the matching page. If it asked for something else, switch tools instead of hoping a similar extension will pass. An API dump is JSON and you want to filter it in a spreadsheet. An array of objects becomes rows. A single object uses its first array property. Nested lists of unknown length will not become a clean sheet. The limit is the part people skip, and it is the part that decides whether the download is usable. If the converter says the JSON must be an array of row objects, flatten the export first. Dates and leading zeros need a look after Excel opens the file. The file stays in your browser and is not uploaded. The limit is 100 MB. Keep the original until the download has been opened in the program that will use it. Check three things in the download: it opens, the JSON material you cared about is still there, and the file size or the layout is what the form described. A new extension alone is not those three things. If a portal, a teacher, or a client rejects the file, send them the original JSON as well when you are allowed to. JSON to Excel is a convenience copy. It is not a new master. Spreadsheets break at quiet places: a second sheet, a date that changed, a leading zero that vanished, a comma inside a name. After JSON to Excel, open the result in a text editor as well as Excel. Excel guesses types and hides the delimiter. The workbook you calculated in is still the master.
Here is the decision for JSON to Excel. You start with JSON and you stop when a real program accepts XLSX. A list of similar objects maps cleanly to rows. A conversion aimed at CSV or JSON flattens that richness. Charts and macros are not the point. If those two sentences describe a tradeoff you do not want, do not convert. Renaming the extension by hand will not do this job. Running the tool twice on its own output will not do it either.
If the converter says the JSON must be an array of row objects, flatten the export first. Dates and leading zeros need a look after Excel opens the file.
A related step, if you still need one, is Excel to JSON.
Other jobs start from the homepage, where each tool is named for the conversion it actually does.