Reading large payloads
A formatted file is readable, but a 3,000-line API response is still hard to navigate. The tree view shows each object and array as a row you can fold, with a count of its children, so you can collapse everything and open only the branch you care about.
Click any key to copy its path in JavaScript notation (for example $.data.items[3].price). The same path works in code as data.items[3].price and maps directly to JSONPath and jq (.data.items[3].price).
Frequently asked questions
What does the path format mean?
$ is the root. .name steps into an object key, [0] into an array index, and ["odd key"] is used for keys containing spaces or symbols. It is valid JSONPath and nearly identical to JavaScript property access.
Can I search inside the tree?
Yes. The filter box matches keys and values (case-insensitive) and automatically opens the branches that contain matches.
Why are strings and numbers different colours?
The viewer colour-codes types — strings, numbers, booleans and null — so you can spot a number sent as a string ("42" vs 42), a frequent bug in API integrations.
Is there a size limit?
No fixed limit. Branches start collapsed below the second level, so even large documents render quickly; expanding a node with thousands of children renders the first 500 and lets you show more.