JSON to Table
Processed Client SideRender JSON as a clean Key / Value table. Expand nested objects and arrays inline to inspect their structure.
Bookmark this tool now — skip the search next time you need it.
About JSON to Table
This tool runs entirely in your browser. Whatever you paste is processed on your own device and is never uploaded, logged, or sent to any server.
Render JSON as a clean key and value table, with nested objects and arrays expandable inline so you can inspect their contents without losing your place in the parent. It suits the case where a tree is more structure than you need — you have a record and you want to read its fields the way you would read a row in a database client, one label and one value per line. Types are colour-coded, nested branches open in place, and a parse failure reports the line it happened on. It is often the fastest way to hand a JSON payload to someone who does not read JSON. A summary badge above the table names what you actually pasted — an array with its item count, or an object with its key count — which settles the first question anyone has about an unfamiliar payload.
Key features
- Key and value table layout, one field per row
- Nested objects and arrays expand inline without leaving the table
- Values colour-coded by type so strings, numbers, booleans, and nulls are distinguishable
- Reads a top-level object or array equally well
- Summary badge naming the top-level shape and its size, so an array of 200 records is distinguishable from a single object at a glance
- Collapsed branches labelled with their own item or key count, so you know what is inside before you open it
- Parse errors report the offending line number
- Handles large documents without a size limit or a server round-trip
- Syntax-highlighted input pane alongside the table
- Runs entirely in your browser — nothing you paste is uploaded
How to use it
- Paste your JSON into the input pane and click Parse.
- Read the fields as key and value rows.
- Click a nested object or array to expand it in place.
- Collapse it again to get back to the parent record.
Tips & common mistakes
- This is the view to use when showing a payload to someone non-technical — a labelled table reads as data, where raw JSON reads as code.
- For a record you want to read field by field, this beats a tree. For a document whose nesting is the thing you are studying, use the JSON Tree Viewer instead.
- It renders a table for viewing, not a spreadsheet file. To get an actual CSV out of an array of records, use JSON to CSV.
- Nested arrays of objects are where a key and value layout starts to strain — if most of your data looks like that, JSON to CSV or the tree views will serve you better.
- Expanding inline keeps the parent visible, which is the advantage over drilling into a tree when you are comparing a nested value against a sibling field.
- If the input will not parse, the JSON Validator reports the parser message with the line number.
- Check the summary badge before reading anything else. An endpoint that is documented as returning a list but reports a single object here is the explanation for a whole class of client-side bugs.
- The copy action gives you back formatted JSON rather than the table, which makes this a reasonable way to tidy a payload you pasted in minified — read it as a table, copy it as clean JSON.