View My JSON
Skip to main content

View My JSON · graph

JSON Graph Viewer

When nesting is deep, a graph shows relationships you miss in a vertical tree.

A small nested document

{
  "company": "Acme",
  "teams": [
    { "name": "Platform", "lead": { "name": "Ira", "level": 5 } },
    { "name": "Mobile", "lead": { "name": "Sam", "level": 4 } }
  ]
}

The graph has a root node for company and teams, one node for each team, and a smaller node hanging off each team for its lead. The two lead nodes have the same shape, which is easy to see in a graph and easy to miss in a long outline.

Why use this

  • Spatial map of keys and values
  • Complement to Tree — pick the view that fits
  • Same paste as your editor and table

When it helps

  • Large object graphs where tree depth feels endless
  • Demoing structure in a meeting

How to use it

  1. Paste JSON into View My JSON.
  2. Open the Graph view.
  3. Pan and explore; switch to Tree or Cards for detail.

What the graph shows

Graph view draws your JSON as a node and link diagram. Objects and arrays become boxes, their primitive fields are listed inside the box, and lines connect each box to the containers nested within it. The point is shape. You can see at once where a document fans out into many children, where it goes deep, and where two branches are built the same way.

Reading nodes and depth

Start at the root and follow the lines outward. A box with many lines leaving it is a wide object or a long array. A long chain of single boxes is deep nesting. Click a node to open its values; you can copy a value from the inspector, and long strings are shortened on the node itself but available in full there.

You can switch the layout direction between left to right, top to bottom, and the two reverse orders, and a Fit button recenters the view. Sliders for depth, array items and object keys control how much of the document is drawn. Depth is the number of levels below the root; lowering it is the fastest way to get a clean overview.

Where a graph beats a tree

A tree outline is a good tool for finding one thing. A graph is better at explaining how things relate. When you are tracing which object owns which array, comparing the layout of repeated branches, or walking a colleague through an unfamiliar payload, a picture they can see all at once is easier than watching you expand and collapse folders. Uneven nesting, where one branch is deep and the others are shallow, also stands out.

Where it struggles

Graphs are poor at precise reading. They are not designed for looking up the fifteenth item in a long list or comparing a column of values; Table does that better. Arrays of many similar records turn into large piles of near-identical boxes. And the canvas has a limit on how much it will draw, so for large inputs the app shows a projected window of the data and says so with a badge. If it reports that the projection is too dense, lower the depth, array and key sliders, or use Tree or Cards. The complete JSON is still in the editor either way.

Empty objects have nothing to draw, and data that cannot be serialized as JSON cannot be graphed at all.

Free, and local

Graph is one of the free views in View My JSON, alongside Cards, Table and Tree, and it needs no account. Parsing and drawing run in your browser. If you want a spatial, orbiting version of the same structure, the 3D explorer is a Pro feature.

Your JSON stays in your browser

For core viewing, formatting, and validation, View My JSON parses and renders locally:

  1. Paste JSON
  2. Browser parses locally
  3. Render Cards / Table / Tree locally
  4. No account required for core tools

FAQ

Is JSON graph free?

Yes. Graph is one of the free views, alongside Cards, Table, and Tree. Charts, 3D, and Compare are Pro.

Related JSON tools

Guides in this cluster

More guides on the blog · Compare View My JSON with other tools