JSON Viewer

Read a large payload without editing it. Collapse, search, copy any path.

Input
Tree

About this tool

Explore a JSON document as a collapsible tree. Large payloads stay readable: collapse what you are done with, expand what you are comparing, and the search box finds keys and values anywhere in the document — collapsed parts included.

Every node has a Copy path action producing a JSONPath expression ($.users[0].name) that works in the JSONPath tester and in most libraries. A click on a scalar shows its full value without the tree moving.

The tree is built in a background thread from the same engine the validator uses, so a multi-megabyte payload opens without freezing the tab — and the document never leaves it.

How to use it

  1. Paste your JSON, or drop a .json file onto the input pane.
  2. Use the search box to find keys or values; matches highlight and the tree expands to them.
  3. Click any node label to copy its path; click a value to see it in full. The stats bar shows nodes, depth and size.

Worked example

The sample renders as service, version, endpoints and limits branches — endpoints expands to two path nodes, each with its methods array. Clicking a path label copies $.endpoints[0].path.

A config, walked

Frequently asked questions

How large a document can it show?
The parse and tree build run off the UI thread, so tens of megabytes open without freezing. Very wide documents render only the branches you expand — a 100,000-item array shows a summary node until you open it.
What path format does Copy path give?
JSONPath: $.users[0].name. It is the closest thing to a standard path language for JSON, and the expression works as-is in the JSONPath tester and in most JSONPath libraries.
Does search look inside collapsed nodes?
Yes — search runs over the whole tree, then expands and highlights the path to each match. Collapsing is a display state, not a filter.
Can I edit in the viewer?
The viewer is read-only by design: exploring a payload is a different job from editing one, and mixing them is how values get changed by accident. Copy the path or the value out, edit in the formatter.
Is my data uploaded anywhere?
No. The tree is built in your browser; a dropped file is read locally and never leaves the tab.