How is it different from JMESPath?

JSONPath is the original Goessner notation with relatively permissive syntax. JMESPath is the AWS standard, with a stricter specification and more features. Both query JSON, and the right choice depends on which one your tooling supports — Postman uses JSONPath, while the AWS CLI uses JMESPath.

What are the basic operators?

The core operators are $ (root), . or [] (child access), .. (recursive), * (wildcard), [n] (a specific index), [start:end:step] (slice), [?()] (filter), and () (script). A path like $.users[0].name walks from the root to users to the first element to the name field. Most paths combine these operators.

How does recursive descent work?

$..name returns every 'name' value regardless of how deeply it is nested. It is invaluable for extracting all instances of a field across a document or finding scattered data. As another example, $..price returns every price field anywhere in the object.

What about filtering?

The [?()] operator applies an expression to each item. $..items[?(@.price > 10)] returns items with a price greater than 10, where @ refers to the current item being evaluated. Filters support comparisons, regex matching, and function calls, which makes them powerful for selective extraction.

Can I get multiple values?

Yes. JSONPath returns an array of matches. $.users[*].email returns every email address, one per user. Even a single result is returned as an array in some implementations and as a scalar in others, so verify the behavior in your specific implementation.

What if the path doesn't match?

You get an empty result, but the exact behavior varies. Some implementations throw an error, others return an empty array, and others return null. Test specifically rather than assuming, and verify against sample data first.

Is the data sent to a server?

No. JSONPath evaluation is pure JavaScript that runs entirely in your browser. Your JSON data never leaves your device, which makes the tool privacy-friendly for API debugging and exploring sensitive JSON.

JSON Path Finder

Find JSON paths interactively by clicking on values online. Free JSON path finder that generates JSONPath expressions for any node.

Data / JSON JSON Tools

Instant results

JSON Input

JSONPath Query

Quick Examples

Results (0 matches)

No results. Enter JSON and a valid path.

About JSON Path Finder

Query JSON data using JSONPath expressions. Extract specific values, filter arrays, and navigate complex JSON structures. Similar to XPath for XML.

How to Use JSON Path Finder

Paste JSON

Drop in the JSON document you want to query. The tool parses it and prepares for path expressions.

Enter JSONPath query

Write a path using the standard syntax — $.field, $.array[0], $..nested, $..items[?(@.price > 10)] — and the tool evaluates it against your JSON.

View results

Matching values appear in the output, either as an array when multiple match, a single value when only one matches, or empty when nothing matches.

Iterate and refine

Adjust the path expression, test edge cases, and save the queries that work for use in scripts, automation, and repeated lookups.

When to Use JSON Path Finder

API response navigation

Pull a specific value out of a JSON response without writing custom traversal code. A JSONPath like $.users[0].email walks straight to what you want, which makes the tool a natural fit for API testing, data pipelines, and any programmatic JSON access where you would rather not hand-roll the navigation.

Config file processing

Configuration files in JSON often need a single value pulled out at a time — $.database.host, for example. JSONPath retrieves it cleanly, so the tool fits comfortably into deployment scripts, config validation, and automated processing.

Data transformation

When source JSON has to become a different shape, JSONPath extracts the specific fields you need before transformation. ETL pipelines, data migrations, and format conversions all rely on this kind of targeted extraction.

Testing and debugging

Finding a specific value buried inside a complex JSON document by scrolling is tedious. JSONPath gives you precise navigation instead, which is invaluable when debugging APIs or validating responses against expectations.

JSON Path Finder Examples

Simple path

Input

JSON: {a: {b: {c: 'value'}}}, Path: $.a.b.c

Output

value

A standard JSONPath. The $ refers to the root, and .name accesses a property. The expression walks down through nested objects and returns either the extracted value or an array of values when multiple match.

Array access

Input

JSON: {users: [{name:'A'}, {name:'B'}]}, Path: $.users[*].name

Output

['A', 'B']

The [*] operator iterates array elements, and JSONPath returns every matching value. This pattern shows up whenever you need to extract a field from each element of an array — list comprehensions, batch operations, that sort of thing.

Filter expression

Input

$..users[?(@.age > 30)]

Output

Users with age > 30

This combines recursive descent (..) with a filter ([?()]) to find every 'users' entry anywhere in the document where the age exceeds 30. The pattern is powerful for complex queries and conditional extraction.

Tips & Best Practices for JSON Path Finder

1.Always start your path with $, the root. Some implementations make it optional, but writing it explicitly is the standard convention.
2.Use the .. operator for recursive descent. $..price finds every 'price' field in the document regardless of how deeply it is nested.
3.Use [*] when you want every element of an array. $.users[*] returns all users, while $.users[0] returns only the first.
4.Filters use the [?()] syntax. Something like $..book[?(@.price < 10)] selects books cheaper than 10, where @ refers to the current item being evaluated.
5.Test your paths against sample data first. Complex paths can produce surprising results, and the tool helps you verify before deploying to production.
6.JSONPath and JMESPath have different syntax but similar goals. JMESPath is the AWS standard; JSONPath shows up in most other tools. Pick one and stick with it.

Frequently Asked Questions

JSONPath is a query language for navigating JSON, conceptually similar to XPath for XML. Stefan Goessner created it in 2007. Common operators include $ for the root, . for a child, [n] for an array index, [*] for all elements, .. for recursive descent, and [?(filter)] for filter expressions. AWS, Postman, and jq tools all use it.

JSON Path Finder

About JSON Path Finder

How to Use JSON Path Finder

Paste JSON

Enter JSONPath query

View results

Iterate and refine

When to Use JSON Path Finder

API response navigation

Config file processing

Data transformation

Testing and debugging

JSON Path Finder Examples

Simple path

Array access

Filter expression

Tips & Best Practices for JSON Path Finder

Frequently Asked Questions

Related Tools

JSON Validator

JSON Formatter

JSON Tree Viewer

JSON Escape/Unescape

CSV Viewer

Credit Card Validator