JSON Viewer

A JSON viewer renders a JSON document as an interactive, collapsible tree instead of a wall of text. Each object and array becomes a node you can expand or collapse, every key is colour-coded by type, and every value carries the JSON path that points to it. It is the fastest way to navigate large or deeply nested API responses, configuration files, and database documents.

The formatter rewrites your JSON as pretty-printed or minified text. The viewer parses the JSON and presents it as a tree you can fold, filter, and copy from. Use the formatter when you need to ship clean text; use the viewer when you need to explore structure, find a value, or extract a path.

Type into the filter box at the top of the tree. The viewer hides any node whose key, value, or descendants do not contain your search term, so matching branches stay visible in context. The match is case-insensitive and works on keys, string values, numbers, booleans, and null.

Yes. Hover over any node and click the small path label on the right. The path is copied to your clipboard in dot/bracket notation — for example $.store.book[0].title — ready to paste into JSONPath, jq, lodash.get, or your own code.

Yes. Hover over an object or array and click the copy icon. The entire subtree is copied as pretty-printed JSON, which is handy for extracting one branch of a large response without manually selecting nested brackets.

No. Parsing, filtering, and rendering all happen entirely in your browser using JSON.parse. Nothing is uploaded, logged, or stored, which makes the viewer safe for inspecting API responses, JWT payloads, configuration files, and other sensitive data.

Yes. The tree renders synchronously and collapses everything below depth two by default, so even multi-megabyte payloads open in a usable state. Use Expand all or Collapse all to flip the entire tree at once, and use the filter to focus on what matters.

Strings are green, numbers are amber, booleans are purple, null is muted grey, and keys are blue. This makes it easy to scan for the right type at a glance — particularly useful when a value looks like a string but is actually a number, or vice versa.

Not directly. The viewer uses the strict JSON parser, so comments, trailing commas, and unquoted keys are rejected. For JSON5 or JSONC, strip the non-standard tokens first; for NDJSON, wrap the lines in a top-level array before pasting.