Which JSONPath syntax does the tester follow?

It uses the jsonpathly implementation of RFC 9535 JSONPath, so expressions may differ from older libraries that introduced their own operators.

What is a normalized path?

It is an unambiguous location for a match, expressed from the JSON root with standardized member and index segments. It can distinguish values that look identical.

Why can a valid query return zero matches?

A syntactically correct expression may simply select nothing in the current document. That is different from a JSONPath syntax error, which is reported separately.

Does the query modify my JSON?

No. Queries are read-only. Source parsing, matching and result export happen locally without changing or uploading the input.

Back to Developer & Data Tools

JSONPath Tester

Run standards-based JSONPath expressions against local JSON and inspect every matching value beside its normalized location.

Test RFC 9535 JSONPath expressions locally in your browser.

1. JSON Input

Type, paste, upload or drop a .json file

2. JSONPath Query

Expression

Supports child and bracket selectors, indexes, wildcards, recursive descent, slices, multiple selectors and RFC 9535 filter expressions.

Examples

Examples load sample data and an expression. Click Run Query when ready.

3. Results

Run a query to see matching values and paths.

Your JSON and query stay in this browser. Nothing is uploaded or stored.

How to use JSONPath Tester

1
Paste JSON, upload or drop a .json file, or load an example document.
2
Enter a JSONPath expression or choose one of the supplied query examples.
3
Select Values, Paths or Both for the result display.
4
Click Run Query and correct either JSON or JSONPath syntax if an error appears.
5
Copy individual paths or values, or download all current matches as JSON.

Frequently asked questions

About JSONPath Tester

JSONPath is useful only when the query engine and displayed locations agree. This tester evaluates RFC 9535 expressions and pairs each selected value with its normalized path, making filters, descendants, slices and member selections easier to verify against real data.

Source JSON and query syntax are validated independently, so an invalid document is not confused with a valid expression that has no matches. Results can emphasize values, paths or both, and each item remains individually copyable. The downloadable JSON records the complete current result set for debugging or documentation.