JSONPath Query Evaluator

Run JSONPath queries against JSON data with live results and expression builder.

Tested tool guide Tested browser tools Checked August 16, 2026

What JSONPath Query Evaluator does, with a checked example

JSONPath Query Evaluator applies a JSONPath expression to pasted JSON and refreshes the matching values as either input changes. Start at the root marker `$`, then select object members, array positions, wildcards, or other accepted path segments; the expression builder helps assemble that path. The common surprise is result shape: JSONPath selects nodes, not a transformed document, so one matched scalar can still appear inside a one-item result collection.

Worked example

A concrete input and expected output from the current implementation.

Input

JSON:
{"orders":[{"id":"A1","total":12},{"id":"B2","total":18}]}

JSONPath:
$.orders[*].total

Expected output

[
  12,
  18
]

`$` identifies the document root, `.orders` selects the array, `[*]` selects both array elements, and `.total` selects each total. The two matched numbers are returned in the same order as the objects in the source array.

How the result is produced

Building the path

The JSON input must be one complete, valid JSON value, while the query is a JSONPath expression rooted at `$`. Dot member selectors address object names, bracket notation can address array positions, and wildcards can select several children. Editing either side triggers the live result, and the expression builder provides a structured way to compose selectors accepted by the evaluator.

Reading the matches

Each successful query denotes a nodelist drawn from the input document. Several selected nodes become several result values. Selecting no node produces an empty result, which differs from selecting a JSON `null`. Array wildcards preserve the source array sequence. Interpret the output as values reached by the path, not as a general-purpose conversion into a newly designed JSON structure.

Good uses

Check that `$.response.items[*].id` reaches every ID in a captured API response before copying the path into a test or monitoring rule.
Inspect a deeply nested configuration document by selecting one branch or one indexed array element without manually scrolling through the full JSON.
Diagnose why a wildcard, bracketed member name, or array index returns too many, too few, or zero values in a downstream JSONPath integration.

Limits and checks

JSONPath implementations do not all accept the same extensions. A filter, function, or shorthand that evaluates here may be rejected or interpreted differently by the library, product, or policy engine where you plan to use it. Treat the destination system as the final compatibility check.
An empty result means the path selected no nodes. It does not prove that a field exists with an empty string, empty array, empty object, or `null`; those are JSON values and should appear as matches when explicitly selected.
Do not infer a stable semantic order from wildcard selection over object members. JSON objects are collections of names and values, while arrays carry an explicit sequence. If order matters, query an array or verify the consuming system's ordering rules.

Common questions

Can this evaluator change or reshape my JSON?

No. JSONPath is a selection language, and this tool shows the values reached by the expression. It does not define a mapping that renames fields, builds a new object, performs arithmetic, or writes changes back into the pasted document. Use a transformation language or application code when the required output has a different structure.

Why does a query work here but fail in another product?

JSONPath existed in several implementation-specific forms before its IETF standardization, and products still differ in supported syntax and extensions, especially filters and functions. The expression builder can help create a query this evaluator accepts, but it cannot guarantee that another engine accepts the same expression. Re-test the exact query with the destination engine and its documentation.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.