JSON Array to HTML Table

The header row is built from the first element of the array. A key that appears only in later objects gets no column of its own, and an object missing a key simply leaves that cell blank. Normalise exports with a shifting field set before pasting — doing so also shows you exactly where the backend stops returning a field.

The value is placed into the cell as it is, so a nested object or array does not turn into readable text and you get an internal representation instead. The table view suits flat records. Flatten nested data into top-level keys before converting, or inspect the whole structure in the JSON Formatter and Validator, which shows the tree.

Yes, though not with a button: select the rendered table with the mouse, copy it, and paste into a sheet — spreadsheet apps split an HTML table from the clipboard into cells. If you would rather have a file than a clipboard, use the neighbouring JSON to CSV tool, whose output Excel and Sheets open directly.

The limit is your tab's memory, not a server quota. Hundreds of rows render instantly; thousands make scrolling visibly heavy, because every cell is a separate markup element. For a large export, paste the first couple of hundred elements to understand the shape and process the full volume with a script or a spreadsheet.

Find the array of records inside it — usually under data, items or results — and paste just that part, square brackets included. The outer object describes the response as a whole, mixing counters and pagination cursors with the payload, and there is nothing meaningful to tabulate at that level.

The table is built by a script in the open tab and the box contents are not transmitted anywhere; the page makes no network request carrying your text. Close the tab and the table is gone, with nothing stored. That is precisely why the tool offers no history and no shareable result link — there is nowhere to keep one.