JSON to Table.

Convert JSON to a table online — free and private

A JSON to table tool turns structured JSON into a grid of rows and columns you can read, sort, and export. Paste a JSON array of objects above, press Build table, and each object becomes a row with columns drawn from your keys. Because it runs client-side, you can explore data without uploading it — and without the public share links some viewers create.

How to view JSON as a table in three steps

1. Paste your JSON into the input, or click “Load sample”.
2. Build the table — choose whether to flatten nested objects and how arrays expand.
3. Sort, filter, and export — click headers to sort, filter rows, then export to CSV, Excel, HTML, or Markdown.

Four exports, one table

Most JSON table viewers export to a single format. This one gives you four: download a CSV or Excel spreadsheet, or copy a ready-to-paste HTML table for the web or a Markdown table for docs and GitHub. Exports always match the current sorted and filtered view, so you ship exactly what you see.

Why a table beats reading raw JSON

A JSON array of objects is a table — it just does not look like one. Compare the same three records:

[
  { "id": 1, "name": "Ada",  "role": "admin", "active": true  },
  { "id": 2, "name": "Alan", "role": "dev",   "active": false },
  { "id": 3, "name": "Grace","role": "admin", "active": true  }
]

id │ name  │ role  │ active
───┼───────┼───────┼────────
1  │ Ada   │ admin │ true
2  │ Alan  │ dev   │ false
3  │ Grace │ admin │ true

With three records the difference is cosmetic. With three hundred, the table is the only one you can actually scan — and once you can sort by a column, the odd record that is breaking your code surfaces immediately instead of being buried a thousand lines down.

Records with different keys still line up

Real API responses are rarely uniform. If one record has a phone field and the others do not, a naive table either drops the column or shifts every row out of alignment.

Columns here are built from the union of every record's keys, and missing values render as empty cells. Nothing is silently dropped, and the grid stays aligned — which also makes the gaps visible, so you can see at a glance which records are incomplete.

Four exports from one table

Once your data is a table, you usually want it somewhere else. Export CSV for a spreadsheet or a data pipeline, Excel for a real .xlsx workbook with typed cells, HTML to drop straight into a page, or Markdown for a README, a pull request, or documentation.

For more control over any one of those, the dedicated tools go deeper: JSON to CSV for delimiters and column picking, JSON to Excel for multi-sheet workbooks, JSON to HTML table for Bootstrap and Tailwind class presets, and JSON to Markdown table for column alignment.

No share links, ever

This is worth calling out, because it is the norm elsewhere. Several popular JSON table viewers work by uploading your JSON and giving you a URL — and some of those URLs are public by default. An API response you pasted for thirty seconds to debug a bug can end up sitting on someone else's server, and occasionally indexed by Google.

Nothing here is uploaded and no link is ever created. The table is built in your browser, which is why there is also no file-size cap.

Why use this JSON table tool?

It flattens nested objects into parent.child columns, lets arrays expand into rows or collapse into a cell, and never sends your data anywhere. Need a specific format? Try JSON to CSV, JSON to Excel, or JSON to SQL. Learn more in our guide on how to convert JSON to a table.