JSON query workbench

Query JSON without sending payloads anywhere

Paste a JSON document, write a JSONPath expression and inspect matching values, normalized JSONPath paths and JSON Pointers side by side. Filters run in the approved safe mode inside a worker.

Client-side only
Safe filters
Paths and pointers

A practical JSONPath review surface

JSONPath is useful when a response, log event or fixture is too nested to inspect by eye. This playground makes the query, the selected values and the exact result addresses visible in one place.

The JSON text and query stay in the browser worker. The route does not call a backend, import URLs, persist payloads or send custom analytics events with user input.

Preset

Result focusValuesPathsPointersAll

Select title values from an array with a simple wildcard.

Input

Safe eval

JSON documentJSONPath expression

Result

Matches3

Displayed3

Focusvalue

Duration2.95 ms

Diagnostics

Safe filter mode

Filters run with the approved safe evaluator. Native eval, callbacks and custom sandboxes are not exposed.

Dialect caveat

JSONPath implementations differ. Verify target-runtime behavior before using a path in production automation.

1string"Sayings of the Century"$['store']['book'][0]['title']/store/book/0/title

2string"Sword of Honour"$['store']['book'][1]['title']/store/book/1/title

3string"Moby Dick"$['store']['book'][2]['title']/store/book/2/title

Values JSON

[
  "Sayings of the Century",
  "Sword of Honour",
  "Moby Dick"
]

How to read JSONPath output

Syntax choices

Dot notation is compact for normal keys, bracket notation is safer for spaces and dashes, wildcards select collections, and recursive descent finds matching keys anywhere in the tree.

Values vs paths

Values show what matched. JSONPath paths and JSON Pointers show exactly where the value came from, which is useful for tests, docs and debugging API responses.

Safe filters and limits

The route uses safe filter evaluation inside a worker, caps input and displayed matches, and avoids native eval, custom sandboxes, network imports and payload persistence.

Use these when JSONPath is only one part of a larger data or configuration workflow.

Query JSON without uploading payloads

JSONPath Query Playground is a privacy-first workbench for developers who need to inspect nested JSON responses, log events, fixtures and configuration documents. Paste JSON, run a JSONPath expression and compare matching values with normalized JSONPath paths and JSON Pointers. The evaluator runs locally in a browser worker and never sends the document to a backend.

What the MVP supports

The MVP supports object properties, array wildcards, recursive descent, bracket notation for special keys, safe filter expressions, result views for values, JSONPath paths and JSON Pointers, no-match diagnostics, invalid JSON diagnostics, invalid JSONPath diagnostics, result caps and privacy-first limits for input size and worker time.

Why visible JSONPath output matters

JSONPath is often used at the edge between API debugging, QA automation and documentation. A query can look correct while selecting the wrong collection, missing a special key, or returning a value without the address needed for an assertion. Showing values alone is not enough for review. A useful playground must show where each value came from. The side-by-side result table makes that visible. The value column answers what matched. The normalized JSONPath column shows the implementation-specific address. The JSON Pointer column gives a stable address style that teams often use in documentation, JSON Patch discussions, schema notes and test output. When a query returns zero matches, that is treated as a successful diagnostic state rather than a generic failure. Filters are useful, but they also raise safety questions. This route intentionally uses a custom safe subset evaluator inside a worker. Native eval, custom callback evaluation and custom sandbox injection are not exposed. That keeps the public tool focused on practical JSON inspection rather than arbitrary code execution. JSONPath review also benefits from naming the address grammar. The root token `$`, current-node token `@`, recursive descent operator `..`, bracket-quoted keys like `['display-name']`, array indexes, slices and filter predicates each fail in different ways. The playground copy calls those cases out so a developer can distinguish a selector problem from a document-shape problem before changing production code.