JSONPath Finder and Tester
Test a JSONPath query against supplied JSON, see exact matched values and normalized paths, and export the results.
Find and Reuse JSONPath Matches
Enter one query per line. Use names, indexes, slices, wildcards or recursive descent. Filters and functions are outside this workspace’s scope.
JSONPath Finder and Tester: how to use it
- Paste strict JSON, open a local JSON file or load the event example.
- Enter one query per line or open a saved query list. Start each query with $. Use names, indexes, slices, wildcards or recursive descent, then select Test query.
- Use a result path to select one match, or download the JSON report with all matched paths and source values.
Limits and notes
Up to 500,000 UTF-16 code units of JSON, 20 queries with 2,000 code units apiece and 1,000 matches at any step. The supported RFC 9535 subset covers names, indexes, slices, selector lists, wildcards and recursive descent. Filter expressions and functions are outside this workspace’s scope.
How your privacy works →JSONPath Finder and Tester: common questions
What is a normalized JSONPath?
It is a bracket-notation expression such as $['events'][1]['talk'] that selects a single node in the supplied document.
Why does a query return zero matches?
A key may be missing or a selector may not apply to that value. A present key with a JSON null is returned as a match.
Will big integer values be rounded?
The report inserts the original JSON token for a matched value. Use a number-preserving parser if you open the report in software that normally rounds large integers.