FAQ
Can I edit or export from the tree view?
No, the tree is read-only. Use the JSON formatter to edit, then come back to inspect.
Will a very large JSON be slow?
Deeply nested or very large payloads can lag because rendering happens in the browser. Minify first if you only need to scan values.
Is the expanded state remembered?
No, it resets when you switch tools or reload.
About this tool
Rendering is manual: editing the box does not refresh anything, you click Parse to rebuild the tree. On a large document, paste first and click once — far cheaper than parsing on every keystroke, and it keeps typing smooth.
Nodes are expanded to three levels by default (depth 0, 1, 2); deeper nodes stay collapsed and show only {N items or [N items. Expand all / collapse all sit in the toolbar. The default matches the shape of a typical API response, where the branch you need is usually within the first two or three levels.
Strings longer than 80 characters are truncated with an ellipsis, and hovering shows the full value — truncation affects display only, never parsing. The status bar reports total node count and maximum nesting depth, which is a more reliable complexity measure than eyeballing the text. Tens of thousands of nodes will feel slow, because every node is built into the DOM at once with no virtual scrolling; collapse the big arrays first, or cut out the field you actually need.
The view is read-only: no editing, no deleting keys, no export. Edit with the JSON formatter and come back to inspect. Nodes are built with textContent, so a string containing <script> is displayed as text and never executed — pasting JSON from an untrusted source is safe here.