DEVELOPER FLAGSHIP
JSON Path Explorer
Simple dot and bracket paths only, not full JSONPath.
At a glance
JSON Path Explorer — JSONPath Explorer queries into a JSON document the way a search query finds rows in a database — one expression pulls out exactly the values you need from a response too big to read.
Free for the core workflow, no account required. Parsing and transformation are performed locally in the browser from the data you enter.
About JSON Path Explorer
JSONPath Explorer queries into a JSON document the way a search query finds rows in a database — one expression pulls out exactly the values you need from a response too big to read.
A large API response can hold thousands of values, and the one you need is buried ten levels down. JSONPath is a small query language for reaching into that structure: $ is the root, .child walks down a key, [0] picks an array index, .. searches at any depth, and [?()] filters by a condition. Worked example — take a small book store: {"store":{"book":[{"title":"Sayings of the Century","price":8.95},{"title":"Sword of Honour","price":12.99},{"title":"Moby Dick","price":8.99},{"title":"The Lord of the Rings","price":22.99"}]}}. The expression $.store.book[?(@.price < 10)].title returns two titles: "Sayings of the Century" (8.95) and "Moby Dick" (8.99). The filter kept only books under 10, and the trailing .title projected just the titles — two values out of a document that also holds authors, categories, and a bicycle entry. Change the filter to @.price < 13 and the result grows to three titles, adding "Sword of Honour" at 12.99. The same document queried with $.store.book[*].title returns all four titles, and $..price returns all four prices: 8.95, 12.99, 8.99, 22.99. Table — the operators that do most real work: $ root, @ current node in a filter, .child a named key, [n] the nth array item, [*] every item, .. recursive descent to any depth, and [?(@.price < 10)] a filter on a condition. Before / after — before: scrolling a 3,000-line response looking for every price under 10; after: one expression returning ["Sayings of the Century", "Moby Dick"]. Picture a filing cabinet: dot notation opens named drawers one by one, .. searches every drawer at once, and the filter only pulls the folders that match. Recursive descent earns its keep on messy real data. The expression $..author searches every level at once, and on the store above it returns four names: Nigel Rees, Evelyn Waugh, Herman Melville, and J. R. R. Tolkien — the authors of the four books, found without knowing that some records nest deeper than others. The same trick finds every id in a paginated export with $..id, whatever depth the pagination wrapper adds. One developer step usually leads to the next. The URL Parser takes a complete web address apart into its labelled pieces and the XML Formatter parses a compressed XML document into its real tree and reprints it with clean indentation. And the Luhn Checksum Validator checks a number with the mod-10 checksum behind credit cards, IMEI numbers, and national ids. Sources: Stefan Gössner, "JSONPath — XPath for JSON" (2007); IETF RFC 9535, JSONPath: Query Expressions for JSON (2024); MDN Web Docs, "JSON" (accessed November 2026). Content last reviewed: November 2026. JSONPath lets you query into JSON documents the way XPath queries XML: $.store.book[?(@.price < 10)].title finds cheap book titles. It is the fastest way to extract one value from a large API response without writing code.
Primary objective: Simple JSON path traversal locally in the browser.
Privacy assurance: Parsing and transformation are performed locally in the browser from the data you enter.
How to Use JSON Path Explorer
- Paste the JSON document — a full API response, a config file, or a data export.
- Start with a plain path such as $.store.book[0].title and confirm it returns one value.
- Add a filter when you need a subset, for example [?(@.price < 10)], and test it without the filter first if it returns nothing.
- Use .. when you are unsure of the nesting depth — $..price finds every price key anywhere in the document.
- Copy the matched values, or refine the expression until the result is exactly the list you need.
Key Use Cases & Applications
- Pulling every error message out of a verbose API response without reading the whole body.
- Extracting a list of ids from a paginated dataset for the next request.
- Checking which items in a catalogue fall below a price threshold.
- Verifying that a nested field exists in every record of an export.
- Pulling all error messages out of a verbose API response.
- Extracting a list of IDs from a paginated JSON dataset.
Frequently Asked Questions
Why does my filter return an empty list?
Usually the path before the filter is wrong, or a number is quoted as a string. Test the path without the filter first — if that returns values, the filter condition is the problem.
How do I get the cheapest book, not just cheap books?
JSONPath filters but does not sort. Pull the prices with $..price, sort them in your code, or filter with an exact value once you know the minimum.
What does $..author return?
Every author value at any depth in the document — recursive descent searches the whole tree, which is useful when records nest at different levels.
Can I combine two conditions in one filter?
Yes, with && and ||: [?(@.price < 10 && @.category == "fiction")] keeps only books that satisfy both. Mind the quoting — strings need quotes, numbers do not.
By Shehzad Hussain — owner and editor of ExpTool, based in Multan, Pakistan. He builds and tests every tool on this site himself.
Last updated: 2026-11-04