Turn JSON records into an Excel workbook you can review
JSON to Excel writes record-shaped JSON into a real .xlsx workbook with one worksheet. It is useful when recipients need a spreadsheet file instead of a text CSV.
When should you use it?
- Share API records with spreadsheet users.
- Prepare a workbook for manual review.
- Preserve booleans as typed cells where possible.
Example: JSON records become worksheet rows
The download is a real .xlsx workbook; the text here illustrates its columns and typed boolean cells.
[{"name":"Alex","active":true},{"name":"Sam","active":false}]name | active
Alex | TRUE
Sam | FALSEChoose a worksheet-friendly structure
Each record becomes a row and its fields become columns. A flat collection is easier to review than records containing several nested collections. If the JSON describes an order with many line items, decide whether the worksheet should have one row per order or one row per line item before converting. That choice changes the meaning of totals and repeated values.
Protect identifiers from spreadsheet number conversion
Excel cells have types, but numeric precision is still limited. This exporter keeps long or decimal number tokens as text and writes supported safe integers and booleans as typed cells. Formula-like strings also remain text. This helps retain an identifier exactly, although a text cell will not behave like a number in every formula. Review the workbook in the application that will receive it.
Move records into a real spreadsheet.
Export a true .xlsx file with column headers from the union of top-level JSON properties. Nested values remain JSON text in one cell.
Provide records
Paste JSON or open a local UTF-8 document.
Review the mapping
Safe integers and booleans become typed cells; other values stay text.
Download XLSX
Open the workbook in Excel or another spreadsheet application.
How do I download JSON records as a real Excel .xlsx workbook?
Paste record-shaped JSON into JSON to Excel and download the generated workbook. The first worksheet uses top-level keys as headers and each object as a row. This is a real ZIP-based .xlsx file rather than a CSV file with a changed extension.
JSON: safe integer and text identifier
json[{"name":"Alex","count":12,"account":"00123"}]count can be a numeric cell; account stays text because it is a JSON string with significant leading zeros.
What happens to formulas and very large numbers?
Formula-like text is written as text rather than executable spreadsheet formulas. Long or decimal numeric spellings may also be text to avoid changing their value; review cell types in the target spreadsheet.
What should you check before using the result?
The sheet is limited to 100 columns and 200,000 cells. Spreadsheet formatting does not make a lossless JSON archive; keep the original document for exact values and structure.
Why some numbers are text
Spreadsheets can round long integers and decimal values. The exporter writes only safe integers as numeric cells. Longer and decimal tokens are stored as text to preserve their spelling; formulas and formula-like strings are also text.
Tabular limits
Export supports up to 100 columns and 200,000 cells from an array of objects or one object. Missing properties become blank cells; null is written as text. It creates one worksheet named Data.
Technical reference: JSON syntax and interoperability · RFC 8259