JSON Viewer

Paste JSON and explore it as a tree. Open what you need, search keys and values, and copy the path to anything you click.

Tree

The tree appears here.

Ctrl+Enter also works. Your JSON is processed in your browser and never sent to a server.

What the Tree Shows

Structure at a glance

Every object and array shows how many keys or items it holds, so you can see the shape of a response before reading it. Strings, numbers, booleans and null each have their own colour.

Search that opens the way

Type a key or a value. Every match is highlighted and every object around it is opened, even when it sits 3,000 items into an array.

Paths you can paste

Click a value to get its JSONPath and its JavaScript accessor, ready for a test assertion, a JSONPath query or your code.

Values exactly as written

Large IDs, trailing zeros and escape sequences are shown as they are in the file, and repeated keys are shown twice, not merged.

Viewer, Formatter or Validator?

All three read JSON with the same check, so they never disagree about whether a document is valid. Use this viewer to explore and find a value. Use the JSON Formatter when you need the text itself indented, minified or with sorted keys. Use the JSON Validator when you only need to know whether it parses, and JSON Compare to see what changed between two versions. When something is broken, the JSON error guides show the fix for each message, starting with unexpected token.

Frequently Asked Questions

How do I view a JSON file as a tree?
Paste the JSON into the box and press View JSON. Objects and arrays become rows you can open and close; each one shows how many keys or items it holds. Expand by level, expand everything on smaller documents, or search to open exactly the parts that match.
How do I get the path to a value?
Click any row. The panel under the tree shows its JSONPath (for example $.order.items[0].sku, the syntax standardised in RFC 9535 and used by many API and test tools) and the matching JavaScript accessor (data.order.items[0].sku), each with a copy button. Keys with spaces or quotes get bracket notation, so the path is always valid.
Why does this viewer show my large IDs correctly?
Many viewers read the document with JavaScript's JSON.parse, which turns an ID such as 12345678901234567890 into 12345678901234567000, because a JavaScript number cannot hold every integer past 2^53. This viewer keeps the text of every number as written, so IDs, prices like 49.90 and exponents like 1E2 appear exactly as they are in the file.
What happens with duplicate keys?
Both are shown, in the order they appear, and listed under the tree with their line numbers. JSON allows repeated keys but most parsers silently keep only the last one, which is a common source of configuration bugs.
Is my JSON uploaded?
No. Parsing and the tree run in your browser. Nothing you paste is sent, logged or stored, which makes it safe for API responses with tokens or customer data.
How large a file can it open?
Several megabytes. Only the open parts of the tree are drawn, and long arrays appear 100 items at a time with a button for the next batch, so a large document stays responsive. Expand all is offered up to 5,000 values; beyond that, open by level or search.
What if my JSON is invalid?
Nothing is shown until it parses. You get the line and column of the first error, a click that selects it, and a link to the guide for that error, from trailing commas to single quotes. The check is the same one the JSON Formatter uses.

Related Tools