Run a JSONPath expression against your document and see exactly which values it selects, and where each one came from. Your file never leaves this page. Everything happens in your browser, and there is no upload endpoint to send it to — that is checked by a build gate that fails if any network code reaches a tool’s bundle.
How to do it
- Paste your JSON.
- Type an expression, or pick one of the examples.
- Read the matches, each with the path it was found at.
Questions
Which parts of JSONPath are supported?
Properties, wildcards, indexes including negative ones, slices, recursive descent with .., unions, and filters — comparison, existence, regular-expression matching, and && / ||.
Is it safe to paste a filter expression?
Yes. Filters are parsed into a comparison and evaluated, never turned into code and run. Several JSONPath libraries have done the latter, which turns a text box into a way to execute whatever is typed into it.
Why does my expression select nothing?
Usually a path that does not exist in the document — which is reported as no matches rather than as an error, because it is a real answer. A genuinely malformed expression is reported as one, with the character it went wrong at.