JSONPath Query Evaluator

Runs locally in your browser. Nothing leaves your device.

Run RFC 9535 JSONPath queries locally against JSON and show normalized paths.

Query settings

Legacy syntax such as JavaScript filters or =~ /regex/ is intentionally rejected. An empty result is not an error.

Input

Output

Paste valid JSON and a JSONPath query.

How it works
  1. 1
    Paste JSON or open a file
    Paste JSON or open a JSON or TXT file up to 100 MB.
  2. 2
    Enter the JSONPath query
    Enter an RFC 9535-compliant expression such as $.store.book[*].title.
  3. 3
    Export the matches
    Choose the output format and copy or download the matches.
Good to know
The JSONPath query evaluator evaluates JSONPath expressions directly in your browser strictly according to RFC 9535, deliberately rejecting legacy syntax like JavaScript filters or =~ /regex/ that many other JSONPath libraries allow. The normalized path is shown for each match, and results can be exported as JSON, JSON Lines, CSV, or just a path list.
A query AST summary shows the structure of the expression. Important: JSONPath variants differ in filters and functions — this tool deliberately follows the RFC standard rather than popular but non-standardized extensions, and an empty result is not an error.
Typical use cases
Validate standard-compliant JSONPath expressions before using them in code
Test a JSONPath expression against real data to ensure it's RFC 9535 compliant and works in standard-compliant libraries.
Export matches as CSV for a spreadsheet evaluation
Choose CSV as the output format to further process path-value pairs directly in a spreadsheet.
Tips for better results
No result is not an error
A valid query can return empty if no nodes match — in that case, check the source data's path structure instead of assuming an error.
Don't expect legacy syntax from other tools
Expressions with JavaScript filters or =~ /regex/ from other JSONPath implementations are deliberately rejected here, since they are not part of RFC 9535.
Features
  • Strict RFC 9535 compliance
    Deliberately rejects legacy syntax like JavaScript filters to ensure standard compliance.
  • Four output formats
    JSON, JSON Lines, CSV, or a plain list of normalized paths.
  • Local processing
    Your data never leaves your device; evaluation runs entirely in the browser.
Frequently asked questions
Why is my filter syntax from another library rejected?
The tool strictly follows RFC 9535 and deliberately rejects legacy extensions like JavaScript filters or =~ /regex/ that are not part of the standard.
Is my data uploaded?
No. Evaluation runs entirely locally in the browser.
More tools
JSON FormatterValidate, format, minify, analyze, and inspect JSON as a tree locally.JMESPath EvaluatorRun JMESPath Core expressions locally against JSON and export the JSON result.JSON to TypeScript InterfaceInfer TypeScript interfaces and type aliases from JSON sample data locally in the browser.XPath Tester / PlaygroundTest XPath 1.0 in the browser and XPath 3.1 locally against XML or HTML documents.
Looking for another tool?
Every tool runs locally in your browser – no sign-up, no upload, and it works offline.
Search all toolsMore in Development