JSON Path Finder

List every path in a JSON document as JSONPath, JavaScript or jq syntax, click a path to see its value, or type a path to look it up. Runs in your browser.

Value at path

Runs entirely in your browser. Your data is never uploaded.

Related Tools

View All

What is JSON Path Finder?

The JSON Path Finder shows the path to every value in a JSON document and lets you look up a value by its path. Paths can be displayed as JSONPath ($.store.book[0].title), JavaScript (data.store.book[0].title) or jq (.store.book[0].title) syntax, ready to paste into code.

How to use JSON Path Finder

  1. Paste JSON into the JSON input box (or click Load sample).
  2. Browse the All paths table; use the filter box to search by path or value.
  3. Click a row to put its path into the Path box and show the value.
  4. Or type a path such as $.store.book[1].title to look it up directly.
  5. Switch Path syntax to copy paths in JavaScript or jq form.

Example

Input
{"store":{"book":[{"title":"A","price":8},{"title":"B","price":12}]}}
Path: $.store.book[1].title
Output
"B"

The paths table lists 9 paths, from $ to $.store.book[1].price.

When to use JSON Path Finder

Use it to find the path to a field you see in a large API response, generate accessors for code, or check where a value lives. For queries that return several values (wildcards, filters, recursive search) use JSON Query.

How JSON Path Finder works

The JSON is parsed with a strict parser that keeps numbers exactly as written. The tree is walked depth-first, building a JSONPath for every node: identifier-like keys use dot notation, other keys use bracket notation with quotes ($['first name']), array items use [index]. Containers are listed with their size. Lookups accept JSONPath with or without $, jq-style leading dots and bracket notation; they resolve one exact location (no wildcards or filters – use JSON Query for those). The table shows at most 500 rows at a time; use the filter for large documents.

Common Use Cases

  • Finding the JavaScript accessor for a deeply nested API field
  • Writing JSONPath for monitoring or test assertions
  • Exploring an unfamiliar JSON structure
  • Getting jq paths for shell scripts

Security Note

Everything runs locally in your browser; the code you paste is not uploaded.

FAQs

Which path syntax should I use?

JSONPath for tools that accept JSONPath, JavaScript for code, jq for the command line.

Can I use wildcards like [*]?

Not here – the finder resolves one exact path. Use the JSON Query tool for wildcards and filters.

What if a key contains spaces or dots?

It is written in bracket notation, e.g. $['first name'].

Good next steps

Explore more categories