Most API responses are arrays of objects — lists of users, orders, products, and so on. A tree view is great for seeing the nesting, but when you want to compare values across records, a table is far easier to scan. This guide shows how JSON arrays map to tables, and how to convert one in seconds.
A table needs rows and columns. In JSON, an array of objects gives you exactly that: each object is a row, and each key is a column.
{
"users": [
{ "name": "Tom", "age": 30, "city": "Beijing" },
{ "name": "Jerry", "age": 25, "city": "Shanghai" }
]
}
Converted to a table, name, age, and city become the columns, and each user becomes a row.
Real data is rarely flat — objects often contain other objects. When you convert to a table, nested fields are flattened automatically using dot notation:
{ "name": "Tom", "addr": { "city": "Beijing", "zip": "100000" } }
This becomes two columns: addr.city and addr.zip. No code required — multi-level data is spread out into a two-dimensional table for you.
In the JSON formatter, it takes two steps:
.json file).It also handles two things for you automatically: