Local spreadsheet workflows

Nested JSON to Excel without losing object boundaries

Nested JSON to Excel conversion here preserves each nested object or array as JSON text in one cell. It does not recursively flatten paths or expand an array into multiple spreadsheet rows.

This works well when you want one row per API record and still need to inspect its details. If you need separate city or tag columns for filtering, reshape the JSON into top-level properties before using the converter.

Create your XLSX workbook

Ready. Input stays in your browser. Limit: 20 MB per file or pasted input.

How to convert nested JSON to a worksheet

  1. Locate the records array in your response. Paste that array, or a wrapper with exactly one array property.
  2. Keep one object per record. A wrapper may contain non-array metadata, but two array properties make it ambiguous and are rejected.
  3. Convert to XLSX and download the Data sheet. Inspect nested fields as JSON strings in their cells.
  4. For filterable subfields, create top-level keys such as city or first_tag in your source data and convert the revised records again.

Example input and output

Input JSON:
{"records":[{"id":7,"address":{"city":"Austin"},"tags":["new","paid"]}],"total":1}

Data worksheet:
id | address           | tags
7  | {"city":"Austin"} | ["new","paid"]

The total metadata is not a column; tags stays in one cell.

Limitations to check first

Nested JSON is stored as a JSON string in a cell, not expanded into rows or dotted-path columns. A single object without an array property and arrays of primitives are rejected. The output is .xlsx only. Each JSON file or pasted UTF-8 input is limited to 20 MB; Excel worksheet limits and browser memory also apply.

Practical tips

Flatten only the fields you actually need for sorting. For example, replace address with a top-level city property if city is the analysis column. Preserve the original JSON separately because a missing value and null both become blank worksheet cells.

Frequently asked questions

Does this recursively flatten nested JSON?

No. Only top-level record keys become headers. Nested objects and arrays are serialized as JSON strings in cells, so one record stays one row.

Can I convert an API response with metadata?

Yes, if the response object has exactly one array property and that array contains objects. Other non-array metadata is ignored; multiple array properties are rejected.

How can I get one column per nested field?

Reshape your source JSON before converting. For example, move address.city into a top-level city key on each record. The tool has no flattening option.

Does an array field become multiple rows?

No. An array inside a record stays as JSON text in one cell. To get one row per array item, prepare an array of objects in that shape before conversion.

What are the output, privacy and size limits?

The tool creates a new values-only XLSX file locally in your browser; files are not uploaded. Each JSON file or pasted UTF-8 input must be 20 MB or smaller. Browser memory and Excel worksheet limits also apply.