Free JSON to Table Converter
Read JSON the easy way, as rows and columns. Paste JSON, scan values in a table instead of nested brackets, and spot missing or odd values fast.
Your input never leaves this device — the table is built entirely in your browser.
What JSON to table conversion does
A JSON document is easy for programs to read but hard for people to scan, especially when it holds a long list of similar records. A table view lays the same data out in rows and columns, so values line up and can be compared at a glance. Each record becomes one row, and each field becomes one column.
The view is most useful for arrays of objects, such as a list of products, users or orders from an API response. Reading across a row shows one record, while reading down a column shows how one field varies. Single objects are shown as a key and value table instead, with one row per field, which suits settings and single-record responses.
Nested data needs a compromise. An object or array inside a cell cannot also be a column, so nested values are shown as JSON text inside the cell. The table still shows that the nested data exists and what it contains, without hiding the rest of the row. The conversion runs in your browser, so pasted JSON never leaves your device.
How to view JSON as a table
Follow these steps to read JSON as a table:
- Paste your JSON into the input area.
- Read the table in the output area. Scan down each column to compare values, and across each row to check a single record.
- Look for empty cells, which show that a record has no value for that column, and for nested cells, which hold JSON text.
- Note anything that needs fixing, then make the change in the original JSON. Keep the original file as the source of truth.
- For a very long list, paste a smaller part first to check the shape of the data, then view the rest in parts.
Start with a complete, valid JSON document. If the input is cut off or has a syntax error, fix it first, because a table cannot be built from text that does not parse.
Worked example: two order records
This example shows two order records. The table keeps the simple fields as columns and shows the nested address as JSON text in its cell.
[
{
"order": 101,
"customer": "Marta",
"total": 49.99,
"paid": true,
"address": {"city": "Lisbon", "country": "PT"}
},
{
"order": 102,
"customer": "Liam",
"total": 12.5,
"paid": false,
"address": {"city": "Dublin", "country": "IE"}
}
]| order | customer | total | paid | address |
|---|---|---|---|---|
| 101 | Marta | 49.99 | true | {"city": "Lisbon", "country": "PT"} |
| 102 | Liam | 12.5 | false | {"city": "Dublin", "country": "IE"} |
Comparing the two rows is immediate: Marta paid more than Liam, and only Marta has paid. The address cells still carry the full nested data, in compact JSON form, for anyone who needs it.
With twenty records the same layout still works, because the columns stay fixed while rows are added below.
Rules, nested data and edge cases
Arrays of objects become rows, with object keys as columns. When records have different keys, a row simply has no value in the columns for keys it lacks, so empty cells mean a missing field, not a zero or an empty string. Check the original JSON before deciding whether a missing field is an error, since some fields are optional by design.
Nested objects and arrays are shown as JSON text inside cells, rather than expanded into extra columns. That keeps the table readable when nesting varies between records. A single object at the top level becomes a key and value table, with field names in the first column and values in the second.
Values keep their types: numbers appear as numbers, booleans appear as true or false, and null means no value. Number formatting from the source text, such as trailing zeros, may change when values are rendered. Very large arrays produce very long tables and may be slow, so inspect large files in smaller parts and confirm the shape of the data before viewing the whole file.
Common table-view mistakes
- Pasting JSON wrapped in quotes: if the whole document is inside one string, with escaped quotes, it is one string value, not a table. Unescape it first, then view the result as a table.
- Expecting nested data to become columns: nested objects stay as JSON text in cells by design. To inspect one nested field across all records, extract that field in the source data first.
- Treating empty cells as errors: an empty cell means the record has no such field. It is only a problem if the field is required for every record.
- Editing values in the table and expecting JSON to change: use the table to read and check data, and make changes in the original JSON file, which stays the source of truth.
- Pasting a huge file at once: a very long table is hard to scan and may be slow. View a sample first, then work through the file in parts.
- Using the table view for spreadsheet work: for sorting, filtering and formulas in a spreadsheet, convert the JSON with the JSON to Excel converter or the JSON to CSV converter on this site instead.
Frequently asked questions
Can I turn the table into a spreadsheet file?
The table view is for reading. To work with the data in a spreadsheet, use the JSON to Excel converter or the JSON to CSV converter on this site, which produce files suited to spreadsheet programs.
Why is nested data shown as JSON text?
Nested objects and arrays cannot fit the row and column layout without hiding other fields, so they are shown as compact JSON text in the cell. The full nested content is still visible, and the rest of the row stays readable.
What happens if rows have different fields?
Columns cover the fields present in the data, and a row with no value for a column shows an empty cell. An empty cell means the field is absent from that record.
What happens with a single JSON object?
A single object becomes a key and value table, with one row per field. That layout suits settings, profiles and single-record responses better than a one-row table with many columns.
What if my JSON is invalid?
Fix the JSON first, checking for missing commas, unmatched brackets and unquoted keys. The table can only be built from a complete, valid document.
Is my JSON uploaded when I view it as a table?
No. The table is built in your browser, and pasted JSON is not uploaded or stored.
Can the table show very large files?
Very large arrays produce very long tables and may be slow. Inspect a smaller part first to confirm the shape of the data, then view the rest in parts.



