Free Online JSON Tree Viewer With Copyable Paths
Read a JSON document as a collapsible tree in your browser instead of scrolling through formatted text. Every branch shows how many keys or items it holds before you open it, searching opens the branches that match, and clicking any value copies the path to it ready to paste into code.
Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.
How to Use JSON Tree Viewer
Step by step, start to finish.
An API response copied out of a browser is the usual case, and pasting is quicker than saving a file first.
The tree starts open to two levels. Each closed branch says how many keys or items it holds, so you know whether it is worth opening.
Type a key or a value and the branches containing a match open themselves. Searching is useless if you still have to go looking.
The path comes out as $.items[0].sku, ready to paste into code or into the path tester.
Key Features
What this tool does, and what it does not do.
Open to a depth, open everything, or close it all, with counts on anything closed.
Matching branches open themselves, so a match is shown in context rather than merely reported.
Click a value for its path, quoted correctly when a key has a space or a dot in it.
Null, empty string, empty array and empty object are drawn differently, because they mean different things.
Only open branches exist in the page, so a document that freezes other viewers stays usable.
Responses full of tokens and personal data are read in this tab and never sent anywhere.
About JSON Tree Viewer
Formatting JSON and reading JSON are different problems, and most tools only solve the first. A pretty printed API response with fifteen thousand lines is still fifteen thousand lines, and finding the one field you care about means scrolling, or searching and then counting braces to work out where you are.
A tree solves it by letting you not look at most of the document. The important detail is the counts: a closed branch that says four thousand items tells you not to open it, and a closed branch that says two keys tells you it is safe. Without them you open everything, which puts you back where you started.
The other thing people actually want from a viewer is the path. The reason you are exploring a response is usually to write code against it, and what you need is the exact expression for one value. Clicking a value and getting $.data.items[0].attributes.name is the difference between a viewer you look at and a viewer you use, which is also why keys with awkward characters are quoted properly rather than joined with dots and hoped for.
Frequently Asked Questions
Common questions about this tool.