Built for tabular data
Best for an “array of objects” where each row is one record. Preview, then download export.xlsx。
A single object is also treated as one row, but list APIs are the smoothest fit.
JSON to Excel
Processed locally You can also load data via #data={"name":"Ada"} or #url=... It is cleared from the address bar after it is read.
Convert between JSON and Excel tables. Turn list-shaped responses into filterable sheets, or turn an ops-maintained xlsx into JSON a program can read. Download happens in the browser. Files are not uploaded to our servers first.
Parsed locally
Files are read in the browser and not sent to our servers. Fits report samples that contain business numbers.
The first download loads the spreadsheet library and needs access to this site’s static assets.
Nested fields
Complex nesting may need flattening first, or export only the columns you care about. Flattened deep objects produce more columns.
Formulas are generally not kept; cell values are what matter.
Example
[
{ "sku": "A01", "stock": 12 },
{ "sku": "A02", "stock": 0 }
] two columns sku and stock, two data rows. Filter stock = 0 in Excel for out-of-stock items, then convert back to JSON if needed. Will a huge sheet freeze?
Limited by browser memory. For tens of thousands of rows, filter a slice in the spreadsheet first, then import.
Are formulas kept?
Cell values win. Excel formulas are generally not written into JSON as-is.
CSV or Excel?
Use xlsx when a non-technical colleague should open it directly. CSV is lighter for scripts and Git.
Can I download without a preview?
Download is disabled when there is no valid output. Convert first to build a preview.
Recommended workflow
- Paste an array of objects and click “Convert” to preview.
- Confirm column names, then click “Download xlsx”.
- Open in Excel / Numbers / WPS and spot-check a few rows.
- For huge row counts, split the file or export on the server.
xlsx is for sharing; CSV is for programmatic round-trips. You can try both here from the same JSON.