Add JSON
Paste a document, load the example, or choose a local .json file.
Interactive local JSON viewer
Explore nested objects and arrays as a collapsible tree, then copy the exact path to any value.
Add valid JSON to explore its structure.
01 — 03
The viewer validates the complete document before building a navigable tree in your browser.
Paste a document, load the example, or choose a local .json file.
Expand only the branches you need or open the complete structure at once.
Copy a JSON path for any object, array item, or leaf value with one button.
EXAMPLES & SYNTAX
The parser preserves JSON values while changing only the representation required by this tool.
{
"site": "jsonminify.org",
"enabled": true,
"items": [1, 2]
}Object
├─ site: jsonminify.org
├─ enabled: true
└─ items: Array(2){"name":"value"}Keys and string values require double quotes.
[1, 2, 3]Items keep their original order.
true · false · nullThese tokens are lowercase and are not quoted.
space · tab · line breakOptional outside strings; meaningful inside quoted strings.
WHY JSONMINIFY.ORG
The tree makes hierarchy and value types visible without changing the original document.
Focus on one part of a large object by expanding and collapsing nested arrays and objects.
Get paths such as $.user.name or $.items[0] directly from the displayed structure.
Strings, numbers, booleans, and null values use distinct labels and readable syntax colors.
COMMON USE CASES
Tree navigation is useful when the question is where a value lives, how items are grouped, or which branch contains an unexpected result.
Open only the branches related to your task instead of scanning a long response from top to bottom.
Follow numeric indexes through lists of users, events, products, or results while keeping the surrounding hierarchy visible.
Trace a setting through parent objects and copy its exact path for documentation, code, or a support conversation.
See whether a field is an object, array, scalar, or null before creating types, selectors, transformations, or tests.
JSON REFERENCE
The viewer represents the parsed value as expandable branches and uses a predictable path notation for objects and arrays.
Each object property appears under its parent key. Identifier-like keys use dot notation in copied paths, such as $.user.name.
Array items appear in their original order and use bracket indexes such as $.items[0]. A copied path identifies a position, not a permanent record ID.
Keys containing spaces, punctuation, or other characters that are awkward in dot notation are quoted in brackets, for example $["display name"].
Processing stays local, but parsing and rendering large documents consumes browser memory. Collapse branches and avoid opening every node on limited-memory devices.
FAQ
How the viewer represents nested data while keeping the source local and unchanged.
No. It parses the source to build a tree but does not rewrite the text in the input panel.
It uses a dollar-sign root, dot notation for identifier-like keys, bracket notation for other keys, and numeric brackets for array indexes.
Yes. Use Expand all to open the full tree, or Collapse all to return to the root view.
Yes. Parsing, tree rendering, and path copying run entirely in your browser.