Test JSONPath expressions against any JSON document — filters, regex, recursive descent.
Updated
Quick start
Paste JSON, type an expression, see resolved paths and matched values instantly.
Drop your document into the input pane, or click Load sample for the classic JSONPath bookstore example.
Start with $ and walk into the tree. Use [*] for wildcards, .. for recursive descent, ?(...) for filters.
Click Copy values (or ⌘/Ctrl + Enter) to grab the matched values as JSON. All evaluation runs locally.
In-depth guide
Paste any JSON document and a JSONPath expression to see exactly which values it selects and where they live in the tree. The evaluator is a small hand-written parser — no eval(), no new Function() — so it's safe to feed untrusted expressions. Both inputs stay in your browser.
| Expression | Meaning |
|---|---|
$ | Root of the document |
$.foo or $['foo'] | Child by key |
$.list[0] | Index (negatives count from end) |
$.list[0,2,4] | Union — multiple indices or keys |
$.list[1:5] | Slice (start, end, optional step) |
$.list[*] | Every immediate child |
$..author | Recursive descent — every author anywhere |
$.list[?(@.price < 10)] | Filter expression |
Inside ?(...) you can compare keys to literals or to each other. @ is the current candidate; $ is the document root.
$.books[?(@.price < $.expensive)]
$.books[?(@.category == 'fiction' && @.isbn)]
$.books[?(@.isbn =~ /^0-/)]
$.books[?([email protected])]
Operators: ==, !=, <, <=, >, >=, =~ (regex), &&, ||, !. A bare path like ?(@.isbn) is true when the key exists with a non-empty value.
RFC 9535 (February 2024) is the new canonical JSONPath spec. This tester implements the practical subset most users actually reach for. Differences to know:
length() / count() / match() functions — use external post-processing... token includes the starting node itself, which matches most legacy implementations but is a known divergence from the strictest reading of the RFC./pattern/flags. A plain string on the right of =~ is compiled as a pattern with no flags.Many JSONPath libraries pass the body of ?(…) to eval() or new Function(). That makes them code-execution sinks: any string you accept from a user or external system runs with full JS privileges.
This implementation parses filter expressions by hand and only evaluates a fixed grammar of comparisons, regex matches and logical operators. Anything else is a syntax error. You can safely take a JSONPath expression from a URL query parameter, a form field or an API request without sanitising it.
Browser-first by design. The tool page explains any exception before you use it.
Pasted code and data are processed locally in the page. EpitomeTool does not send your input to a formatting, validation, or conversion API.
No. Both the JSON parse and the JSONPath evaluation run entirely in your browser as JavaScript. Nothing is sent over the network.
The common Stefan Gössner dialect popularised in 2007 and partly standardised in RFC 9535. Supported syntax: `$` root, `.name` or `['name']` child, `[n]` index (negatives count from end), `[a,b,c]` union, `[start:end:step]` slice, `[*]` wildcard, `..` recursive descent, `?(...)` filter.
Comparison: `==`, `!=`, `<`, `<=`, `>`, `>=`. Regex match: `=~` (right-hand side is a string or `/pattern/flags`). Logical: `&&`, `||`, `!`. Inside filters, `@` is the current candidate and `$` is the JSON root. Bare paths like `?(@.isbn)` are truthy when the key exists with a non-empty value.
Three common causes: (1) the path before `?(` must point at an array or object — the filter tests each child. (2) strings must be quoted: `?(@.category == 'fiction')`, not `== fiction`. (3) regex literals use `/pattern/flags` syntax: `?(@.isbn =~ /^0-/)`.
`[*]` matches the immediate children of one level. `..` recursively descends into every nested object and array. So `$.store.book[*]` gives the four book objects, but `$..book` finds the `book` key wherever it appears in the tree.
`[-1]` is the last element; `[-2]` the second-from-last. Slices accept negatives too: `[-3:]` is the last three elements, `[:-1]` is everything except the last.
Yes — this implementation uses a hand-written parser, not `eval()` or `new Function()`. Only the supported operators above are honoured. Anything else is a syntax error rather than arbitrary code execution. (Many older JSONPath libraries do use `eval()` and should not be fed untrusted expressions.)
Close, but not byte-identical. RFC 9535 (Feb 2024) tightened several edge cases (canonical output ordering, function syntax, name-shorthand grammar). This tool covers the productive subset most users actually need; for spec-conformance work, cross-check with a reference engine like jsonpath-rfc9535.
Keep exploring
Hand-picked utilities that pair well with the one you're on — all free, client-side, and zero-signup.
Format, validate, and minify JSON with exact line/column parse errors, optional common-fix mode, and one-click copy for API payloads.
Flatten JSON arrays into CSV with custom delimiters.
Validate JSON against a JSON Schema, see errors inline.
Shrink PDF file size without uploading to a server.
Body Mass Index with metric / imperial inputs and WHO category bands.
Combine multiple PDFs into one in your browser.
Split a PDF by pages or page ranges, download as zip.