JSON Viewer

A formatted JSON document is readable in the way a phone book is readable: every character is there, and finding the one thing you want is still work. A tree is the right shape for the job — fold away what you do not care about and the structure becomes obvious in seconds.

Everything opens two levels deep, which is usually enough to see the shape of a response without being buried in it. From there, fold individual branches, or expand and collapse everything at once.

The filter searches keys and values together and keeps the path to each match visible, so you see where the matching thing sits rather than a disconnected list of results. Hiding the ancestors of a match would defeat the point of a tree.

Every node has a copy button that gives you its path — <code>root.users[0].name</code> — which is the expression you would write in code to reach that value. Reading a response to find out how to address something is usually the reason for opening it at all, so it is one click rather than a manual count through the brackets.

The whole document stays in your browser. API responses are exactly the kind of thing that carries tokens, email addresses and customer records, and none of it is transmitted anywhere.