How It Works Under the Hood
The evaluator parses JSONPath tokens starting from root `$`, traversing child keys, wildcard slots (`*`), negative array indices (`[-1]`), slice ranges (`[start:end]`), recursive subtree descent (`..`), and safe AST-free comparison predicates (`==`, `!=`, `<`, `<=`, `>`, `>=`, boolean flags).
Step-by-Step Instructions
Paste any JSON object or array into the left JSON Input pane.
Type a JSONPath expression like `$.store.books[*].title` or click a quick preset.
Review extracted values as formatted JSON alongside each exact matched node path (`$['store']...`).
Copy the matched JSON array for tests, API mocks, or automation scripts.
Key Features & Performance
- Supports dot & bracket notation, array wildcards `[*]`, negative indexing `[-1]`, and slices `[0:3]`
- Supports recursive descent `$..key` across arbitrary nesting depths
- Evaluates filter expressions `[?(@.price < 20)]`, `[?(@.inStock)]`, and string equality without unsafe `eval()`
- Shows exact resolved node path next to every extracted value
- 100% browser-local for inspecting sensitive API responses and webhook payloads
Methodology, Formulas & Technical Standards
Expressions run through a recursive path evaluator without `eval()` or `new Function()`, eliminating injection risk while enforcing strict CSP compatibility and returning deterministic traversal order.
Common Real-World Use Cases
- Extracting response fields for Postman, Playwright, Step Functions, or Kubernetes/AWS CLI workflows
- Debugging webhook JSON payloads to isolate deeply nested IDs or arrays
- Verifying negative array index (`[-1]`) and predicate filter expressions before deploying configs
- Inspecting large OpenAPI / GraphQL JSON snapshots locally
Worked Examples & Edge Cases
Filter Books Under $20
$.store.books[?(@.price < 20)].title
["Browser Cryptography", "Zero-Backend Architecture", "WebAssembly Field Guide"]
Filters objects first, then extracts only the requested property.
Recursive Price Extraction
$..price
[14.5, 24, 8.99, 19.5]
Collects matching keys at any depth.
Limitations, Scope & Accuracy Notes
- • Filter predicates evaluate single binary/truthy conditions (`@.prop op literal`); compound `&&`/`||` chaining or regex script calls inside `[?(...)]` are not yet supported.
- • Invalid JSON input reports exact native `JSON.parse` syntax diagnostics.
Local Browser Processing & Privacy
Traditional web converters upload your documents, snippets, or media files to remote servers. JSONPath Expression & Filter Tester runs inside your browser tab:
Your input text and files are processed locally without uploading payloads to a processing server.
Microdeck does not log or store the files or inputs you paste into tool workspaces (normal static hosting/CDN requests still load page assets).
Working outputs stay in your browser tab and are released when you reset the tool or close the tab.
Frequently Asked Questions
Does this JSONPath engine use `eval()` under the hood?
No. Filter conditions are parsed explicitly by token rather than evaluated as arbitrary JavaScript, keeping execution safe and predictable.
How do negative array indices work?
`$[-1]` selects the last element, `[-2]` selects second-to-last, and slices like `[0:2]` follow half-open start/end bounds.
Can I see where in the JSON tree each match came from?
Yes. Below the JSON output panel, every match lists its canonical resolved bracket path.
What if my JSON payload contains PII or tokens?
Parsing and querying occur strictly in browser RAM; zero payload bytes leave your machine.
Explore Related Micro-Tools
JSON Formatter, Validator & Diff
Format, validate, compare diffs & auto-repair malformed JSON locally in your browser
JSON Schema Draft Validator
Validate JSON payloads against JSON Schema rules (`required`, `type`, `enum`, `format`, `additionalProperties`, numeric/string bounds)
NDJSON / JSON Lines Explorer & Filter
Parse streaming `.ndjson` / `.jsonl` logs into searchable tables, flag malformed lines & export filtered CSV/JSON/NDJSON