JSON Viewer

Explore JSON as a collapsible tree.

Tree view
The tree appears here. Paste JSON or click Sample.

JSON Viewer – Explore JSON as an Interactive Tree

The JSON viewer turns raw JSON into a collapsible, color-coded tree. Paste an API response or open a .json file and browse it the way you browse folders: expand the branches you care about, collapse the rest, and click any value to see its full path.

Features

  • Collapsible tree with item counts for every object {n} and array [n].
  • Expand all / Collapse buttons to switch between overview and detail.
  • Click to inspect – the selected node shows its JSONPath, type, length, and formatted value.
  • Copy path or value in one click, ready for code, JSONPath queries, or documentation.
  • Color coding for strings, numbers, booleans, and null, so data types are obvious at a glance.
  • Live validation – syntax errors are reported with line and column; valid documents show object, array, key, and depth counts.

When a tree beats text

Formatted JSON is fine for small documents, but real API responses often run to thousands of lines with arrays of nested objects. In a tree you can fold an entire list away, jump straight into the third item, and see how deeply things are nested without scrolling. It's the fastest way to understand an unfamiliar API, debug a webhook payload, or check what a configuration file actually contains.

Paths you can reuse

Paths are written in JSONPath dot/bracket notation, like $.store.book[0].author. Most languages use the same shape: drop the $ and you have JavaScript property access. You can paste the path into the JSONPath Tester to query similar values across the document.

Need to search inside big documents? The JSON Navigator adds key and value search. To edit the data, use the JSON Editor.

Frequently Asked Questions

Click any node in the tree. The panel below the tree shows its JSONPath (for example $.store.book[2].title), its type, and its value, with buttons to copy the path or the value.

Yes. Open a .json file with the Open File button; it's read locally by your browser. Only expanded nodes are rendered, and very long arrays show the first 500 items per level, so even multi-megabyte files stay responsive.

[3] after an array means it holds three items and {5} after an object means it has five keys. They let you see the size of each branch without expanding it.

No. Parsing and rendering happen entirely in your browser, so you can safely inspect private API responses and exports.