Nested JSON to Excel - Flatten API Data for Spreadsheets
Last updated: 23 May 2026
API responses rarely arrive as a flat table. You get nested objects, arrays inside objects, and metadata next to record lists. Flattening nested JSON to Excel manually is slow and error-prone - this guide covers how automated flattening works and what to expect in your spreadsheet.
Flattening nested objects
With Separate columns mode, nested paths become column headers joined by dots, for example customer.address.city. That matches how analysts search and filter in Excel. Choose JSON in one cell when you want to preserve a subtree as formatted JSON text instead.
API wrappers (data, results, items)
Many APIs return { "data": [ {...}, {...} ], "meta": {...} }. The converter locates the main record array and ignores pagination metadata for the row set - see converting an API response to Excel for a worked example. Supported wrapper keys include data, results, items, records, rows, entries, payload, hits, and others. Nested envelopes like data.items are handled when the records live one level down.
Arrays in a row
Arrays of simple values (strings, numbers) appear as a single comma-separated cell, for example tags → a, b, c. Arrays of objects are kept as JSON text in one cell, so your row count stays predictable - the JSON array to Excel guide walks through that row-and-column mapping. When a file has two or more top-level lists of objects (for example orders and users), each list maps to its own Excel sheet.
JSON inside string fields
Webhooks sometimes store a second JSON document inside a string field. When flattening is enabled, those strings can expand into additional columns - useful for Stripe, Shopify, and custom event pipelines without a second parse step. The same flattening also turns nested government exports into clean columns - see converting GST JSON (GSTR-2A / GSTR-2B) to Excel.
Limits to know
Extremely deep nesting (dozens of levels) may hit safety limits. Very wide rows (thousands of unique keys) can produce large sheets. For production analytics, consider filtering fields at the source API when possible.
Frequently asked questions
- How do I convert nested JSON to Excel?
- Upload or paste your nested JSON, keep Separate columns mode on, preview the table, and click Download Excel. Nested objects are flattened into dotted column headers such as customer.address.city, so each value lands in its own column ready to filter and pivot.
- Can I flatten nested JSON to XLSX columns?
- Yes. With Separate columns mode, every nested path becomes its own column header joined by dots (for example user.address.city). If you would rather keep a subtree intact, switch to JSON in one cell and that object is written as JSON text instead.
- Is there a free nested JSON to Excel converter online?
- Yes, this nested JSON to Excel converter is completely free with no signup. It runs entirely in your browser, detects common API wrappers like data, results, and items automatically, and supports files up to 15 MB.
- How are arrays inside nested JSON handled?
- Arrays of simple values (strings or numbers) are joined into one comma-separated cell, for example tags becomes a, b, c. Arrays of objects are kept as JSON text in a single cell so your row count stays predictable, and when a file has two or more top-level lists of objects, each list becomes its own Excel sheet.
Related guides
- JSON to Excel
- NDJSON / JSONL to Excel
- Postman JSON to Excel
- API Response to Excel
- JSON to CSV vs Excel
- JSON Array to Excel
- MongoDB / Firebase to Excel
- GST JSON to Excel
- Best JSON to Excel Converter
- How to Open JSON
- JSON to Google Sheets
See all guides or the FAQ.