Have an array of objects — API results, exported records, a log dump — and need a real Excel workbook, not a
CSV detour through Excel's import wizard? Convert it to .xlsx in one click, entirely in your
browser.
Json Web Viewer's Excel export takes a JSON array of objects and turns each object into a spreadsheet row,
with each distinct field becoming a column — written as a real .xlsx workbook, not text pretending
to be one. Load the array into Table mode first to preview it as a grid — sort columns,
spot-check values, edit a cell — then export exactly what's on screen from the Save menu's
Excel (.xlsx)… option.
Nested objects and arrays inside a record don't fit a flat spreadsheet cell, so you get a choice: keep them as
raw JSON text in that cell, or turn on Flatten nested properties in Settings to spread nested
fields into their own dotted columns instead (address.city, address.country, and so
on). Numbers land as real numeric cells rather than text Excel has to re-interpret, and any value that looks
like a formula (starting with =, +, -, or @) is written as
inert text so a malicious cell in someone else's export can't run code when you open it.
Example — this JSON array:
[
{ "id": 1, "name": "Ada Lovelace", "role": "Engineer", "address": { "city": "London", "country": "UK" } },
{ "id": 2, "name": "Grace Hopper", "role": "Rear Admiral", "address": { "city": "New York", "country": "USA" } }
]with Flatten nested properties on, exports as a sheet with these columns:
id | name | role | address.city | address.country
1 | Ada Lovelace | Engineer | London | UK
2 | Grace Hopper | Rear Admiral | New York | USA
Open this example in the editor →
The link above pre-loads the array above into Table mode. From there, open Save in the
toolbar and choose Excel (.xlsx)… to export it.
No. The .xlsx file is built entirely in your browser and downloaded straight to your device —
your JSON and the resulting spreadsheet never touch a server.
A CSV is plain text with no cell types, formatting, or multiple sheets — opening one in Excel routes it
through an import wizard that can mangle dates, leading zeros, and locale-specific delimiters. The
.xlsx export writes a real Excel workbook directly: numbers land as actual numeric cells (not
text Excel has to guess at), so it opens correctly with no import step.
A spreadsheet cell can't hold a nested object, so by default a nested value is kept as its raw JSON text in
that cell. Table mode's "Flatten nested properties" setting can instead spread nested fields into their own
dotted columns (e.g. address.city, address.country) before export.
Prefer a plain-text file you can diff or pipe into another tool? See JSON to CSV instead.