Skip to content

JSON Tree Viewer - Visualise JSON Structure Online

Explore JSON as a Tree

Paste JSON on the left and it is drawn as a tree on the right. Objects and arrays are nodes you can open and close, and strings, numbers, booleans and null are coloured differently so you can scan for the type you want. Each node shows its type, and collapsed nodes show their size, so orders with "250 items" stands out next to meta with "3 keys".

When a Tree Beats Formatted Text

Formatted JSON is fine until a response is a few hundred lines long. Then the structure you care about is spread over several screens, and it is hard to tell whether address belongs to the customer or to the shipment. In the tree you collapse the branches you do not need and keep the parent visible. Typical cases are paginated API responses where the data sits under data.items, Terraform state files, Elasticsearch results, and NoSQL documents with arrays nested inside arrays.

Copy Paths for Code

Every key copies its full path when clicked, in the same JSONPath format used by the JSON path finder: $.data.items[0].price.amount. Remove the $ for jq, or replace it with your variable name in JavaScript. If you need the data as indented text instead, use the JSON formatter, and to check a document that will not load, use the JSON validator.

Related Tools

Frequently Asked Questions

How do I expand and collapse nodes?
Click the arrow next to any object or array. The tree opens three levels deep when you paste, and deeper levels stay collapsed until you open them. A collapsed node shows how many keys or items it holds, such as "12 items", so you can tell where the bulk of the data is without opening it.
How do I get the path to a value?
Hover over a key to see its path, and click the key or the copy icon next to it to copy the path, for example $.orders[3].items[0].sku. Keys with spaces or hyphens use bracket notation: $["content-type"].
Can I search the tree?
Not in the tree itself. To find every path that contains a key or matches a condition, paste the same JSON into the JSON Path Finder, which lists all paths with a filter box and supports JSONPath queries.
How does it handle large files?
Collapsed nodes are not rendered at all, so a large document stays responsive as long as you open only the parts you need. Expanding an array with tens of thousands of entries will be slow, because each entry becomes a row.
Are large numbers shown correctly?
Yes. Integers above 2^53, such as 64-bit IDs, are parsed exactly and shown with all their digits, rather than rounded as JSON.parse would.