Query JSON locally using RFC 9535 JSONPath. Test filters, wildcards and slices, inspect matched values and normalized paths, then copy or download results without executing JavaScript.
$ root · $.name child · $['a.b'] literal key · $[*] children · $..price descendants · $[0,-1] selected indexes · $[1:5:2] slice · $.books[[email protected] < 10] filter.
Standard functions include length(), count(), value(), match() and search(). Legacy script expressions, custom functions and JavaScript method calls are not supported. Regex functions use the library’s I-Regexp interpretation. A 5-second limit includes startup; results are capped at 1,000 matches and 250,000 UTF-16 output units. Limit errors provide no partial export.
JSONPath RFC 9535 reference ↗Queries run on your device in a disposable worker with a self-hosted RFC 9535 parser. Query text is interpreted as JSONPath, never JavaScript. No uploads, external APIs, accounts or saved query history are involved.
The tool uses self-hosted jsonpath-rfc9535 1.3.0 (Apache-2.0), targeting the standardized RFC 9535 dialect. It supports child and descendant segments, quoted names, wildcards, index lists, slices, filters and standard length/count/value/match/search functions. It does not implement legacy JavaScript script expressions, arbitrary method calls or custom functions. Behavior can differ from older JSONPath tools.
No. Filters are parsed and interpreted by the JSONPath engine; there is no eval, Function constructor or query-generated JavaScript. Match/search functions use the library’s I-Regexp interpretation with Unicode behavior. Expensive queries or patterns can still take time, so work runs in a cancelable worker with a five-second deadline.
Values produces a JSON array of selected values. Paths produces normalized JSONPath strings such as $['books'][0]['title']. Paths and values produces objects with path and value members. Results are always arrays, even for one or zero matches. Duplicate selections are retained. Object-member traversal order follows the engine and does not promise original JSON text order.
Numbers are parsed with JavaScript binary64 semantics, so ordinary decimal precision and number spelling can change. Unsafe integers, non-finite values and nonzero underflow to zero are rejected. Quote large identifiers to retain their text. Duplicate keys and unpaired surrogate strings/keys are rejected. Objects have no inherited properties internally, so prototype-like keys remain own data.
Input accepts 100,000 UTF-16 units, 20,000 values and 64 nested containers. Queries accept up to 2,000 units. Results are limited to 1,000 matches and 250,000 output units. Exceeding a limit fails rather than exporting a partial list. The five-second deadline includes module startup, parsing and execution; cancel, edits and page exit terminate the worker and discard late replies.
No. The tool only queries the parsed document. Inputs remain unchanged, results are rendered as text, and no API or storage is used. Exports contain selected values or paths rather than a wrapper report, so they can contain sensitive source data. Copy/download are optional.
