Interactive local JSON viewer

JSON Viewer Online

Explore nested objects and arrays as a collapsible tree, then copy the exact path to any value.

JSON tree viewer

Local processing · private
Input JSON1 line · 0 B
JSON tree

Add valid JSON to explore its structure.

Browser-direct

Load JSON from a URL

Your browser contacts this URL directly. The destination must allow CORS; jsonminify.org does not proxy or store the response.

Processed in your browser
Standard JSON validation
Copy precise JSON paths

01 — 03

Explore nested JSON in three steps

The viewer validates the complete document before building a navigable tree in your browser.

01

Add JSON

Paste a document, load the example, or choose a local .json file.

02

Open the tree

Expand only the branches you need or open the complete structure at once.

03

Copy a path

Copy a JSON path for any object, array item, or leaf value with one button.

EXAMPLES & SYNTAX

Input, output, and common errors

The parser preserves JSON values while changing only the representation required by this tool.

INPUT
{
  "site": "jsonminify.org",
  "enabled": true,
  "items": [1, 2]
}
OUTPUT
Object
├─ site: jsonminify.org
├─ enabled: true
└─ items: Array(2)
CaseValid formWhy it matters
Object keys{"name":"value"}

Keys and string values require double quotes.

Arrays[1, 2, 3]

Items keep their original order.

Primitive valuestrue · false · null

These tokens are lowercase and are not quoted.

Whitespacespace · tab · line break

Optional outside strings; meaningful inside quoted strings.

WHY JSONMINIFY.ORG

See structure instead of scanning text

The tree makes hierarchy and value types visible without changing the original document.

Collapsible branches

Focus on one part of a large object by expanding and collapsing nested arrays and objects.

Copyable JSON paths

Get paths such as $.user.name or $.items[0] directly from the displayed structure.

Typed values

Strings, numbers, booleans, and null values use distinct labels and readable syntax colors.

COMMON USE CASES

When a JSON tree is easier than raw text

Tree navigation is useful when the question is where a value lives, how items are grouped, or which branch contains an unexpected result.

Explore an unfamiliar API payload

Open only the branches related to your task instead of scanning a long response from top to bottom.

Inspect arrays of records

Follow numeric indexes through lists of users, events, products, or results while keeping the surrounding hierarchy visible.

Locate a nested configuration value

Trace a setting through parent objects and copy its exact path for documentation, code, or a support conversation.

Compare shape before writing code

See whether a field is an object, array, scalar, or null before creating types, selectors, transformations, or tests.

JSON REFERENCE

Reading the JSON tree and copied paths

The viewer represents the parsed value as expandable branches and uses a predictable path notation for objects and arrays.

01

Objects become named branches

Each object property appears under its parent key. Identifier-like keys use dot notation in copied paths, such as $.user.name.

02

Arrays use numeric indexes

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.

03

Complex keys use bracket notation

Keys containing spaces, punctuation, or other characters that are awkward in dot notation are quoted in brackets, for example $["display name"].

04

Large trees still use device memory

Processing stays local, but parsing and rendering large documents consumes browser memory. Collapse branches and avoid opening every node on limited-memory devices.

FAQ

JSON tree and path questions

How the viewer represents nested data while keeping the source local and unchanged.

Does the viewer modify my JSON?

No. It parses the source to build a tree but does not rewrite the text in the input panel.

Which path notation does it copy?

It uses a dollar-sign root, dot notation for identifier-like keys, bracket notation for other keys, and numeric brackets for array indexes.

Can the viewer open every branch?

Yes. Use Expand all to open the full tree, or Collapse all to return to the root view.

Is the JSON tree generated locally?

Yes. Parsing, tree rendering, and path copying run entirely in your browser.