View My JSON · 3d
JSON 3D Viewer
Sometimes 2D trees run out of space. A 3D explorer lets you orbit nested structure and spot clusters of keys.
Structure worth orbiting
{
"app": "shop",
"services": {
"orders": { "db": { "host": "o1", "pool": 10 }, "cache": { "ttl": 60 } },
"users": { "db": { "host": "u1", "pool": 5 } },
"search": { "index": { "shards": 3, "replicas": 1 } }
}
}In 3D, app sits at the root and services spreads into three branches. You can see that orders is the bushiest branch, filter to just that subtree, and read the depth and type counts in the Insight panel.
Why use this
- Orbit nested structure in 3D
- Spot clusters that a flat tree hides
- Return to Cards / Table for precise values
When it helps
- Very deep nesting where 2D trees feel cramped
- Presenting structure visually to non-authors of the payload
How to use it
- Paste JSON into View My JSON.
- Open the 3D explorer (Pro).
- Orbit and zoom; switch views when you need exact values.
What the 3D explorer is
The 3D explorer turns a JSON document into a node-and-link model you can orbit, zoom and click. It is a Pro feature in View My JSON, so the free tools, which include Cards, Table, Tree and the 2D Graph, are the place to start. Reach for 3D after you have already validated the document and want a different kind of overview.
Reading nodes, depth and colors
Each node is a value: an object, array, string, number, boolean or null, each with its own color. The root is the top of the hierarchy and depth increases as you move away from it. The default layout is a stable tree, which is best for JSON because it keeps parents above children. Force layouts, top-down, left-right and radial, let the nodes push against each other and can show clusters, though positions then change between layouts, so do not read meaning into exact coordinates.
Node size can follow type, subtree weight or depth. Weight is handy: the biggest blobs are the branches holding the most content. Labels can be set to automatic, all, selected or none, and turning them off helps when the scene gets crowded.
Focus, filter and insight
Clicking a node opens an inspector with its path, depth, parent and children. From there you can focus on the node's neighbors, its path from the root, or its whole subtree, and everything else fades or hides. You can also hide types, so showing only containers removes the leaves and exposes the skeleton. A search box finds nodes by label, path or preview.
The Insight panel summarizes the document: max depth, a count by type, a depth histogram and the heaviest nodes, and you can copy those stats. It is a quick way to answer how big and how deep before you commit to reading anything.
When 3D helps and when it does not
It helps when you want to understand the overall shape of a heavily nested configuration or an API tree, or show that shape to someone who did not write it. Seeing which branch is heavy is hard from an outline.
It does not help for reading values. Labels in a 3D scene overlap, depth perception makes exact comparison unreliable, and anything with a lot of nodes turns into a dense cloud. On large documents, the depth control and the focus modes are what keep it usable, and what you see may not be every node. Use Table or Tree when you need exact values, and the editor when you need the full text.
Where your data goes
The explorer builds the scene from the JSON already loaded in the app, in your browser. No account is needed to use the free views, and a Pro unlock is what turns on 3D, Charts and Compare.
Your JSON stays in your browser
For core viewing, formatting, and validation, View My JSON parses and renders locally:
- Paste JSON
- Browser parses locally
- Render Cards / Table / Tree locally
- No account required for core tools
FAQ
When should I use a JSON 3D viewer?
Use 3D when nested depth makes trees hard to navigate, or when you want a spatial overview before drilling into values.
Is the JSON 3D viewer free?
3D explorer is a Pro feature. Free tools still include Cards, Table, Tree, Format, and Validate.
Related JSON tools
- JSON Graph ViewerWhen nesting is deep, a graph shows relationships you miss in a vertical tree.
- JSON VisualizerVisualization means more than pretty print. See shape, relationships, and records — not only indented braces.
- JSON Tree ViewerDeep configs bury values. A tree lets you expand only the path you care about instead of scrolling a formatted dump.
- Online JSON ViewerRaw braces are hard to read. View My JSON turns JSON into UI so you can understand APIs, configs, and logs faster — one workspace, not five tabs.
Guides in this cluster
More guides on the blog · Compare View My JSON with other tools