We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Accurately extract data from JSON documents using JSONPath expressions. Supports recursive queries and filter expressions.
Enter JSON and a JSONPath expression
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
JSONPath is a query syntax for selecting values from a JSON document. This evaluator accepts JSON text and an expression, then returns the matched values in an array. Its supported subset includes the root symbol $, dot notation for simple object keys, quoted keys in brackets, nonnegative array indexes, and a one-level wildcard written [*]. Each path segment operates on the values selected by the preceding segment.
For example, $.store.book[*].title follows the store object key, enters book, expands the array’s direct elements, and selects each title. The result is an array even when there is only one match. A missing key or out-of-range index contributes no value, so the result may be an empty array.
$ selects the root JSON value..name accesses a simple object key made from letters, digits, underscore, dollar sign, or hyphen.['name'] or ["name"] accesses a quoted key, including names that are awkward in dot notation.[0] selects one nonnegative array position; indexes begin at zero.[*] expands the direct values of the current object or array. It does not recursively walk every nested level.The evaluator returns selected values, not their original locations in the document. If you need paths alongside values, this output does not provide that mapping.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Paste a complete JSON object or array. If the input has a syntax error, fix that first; a malformed document and an unsupported path produce different error states.
Begin with $, then add a key, quoted bracket key, array index, or wildcard as needed. You can load the sample to see $.store.book[*].title in action.
Compare each result with the expected fields and nesting level. An empty array usually means a key or index did not select anything; the evaluator does not guess a similar key for you.
The result is a JSON array of selected values. Check its shape before pasting it into a script or another system.
Use cases
See how the tool fits into real work and everyday tasks.
After removing credentials or personal data, a developer can select a nested field or expand one array level to confirm the returned values and their JSON types.
A team can reuse a short path against a known JSON sample to see whether a field appears at the expected nesting level before writing application code.
Q&A
Find concise answers to common questions and confusing cases.
All matched values use the same array output shape. One match appears as a one-element array; no matches appear as an empty array.
The page implements only a subset of JSONPath. Recursive descent, filters, slices, negative indexes, and selector unions are not supported; use the root, key, nonnegative index, and direct wildcard forms described above.
No. [*] expands only the current object’s or array’s direct values. Add further path segments to inspect another level.
No. It returns values in an array without their document locations. Keep the source JSON if you need to trace a result back to a specific path.
Notes
Review scope, result limitations, and important precautions before use.
RFC 9535 defines more syntax than this page supports, including descendant segments and filter selectors. A query accepted by another JSONPath implementation may fail here. Treat error feedback as a limit of this evaluator’s supported subset, not proof that a query is invalid under the full standard.
Do not paste secrets, access tokens, or personal information into a page unless you are comfortable processing that content online. For production code, verify results with your target JSONPath implementation and test representative inputs, including empty or missing fields.
Related
Discover related tools, collections, and available API capabilities.