JSON Array Extraction Explained
How the tool recursively finds arrays under object paths and turns each into a table.
Real-world JSON is rarely a flat array. This article explains how arrays are discovered inside nested objects and how each one becomes its own table.
Recursive path detection
The tool walks every object value. When it meets an array, it stops and registers a table named by the dotted path to that array — for example data.orders or data.raw.listv2. It does not look inside array elements for further arrays, so nested arrays stay as JSON strings in a cell.
Top-level arrays
If the entire input is an array, it becomes a single table named root. This is the simplest case and works for a plain list of objects or primitives.
Multiple arrays at once
When several arrays exist at different paths, each becomes a separate tab. You can switch tabs to preview each table, and download them all into one XLSX with one sheet per array.
Edge cases
Empty arrays still produce a tab so nothing is silently dropped. Objects that contain no arrays at all return a clear "no list found" message instead of a misleading single-row table.