Q01
Should nested arrays become rows or cells?
Keep them as JSON text cells unless your data model explicitly defines one array item per worksheet row. This converter uses the safer cell-based behavior.
JSON to Excel
Convert JSON objects and arrays to XLSX
Data Format
🔒 100% client-side — your data never leaves this pageMaintained by ToolsKit Editorial Team•Updated: August 23, 2026•Reviewed: August 23, 2026
Page mode
JSON input
Quick conversion
Paste JSON, verify the table preview, then download a real XLSX workbook. Nested objects are flattened into dot-path columns by default.
100% client-side; your data is not uploaded
Excel preview
XLSX
Prepare a preview to verify columns, values, and row count before downloading.
Next step workflow
About this tool
Convert JSON objects, arrays of objects, or primitive arrays into a genuine Excel XLSX workbook directly in your browser. Nested objects can be flattened into dot-path columns, while nested arrays remain readable JSON text so records are not split unexpectedly. Preview rows and headers before download, customize the worksheet and file names, and preserve numbers and booleans as typed Excel cells. Files up to 10 MB can be processed without uploading your data to a server.
Direct Answers
Q02
When should I choose XLSX instead of CSV?
Choose XLSX when typed numbers and booleans, worksheet naming, and direct Excel compatibility matter. Choose CSV for smaller plain-text interchange files.
Failure Input Library
Failure sample 1
Bad input: An array field was treated as a row source without a defined join rule.
Failure: One record unexpectedly expands into many rows
Fix: Keep nested arrays as JSON text, or normalize them into a separate table before export.
Failure sample 2
Bad input: Objects in the JSON array do not share exactly the same keys.
Failure: Similar records produce missing cells
Fix: Review the union of preview columns; blank cells represent fields missing from that record.
Scenario Recipes
01
Export an API response for spreadsheet review
Goal: Create a review-ready workbook without changing record boundaries
- Paste the JSON response or upload its .json file.
- Keep nested-object flattening enabled and prepare the preview.
- Check headers, row count, and serialized array fields before downloading XLSX.
Result: A typed Excel workbook with stable rows and readable nested-field columns.
Failure Clinic (Common Pitfalls)
One record unexpectedly expands into many rows
Cause: An array field was treated as a row source without a defined join rule.
Fix: Keep nested arrays as JSON text, or normalize them into a separate table before export.
Similar records produce missing cells
Cause: Objects in the JSON array do not share exactly the same keys.
Fix: Review the union of preview columns; blank cells represent fields missing from that record.
Use It In Practice
JSON to Excel is most reliable with real inputs and scenario-driven decisions, especially around "Should nested arrays become rows or cells?".
Use Cases
- Use it to answer "Should nested arrays become rows or cells?" consistently during reviews.
- Use it to answer "When should I choose XLSX instead of CSV?" consistently during reviews.
- Run "Export an API response for spreadsheet review" to Create a review-ready workbook without changing record boundaries.
Quick Steps
- Paste the JSON response or upload its .json file.
- Keep nested-object flattening enabled and prepare the preview.
- Check headers, row count, and serialized array fields before downloading XLSX.
Avoid Common Mistakes
- Common failure: One record unexpectedly expands into many rows
- Common failure: Similar records produce missing cells
Frequently Asked Questions
What JSON structures can I convert to Excel?
You can convert one JSON object, an array of objects, an array of strings or numbers, and mixed arrays. A single object becomes one row, while primitive array items are placed in a value column.
How does the converter handle nested JSON objects?
Nested-object flattening is enabled by default. A field such as customer.name becomes its own Excel column. You can disable flattening in Deep mode to keep nested objects as JSON text.
What happens to arrays stored inside a JSON record?
Nested arrays are serialized as JSON text in one cell. This preserves the original record count and avoids guessing whether array items should become rows or columns.
Are numbers and booleans preserved as Excel cell types?
Yes. JSON numbers and booleans are written as numeric and boolean cells. Strings remain text, while null or missing values become empty cells.
Can I choose the XLSX file name and worksheet name?
Yes. Both names are editable. Invalid filename characters are replaced, and worksheet names are sanitized to Excel's 31-character limit and character rules.
What are the JSON-to-Excel size limits?
The browser tool accepts up to 10 MB of JSON and exports at most 50,000 rows and 200 columns per workbook. The on-page preview shows up to 30 rows and 20 columns, but the downloaded file contains all accepted data.
Is the generated file compatible with Microsoft Excel and Google Sheets?
The download is a standard XLSX workbook that opens in current Microsoft Excel, LibreOffice Calc, Apple Numbers, and Google Sheets import workflows.
Is my JSON uploaded while creating the Excel file?
No. JSON parsing, preview generation, and XLSX creation all run locally in your browser. Your input is not sent to a ToolsKit server.
Keep browsing