JSONPath Finder & Tester — Free Online 2026

JSONPath Finder Online — Complete Guide

This JSONPath finder online is a dual-mode tool that lets you both discover and evaluate JSON paths in real time. In Tree Finder mode, paste any JSON and click any value — string, number, boolean, or null — to instantly see its complete JSONPath expression like $.store.books[0].price. In Query Tester mode, type a JSONPath expression including advanced syntax like recursive descent ($..price), wildcards ($.store.*), filter expressions ($.books[?(@.inStock == true)]), and slices ($.books[0:2]), and all matching values are returned immediately. Everything runs in your browser — your JSON data never leaves your device.

When to Use Finder Mode vs Query Tester

Use Finder mode when you are exploring an unfamiliar API response and want to discover which path leads to a specific value. It is the fastest way to go from "I can see this value" to "I have the exact JSONPath for it." Use Query Tester mode when you already know the path pattern and want to verify it returns the right data — for example, confirming that $.items[?(@.status == "active")].id returns all active item IDs before wiring it into your Postman test or ETL pipeline. Together, the two modes cover the full JSONPath workflow without switching between tools.

JSONPath vs JSON Pointer vs jq

Three technologies are commonly confused. JSONPath (Stefan Goessner, 2007; standardized as RFC 9535 in 2024) is the most widely supported format — used natively in Postman, AWS CloudFormation, Kubernetes config selectors, Python jsonpath-ng, and Java Jayway JsonPath. It uses $ as root and supports filter expressions. JSON Pointer (RFC 6901) uses slash-delimited paths like /store/books/0/title — simpler, no filters, used in JSON Patch. jq is a standalone command-line tool with a Turing-complete transformation language — far more powerful than JSONPath for transforming data, but not interoperable with most API tools. The export snippet on this tool converts any JSONPath to its jq equivalent for command-line use.

Filter Expressions — The Most Powerful JSONPath Feature

Filter expressions let you select array elements based on their content rather than their index. The syntax is [?(@.field operator value)] where @ represents the current element. For example, $.products[?(@.price < 50 && @.inStock == true)] returns all products under $50 that are in stock. Supported operators in this tool: == != < <= > >= with && and || for combining conditions. Filter evaluation uses a safe AST-based engine — no eval() — so you can safely paste untrusted JSON and test against it.

Real-World Use Cases for JSONPath

API testing with Postman: paste your API response here, find the path to the value you want to assert, then copy it directly into your Postman test script. ETL pipelines: use $..fieldName to extract a field from every level of a nested response without knowing the exact structure. Log analysis: JSON Lines logs (one JSON object per line) can each be inspected here — find the path to your error code once, then use it in your Elasticsearch query or log aggregation rule. You can also pipe the output through our JSON to CSV converter to analyze the extracted data in a spreadsheet, or validate your source JSON with our JSON Validator before querying it.

JSONPath Syntax Reference and Common Patterns

Understanding which JSONPath expression to write is the main challenge for most developers. The cheatsheet above lists the syntax tokens. Below are the most frequently used patterns with explanations of when each is appropriate.

Recursive Descent (..) — The Most Searched Feature

The double dot .. operator traverses the entire document tree, finding all matching keys at any nesting depth. $..price returns every value stored under a key named price anywhere in the document — inside arrays, nested objects, or any combination. This is equivalent to jq's .. | .price? // empty. It is particularly useful when you receive API responses from different service versions where the same field appears at different nesting levels. The recursive descent evaluator in this tool visits every node exactly once, so there is no risk of infinite loops on cyclical structures (pure JSON cannot be cyclical).

Array Slices and Unions

Python-style slicing [start:end:step] works exactly as in Python: [0:3] returns the first three elements, [-2:] returns the last two, and [::2] returns every other element. Union syntax [0,2,4] returns elements at specific indices. These are supported in jsonpath-ng (Python), Jayway (Java), and most server-side implementations. Note that some libraries, including the JavaScript jsonpath npm package, have partial support — always test against your target runtime before deploying to production. Use our JSON Schema Generator to validate the structure of responses returned by these expressions.

Comparing JSONPath Implementations

File Upload and URL Loading

Beyond pasting JSON manually, this tool accepts .json file uploads (drag-and-drop or the Upload button) and can fetch JSON from any public URL that returns CORS-permissive headers. If a URL responds with a CORS error (which is common for non-public APIs), download the file and upload it instead — the tool will show a clear message explaining this. The JSON Repair tool can fix malformed JSON (trailing commas, single quotes, unquoted keys) before you bring it here for path analysis. If you need to convert your JSON data to another format after querying, try JSON to TypeScript to generate interface definitions or JSON Schema Generator to create a schema for validation.