JSON path list

Client

See every path from the document root to a primitive value or empty collection. Switch the output to include RFC 6901 JSON Pointers (tab-separated), filter by substring, and skim depth stats—useful next to JSON Pointer resolve, JSONPath, and schema work.

Learn more: path listing

Walk the parsed tree and print one path per leaf—syntax mirrors common `$` / dot / bracket notation; you can also emit RFC 6901 JSON Pointers alongside each line for RFCs, OpenAPI, or the JSON Pointer tool.

JSON Pointer column

The optional tab-separated mode prints `leaf path` + `JSON Pointer` so you can paste pointers into validation errors, patch bodies, or the JSON Pointer resolver without hand-translating `~0` / `~1` escapes for `/` and `~` in object keys.

Filter and stats

Use substring filter to shrink long API dumps; the max depth counts JSON Pointer segments (shallow trees are easier to scan in reviews).

Compare

For resolving a single pointer interactively, use the JSON Pointer & Patch page; this tool is for enumerating every leaf at once.

JSON path list

?

One path per line from root $ to each primitive or empty object/array. Toggle RFC 6901 pointers for copy/paste into JSON Pointer & Patch or specs.

Showing 4 paths · max depth 3 segments

Nearby workflows on Toolcore

  • JSON formatter — when the document must parse before any transform or export.
  • JSON extract — to pull values at paths you listed.

Common use cases

  • Enumerate every leaf path when writing JSON Schema, OpenAPI examples, or field documentation.
  • Cross-check path strings before converting them to JSON Pointer or JSONPath expressions.
  • Spot unexpectedly deep nesting or missing branches when onboarding to an unfamiliar API payload.

Common mistakes to avoid

  • Treating listed paths as JSON Pointers verbatim

    This view uses dot/bracket notation for humans. JSON Pointer has different escaping rules for ~ and / in keys—translate carefully.

  • Expecting array indices in paths to match another tool’s 1-based indexing

    Paths follow JSON array indexing (0-based). Off-by-one mistakes break automation that replays paths elsewhere.

FAQ

Is path listing performed locally?

Yes. The document is walked in your browser; nothing is uploaded.

Why do I see paths to empty arrays or objects?

Leaves include empty collections when the tool reports them as terminal nodes—useful for spotting structural holes versus missing keys.

How does the JSON Pointer column relate to the human-readable path?

Each line can show the leaf path plus a separate RFC 6901 pointer with correct ~0/~1 escaping for keys that contain `~` or `/`. Paste that pointer value into the JSON Pointer tool or APIs that expect RFC 6901 strings.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • list all json paths
  • json key path explorer
  • json path to rfc 6901 pointer

More tools

Related utilities you can open in another tab—mostly client-side.