What does a JSONPath expression look like?

It starts at the root with $, then walks the document. A dot reads a key ($.store), a bracket reads an index or a quoted key ($.store.book[0], $['a key']), [*] is every item, .. searches at any depth, and [?(@.price < 10)] filters. You can mix them, for example $..book[?(@.price < 10)].title.

Why does clicking a key change my expression?

That is the explorer part: each key in the tree carries the path that reaches it, and clicking it loads that path so you can see it work, then extend it by hand. It is a way to build a long path without counting brackets.

Are filters and recursive search supported?

Yes. The vendored engine supports recursive descent (..), wildcards ([*]), array and object unions, slices ([1:3]), and filter expressions with comparisons such as ==, !=, and >=. If an expression is not valid, the status line says so rather than showing a wrong result.

What does the path in the results mean?

It is the canonical JSONPath that reaches that match, always written with brackets. It is useful when you want to copy one exact location out of a large document, or reuse it in another tool that takes a JSONPath.

No. Parsing, matching and the tree all run in your browser, and nothing is sent to a server.

JSON Path Explorer

Q: Why does clicking a key change my expression?

That is the explorer part: each key in the tree carries the path that reaches it, and clicking it loads that path so you can see it work, then extend it by hand. It is a way to build a long path without counting brackets.

Q: Are filters and recursive search supported?

Yes. The vendored engine supports recursive descent (..), wildcards ([*]), array and object unions, slices ([1:3]), and filter expressions with comparisons such as ==, !=, and >=. If an expression is not valid, the status line says so rather than showing a wrong result.