JSON WORKSPACE
JSON Tree Viewer
Explore a bounded server-derived JSON tree.
Input is processed on this site only when you run the tool. The application does not save inputs or results.
input.json
Result result.json
A little clarity goes here.
Run the tool to see your result.
Result preview
UTF-8 text, at most 65536 bytes per input. Tab leaves the editor. Plain text disables syntax colors. Browser textareas may normalize line endings to LF.
{"inspect":{"inputMode":"text","options":[],"inputLabels":[],"inputLimits":[]}}{"inspect":{"input":"{\"project\":\"Example\",\"items\":[1,true,null]}","options":[]}}A QUICK WALKTHROUGH
A familiar workflow,
with room to focus.
Paste a valid JSON document with unique object keys.
Inspect to receive a server-derived tree and exact token metadata.
Expand containers; Copy and Download retain your input JSON. Source data exposes the node records.
When to use JSON Tree Viewer
Explore a nested JSON fixture when following member paths is easier than scanning indentation in a long response.
Read the result
The tree is derived by PHP and retains original scalar tokens. Expand containers for structure; Copy and download in the tree view retain your input JSON; switch to Source data to inspect or export the server’s node records.
SEE IT IN PRACTICE
Worked examples
Sample input. A result you can inspect.
Inspect example
Input
{"project":"Example","items":[1,true,null]}Expected result
{"nodes":[{"path":"","depth":0,"name":null,"type":"object","token":"","children":2},{"path":"/project","depth":1,"name":"project","type":"string","token":"\"Example\"","children":0},{"path":"/items","depth":1,"name":"items","type":"array","token":"","children":3},{"path":"/items/0","depth":2,"name":"0","type":"number","token":"1","children":0},{"path":"/items/1","depth":2,"name":"1","type":"boolean","token":"true","children":0},{"path":"/items/2","depth":2,"name":"2","type":"null","token":"null","children":0}]}{"kind":"tree","title":"JSON tree","nodes":[{"path":"","depth":0,"name":null,"type":"object","token":"","children":2},{"path":"\/project","depth":1,"name":"project","type":"string","token":"\"Example\"","children":0},{"path":"\/items","depth":1,"name":"items","type":"array","token":"","children":3},{"path":"\/items\/0","depth":2,"name":"0","type":"number","token":"1","children":0},{"path":"\/items\/1","depth":2,"name":"1","type":"boolean","token":"true","children":0},{"path":"\/items\/2","depth":2,"name":"2","type":"null","token":"null","children":0}],"total":6,"copyInput":true,"schema":1}Formats, limits and common errors
Fix JSON syntax or duplicate keys, or reduce the number of nodes.
- All JSON root types; at most 64 container levels, 10,000 parsed values and 1,000 result nodes. Excess is rejected. The interactive preview shows up to 500 nodes; Source data retains the complete result.
- Paths are JSON Pointers; scalar tokens preserve numeric spelling and Unicode escapes. Member labels are escaped text. Duplicate keys are rejected to keep paths unambiguous.
- The browser only presents returned nodes. It does not parse or process your input JSON.
- Input: 65,536 UTF-8 bytes per text field. Output: at most 524,288 UTF-8 bytes; serialized responses have a separate 1 MiB ceiling. Size/work failures return no partial result.