JSON path list

Client

See every path from the document root to a primitive value or empty collection—handy when pairing with JSON Pointer, query tools, or schema authoring.

Learn more: path listing

Walk the parsed tree and print one path per leaf—syntax is similar to JSON Pointer segments but uses `$` as the document root.

Compare

For resolving a single pointer, use the JSON Pointer tool; this page is for exploring every endpoint in a document at once.

JSON path list

?

One path per line from root $ to each primitive or empty object/array.

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.

More tools

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