JSON Tree Viewer

How this reads your output

The document is parsed and drawn as a tree. Nodes below the second level start collapsed, and each collapsed row shows what it contains — the number of items in an array, the number of keys in an object — so the shape of a large response is visible without expanding it. Hovering any row shows the path to that value in the notation you would use to reach it in code. The drawing stops at 5,000 nodes because past that a tree stops being a way to find anything, but the parsing and the counts cover the whole document.

What the results mean

Nodes

Every value in the document, at every level. A rough measure of how much there is to navigate.

Maximum depth

How deeply nested the document is. Deep nesting is the usual reason a response is hard to read as text.

Path

Shown on hover — the expression that reaches that value, ready to paste into code.

Top-level type

Whether the response is an object or an array. An API that returns a bare array is the common cause of code expecting a wrapper and finding none.

Common problems and fixes

The tree stops part way down a large file

Drawing is capped at 5,000 nodes. The counts above cover the whole document — for very large responses, filter server-side or extract the section you need first.

A number is not what my API sent

JSON numbers above 2^53 lose precision when parsed by JavaScript, which is every browser. IDs sent as numbers rather than strings are the usual victims.

It says invalid but looks fine

Trailing commas, single quotes and unquoted keys are all valid JavaScript and invalid JSON. The JSON formatter points at the exact line and column.

Frequently asked questions

More in DevTools

• ASCII Table ReferenceLook up any character’s ASCII code in every base.
• Number Base ConverterConvert a number between binary, octal, decimal and hex — exactly, at any size.