View My JSON
Skip to main content

View My JSON · table

JSON to Table Converter

When JSON is a list of records, a table beats scrolling braces. Scan fields as columns in one click.

Array → rows

[
  { "id": 101, "name": "John", "email": "j@ex.com" },
  { "id": 102, "name": "Sarah", "email": "s@ex.com" }
]

Table columns: id | name | email — one row per object.

Why use this

  • Arrays of objects become rows
  • Scan columns instead of nested braces
  • Edit source JSON and refresh the table

When it helps

  • API lists of users, orders, or events
  • Comparing field values across many records

How to use it

  1. Paste an array of objects.
  2. Open Table view.
  3. Scan rows; switch to Cards or Tree for nested fields.

When a table fits and when it does not

A table is a good fit when your JSON is an array of objects that share most of their keys, like a list of users, orders or log entries. Each object becomes a row and each distinct key becomes a column, which turns a hunt through braces into a quick scan down one column. It is a poor fit for a single deeply nested object, such as a configuration, because there is no list of similar records to line up. For those, Tree or Cards read better.

Where the array lives

APIs rarely return a bare array. More often the records sit inside a wrapper, like { "data": [ ... ], "meta": { ... } } or { "results": [ ... ], "next": "..." }. The table you want is the one for the inner array, not for the whole response. If you see one row with two columns instead of the records you expected, look for the array inside and view that part.

Uneven and nested records

Real data is rarely tidy. One record has a phone field, the next does not, and a third has it as null. JSON treats a missing key and a null value as different things, and a table will show them as empty cells, so check the source if the difference matters to you. Nested objects and arrays inside a record, such as an address object, do not flatten neatly into one cell. They appear as expandable values, and the Cards or Tree view is better for reading them in full.

Types can also vary by row. A field that is a number in most rows and a string in a few often points to a data quality problem upstream, and a table makes that visible in a way raw JSON does not.

From table to something else

A table is for reading, and the original text remains the source of truth. If you want to share the data with someone who works in a spreadsheet, check what your destination expects before you copy; spreadsheets can reinterpret values such as long IDs or leading-zero codes. The JSON itself never changes when you switch views, so you can go back to the text to fix a value you noticed in the table.

A quick checklist

Before you trust a table, confirm three things. First, that you are viewing the array of records and not the wrapper around it. Second, that the number of rows matches the count you expect, for example the total in the response metadata. Third, that columns you care about are not empty simply because the key is spelled differently in some records, such as userId in some and user_id in others. Mixed naming is a common cause of apparently missing data, and a table shows it as two separate columns.

Core viewing, formatting, and validation run in your browser — no account required for those steps. Still strip secrets before pasting into any online tool. Details: privacy policy · about.

FAQ

Can I convert any JSON to a table?

Table view works best for arrays of objects. Nested objects may show as expandable values; use Cards or Tree for irregular shapes.

Related JSON tools

Guides in this cluster

More guides on the blog · Compare View My JSON with other tools