Pull specific values out of a JSON document with a JSONPath expression and see the matches as you type. Wildcards fan out across arrays and object values, slices take a range, negative indices count from the end, and recursive descent finds a key wherever it is buried. One thing worth knowing up front: filter expressions — the `[?(@.price<10)]` form — are not implemented, because they are a small expression language in their own right and a half-working version would be worse than none. Critically, the tool says so when you use one. Returning no matches silently would look like your data did not contain what you asked for, which is a far more misleading failure than an honest limitation. Everything runs in your browser.
| Expression | Meaning |
|---|---|
| $ | The whole document |
| $.store.book | A named path |
| $['store']['book'] | The same, bracket-quoted |
| $.book[0] / $.book[-1] | First and last element |
| $.book[*].title | Every title in the array |
| $.book[1:3] | A slice, end exclusive |
| $..price | Every price, at any depth |
| $..* | Every descendant node |
| [?(@.price<10)] | Filters — not supported, and you are told |
No. The document is parsed and queried in your browser.
No, and the tool tells you rather than quietly returning nothing. Filters are a small expression language with operators and precedence of their own; a partial implementation would fail in ways that look like your data is wrong. Structural paths, wildcards, slices and recursive descent all work.
The root `$`, dotted names, bracket-quoted names, indices including negative ones, `[*]` wildcards over arrays and objects, `[start:end]` slices with either bound optional, and `..key` recursive descent plus bare `..` for every descendant.
Usually the path does not match the document's actual shape — a common cause is forgetting that a level is an array, so `$.items.name` needs to be `$.items[*].name`. If the expression itself is malformed, or uses a filter, you get a specific message instead of an empty result.
Yes. `[-1]` is the last element, `[-2]` the second to last, as the specification intends. Many simple implementations silently return nothing for these.
The expression is tokenised into steps — dotted names, bracket contents and recursive descent — and each step maps the current set of matches to the next, which is what lets a single wildcard fan out across an array and every subsequent step apply to all of the results. Supported syntax covers the structural majority of JSONPath: the root, dotted and bracket-quoted names, positive and negative indices, wildcards over both arrays and object values, slices with either bound omitted, and recursive descent for a named key or for every descendant. Negative indices count from the end, as the specification intends, rather than silently missing. What is deliberately absent is filter expressions such as the canonical price comparison, because those are a small expression language with their own operators and precedence, and a half-working implementation of them is worse than none. The important part is that they are detected rather than ignored: an unsupported filter returns an explicit message saying so, because silently returning no matches would look like the data did not contain what you were looking for rather than like the tool being limited, and that is a genuinely misleading failure. Malformed expressions are reported specifically too — an unclosed bracket, or an expression that does not begin at the root — instead of returning an empty result that could mean either. Evaluation is immediate as you type, and the document never leaves your browser.