About the JSONPath Tester
JSONPath is to JSON what XPath is to XML: a compact way to select parts of a document. It is used by Kubernetes (kubectl -o jsonpath), AWS Step Functions, REST Assured, Postman tests and many logging tools. This tester evaluates your expression live and shows both the matching values and their normalized paths.
Syntax cheat sheet
| Expression | Meaning |
|---|---|
$ | Root object |
.key / ['key'] | Child member |
..key | Recursive descent — all key members at any depth |
* | Wildcard — all members / elements |
[0], [-1], [0,2] | Array index(es); negative counts from the end |
[1:3], [::2] | Array slice (start:end:step) |
[?(@.price < 10)] | Filter with == != < <= > >= && || ! |
[?(@.name =~ /^a/i)] | Regular-expression match |
Features
- Live evaluation as you type
- Filters with logical operators
- Regex matching with
=~ - Slices with negative indices and steps
- Shows result values or normalized paths
- Safe evaluator — no
eval()
How to use it
- Paste your JSON document (or load the sample).
- Type a JSONPath expression — results update instantly.
- Switch between Values and Paths and copy the output.
Frequently asked questions
Which JSONPath dialect is supported?
The classic Goessner syntax used by most libraries (Jayway, jsonpath-plus), including filter expressions. Script expressions (…) other than filters are intentionally not executed for safety.
How is this different from kubectl jsonpath?
kubectl uses the same core syntax but wraps expressions in {…} and adds range/end templating. Remove the braces to test the inner expression here.