jfmt.dev

JSON Viewer

Paste JSON and walk it as a collapsible tree. Expand only the branch you care about โ€” the document is parsed in this tab and never leaves the device.

input.json

JSON formatter

Input0 B
Output ยท preview.json
{ }

Run a tool to see a polished result here

Live syncReady ยท processed locally in your browser
Local-only processing: your JSON never leaves this browser tab.

A tree is for inspection, pretty print is for copy-paste

Pretty-printed JSON is still a wall of text: every nested object costs another indent level on the screen. The viewer maps objects and arrays onto foldable nodes, auto-folds large arrays, and lets you change a value in place. When you need indented source to drop into a PR, switch to the beautifier; when you need to hunt `user.profile.roles[1]`, stay on the tree.

How large arrays are folded

A 100-item list is painful as pretty-printed text and painful as 100 open nodes. The viewer auto-folds long arrays so you expand a window of indexes at a time. That is the main reason this page exists alongside the beautifier: the beautifier must show every line, the tree does not.

Types you can see in the tree

Objects show keys. Arrays show indexes. Strings, numbers, booleans, and null are labeled as leaves so you can spot `1` vs `"1"` without reading quotes in a 4 kB dump. Duplicate keys that survived parsing appear as the last value; the status line still warns they existed.

Jumping to a path vs clicking around

If you already know the path (`$.store.book[*].author`), JSONPath is faster than expanding nodes. If you do not know the path, the tree is how you discover it. Many people use both: viewer to find the field, JSONPath to extract it into a list.

Sample input on this page

The sample nests a user profile, feature flags, and an items array so you can collapse flags, expand roles, and open a single SKU without pretty-printing the whole document. Swap in a production payload of your own; it stays in this tab.

{
  "user": {
    "id": "u_18",
    "profile": { "name": "Ada", "roles": ["admin", "editor"] }
  },
  "flags": { "dark": true, "beta": false },
  "items": [
    { "sku": "fmt", "qty": 2 },
    { "sku": "xlsx", "qty": 1 }
  ]
}

How to use this tool

  1. Paste a nested payload โ€” API responses with users, flags, and item lists are a good fit.
  2. Run JSON Viewer. Objects and arrays become nodes. Click a disclosure control to expand a branch; large arrays fold in groups so the page stays usable.
  3. Edit a scalar in the tree if you are exploring; the left-hand text updates to match. Copy still comes from the formatted JSON if you need the whole document.
  4. Invalid input will not render a tree. Validate or Repair first, then come back.

When this page is the right choice

Open the viewer when the problem is โ€œwhat is inside this blob?โ€ rather than โ€œmake it prettyโ€ or โ€œturn it into Excelโ€. It is the right URL for json viewer / json tree searches. It is the wrong URL for schema validation or comparing two files side by side.

FAQ

Does the JSON viewer upload my file?

No. The tree is built in the browser from the text you pasted.

Can I edit values in the tree?

Yes for inspection. Changing a leaf writes back into the document. Treat it as a scratchpad, not a full IDE.

What if the JSON is invalid?

The viewer needs a parseable document. Use the validator or Repair, then run the viewer again.

Why not only pretty-print?

Pretty print is linear text. A tree lets you collapse 90% of a payload and still see one nested field.

Is this a JSON editor with schema?

No. It is a local tree for viewing and light edits. It does not load JSON Schema.