Best on a larger screen. The editors have more room on desktop.

JSON Graph Visualizer

InteractiveIn-browser only
Graph
Drawing the graph…

Drawing the graph…

Every object and array becomes a node; keys and values stay inside it. Nothing leaves your browser.

Help

Visualise JSON as an interactive node graph — click any node to see its path. 100% in-browser.

01-03 Guide

How to visualize JSON as a graph

Paste JSON to see it as an interactive node graph: each object or array is one node, an array of records collapses into one schema card, and clicking a node gives you its JSONPath. Nothing leaves your browser.

  1. 01

    Paste, type, or upload JSON into the Source pane — it is parsed in your browser, never uploaded.

  2. 02

    Read the structure as a node graph: every object and array becomes a node, and its keys and values stay inside it.

  3. 03

    Click a node for its JSONPath, collapse branches you are not reading, search keys and values, then export SVG or PNG.

Built for reading structure

What the JSON graph gives you

Structure, not noise

Objects and arrays become nodes; their keys and values stay inside them. Your document shape is what you see, not one box per key.

The path is the navigation

Click any node for its canonical JSONPath, ready to copy into code, a jq query, or a bug report.

Search the whole document

Matching runs over the model, so a hit inside a collapsed or off-screen branch is still found and stepped to.

Collapse what you are not reading

Fold any branch, or every branch at once, to bring a large payload down to the part that matters.

Vector and raster export

Download the graph as SVG or PNG: every unfolded node, including those scrolled off-screen, drawn from the graph itself rather than screenshotted.

Honest about limits

Very large documents are drawn breadth-first against a device-scaled budget, and the graph says exactly how many branches it left out.

Technical Guide

What a JSON graph visualizer shows that a tree does not

A JSON graph visualizer draws a JSON document as connected nodes instead of indented text. In JSON iGraph, each object or array becomes one node that lists its keys and primitive values, and each nested object or array becomes a child node joined to it by an edge labelled with its key. The graph grows with the structure of your document, not with its number of keys.

A tree view, which is what most JSON viewers show, is an indented list: quick for reading one branch, slow for seeing how a large document fits together. The graph shows the overall shape, the depth and where the bulk of the data sits at a glance. Every node's address is its JSONPath in RFC 9535 syntax, so clicking a node gives you a path to paste into code, a query or a bug report.

How it handles real-world JSON

  • Arrays of 10 or more records collapse into one schema card that lists each field and its types, instead of one box per record.
  • Past 150 visible nodes the graph folds branches, so you open one level at a time, or use Expand all.
  • Very large documents are drawn breadth-first against a node budget scaled to your device, and the graph says how many branches it left out.
  • Parsing and graph building run in a Web Worker, so the page stays responsive while a big document loads.
FAQ

JSON graph questions

How does the JSON graph visualizer work?

Each object and array in your document becomes a node, and the keys and primitive values it holds are listed inside that node. Nested objects and arrays become their own nodes, joined by a labelled edge. That keeps the graph proportional to your document structure rather than its number of keys, so a flat object with 500 fields is one readable node instead of 500 scattered ones.

What is the JSONPath shown when I click a node?

Clicking any node fills the path bar with its canonical JSONPath, such as $.user.roles[0]. Click the path to copy it. Keys that are not plain identifiers are bracket-quoted automatically, so $['first name'] is always valid to paste back into code or a query.

Is my JSON uploaded to a server to render the graph?

No. Everything happens in your browser: parsing and graph building run in a Web Worker, and search, layout and export run in the page. Your JSON is never transmitted, logged, or stored, which makes the graph safe for production configs, API responses, and payloads containing credentials.

Can I export the JSON graph as an image?

Yes. Export as SVG for true vector output you can scale or edit, or as PNG for pasting into documents and tickets. Both include every unfolded node, including the parts scrolled off-screen, and both are drawn locally from the graph model rather than by screenshotting the page. Folded branches stay folded in the export, so use Expand all first to include the whole document.

How is a JSON graph different from a JSON viewer or tree view?

A tree view, which most JSON viewers show, is an indented, collapsible list: fast for reading one branch, hard for seeing how a large document fits together. The graph draws each object and array as a node joined to its parent, so the overall shape, the depth and repeated record structures are visible at once. JSON iGraph has both: the graph here, and a tree view in the JSON Formatter.

What happens with very large JSON files?

The graph expands breadth-first against a node budget scaled to your device, so the shallow structure you use to orient yourself is always drawn first. If a document exceeds that budget the graph tells you how many branches were not drawn rather than silently hiding them or freezing the page.

Can I link someone directly to a node in the graph?

Yes. Add a path query parameter to the URL — for example /json-graph?path=$.user.roles[0] — and the graph opens with that node selected, provided the same document is loaded.

Related JSON tools

Last updated