JSON Path Tester
Test JSON path expressions against JSON data to query nested object properties, wildcards, and array indices.
Run tool
This online JSON path evaluation utility allows you to query structured JSON documents and inspect matching elements quickly. You can supply raw JSON payload text along with a targeted path query expression. The parser evaluates dot notation property paths for nested objects, wildcard selectors across properties or list items, and bracket notation expressions for specific array indices or index slices. When the input contains valid JSON and a supported path expression, the tool displays the extracted values, the total count of matched elements, and the original path used for the query. If the document or path field is left blank, the utility completes without returning matches. Providing syntactically broken JSON input generates an error message instead of parsed results. This tool helps developers, testers, and data analysts inspect payload segments, verify path expressions, and extract nested data collections from API responses without modifying the source structure.
Instructions
- Paste or type your JSON data into the JSON Input field.
- Enter your query expression into the JSON Path field using dot notation, wildcards, or bracket indexing.
- Run the tool to evaluate the path against your data.
- Review the extracted elements, match count, and evaluated path expression in the output area.
Examples
- Extracting a nested property: Enter {"user": {"name": "Alex", "role": "admin"}} in JSON Input and user.name in JSON Path to view the matched string Alex.
- Selecting list elements: Enter {"items": ["apple", "banana", "cherry"]} in JSON Input and items[0:2] in JSON Path to retrieve the first two list entries.
FAQ
Which path expressions are supported?
The tool supports dot notation for nested object properties, wildcards for traversing object values and lists, and bracket notation for array indices and index ranges.
What happens if the JSON text contains syntax errors?
If the JSON input is invalid and both fields contain non-whitespace text, the tool displays an error notification rather than an extraction list. Correct any syntax mistakes such as missing quotes or unbalanced brackets to proceed.
What output appears if no elements match the path?
When the JSON is valid but the requested path does not match any data, the tool displays zero matched items along with the evaluated path.
What occurs when one or both fields are left empty?
If either the JSON input or the path expression is blank or contains only whitespace, the tool completes with zero matches.