Question 1

What does "copy path" actually copy?

Accepted Answer

A dot-and-bracket path you can paste directly into JavaScript to reach that value, e.g. root.users[2].address.city for a nested field inside the third item of a users array. Object keys use a leading dot, array indices use brackets — the same syntax you would type to access that value in code.

Question 2

Does the search box match values, or only keys?

Accepted Answer

Both. Typing a key name highlights matching keys; typing a value (a string, number, or boolean) also matches nodes whose value contains it. Any branch containing a match is automatically expanded so you never have to manually open a path to find a hit.

Question 3

Will the tree view stay usable on a very deeply nested or very large JSON document?

Accepted Answer

Nodes are collapsed by default below the top level, so the initial render only has to draw what's visible — you expand branches as you need them rather than the whole tree rendering at once. Extremely wide arrays (tens of thousands of sibling items) will still be slower to scroll than a small document, since every visible row is a real DOM node.

Question 4

Can I view an array of primitives, not just objects?

Accepted Answer

Yes — a top-level array of strings, numbers, or booleans renders as indexed leaf nodes ([0], [1], [2]...) just like an array of objects would, and each one is still searchable and copyable.

JSON Viewer

Pro Tip

Collapsible Tree

Search Within Tree

Local Processing

Frequently Asked Questions