JSONPath Tester
Type a JSONPath expression, paste your JSON and see exactly what it matches. Filters run without eval, and your data stays inside your browser.
- No registration
- No server involved
- Filters in safe mode
- Shows paths and values
- Runs on your device. Files are never uploaded.
- Free and unlimited. No sign-up, no watermark.
JSON path tester in three steps
No account, no email, no waiting for an upload.
- STEP 01
Add your JSON
Paste it or open a .json file.
- STEP 02
Write the expression
For example $..author or $.items[?(@.price > 5)]. The default is $.* (everything at the top level).
- STEP 03
Read the matches
See matching values, or switch to paths and values to learn where each came from.
What JSON path tester does, and what it doesn't
We'd rather tell you up front than surprise you after the download.
What you get
- Recursive and filtered queriesUse .. for deep search, [0:3] for slices, [*] for all items and [?(@.x > 1)] for filters.
- Two result viewsShow only the matching values, or each match with its full path.
- Safe filter evaluationFilter expressions run through the library's own interpreter in safe mode, so no arbitrary code is evaluated.
- Match countThe result note tells you how many matches there were, including zero.
- Clear error messagesA bad JSON or an unusable expression returns a message you can act on.
Good to know
- One JSONPath dialectThe tester uses the jsonpath-plus library. Other libraries differ on edge cases, so test again in your own runtime if you rely on corners of the syntax.
- Filter scripts are limitedSafe mode supports comparisons and logic in filters, not full JavaScript code.
- Valid JSON firstIf the data does not parse, run it through the JSON validator.
Your data never leave your device
The tool runs inside your browser instead of on our servers, so there is nothing to upload, store or delete afterwards.
Typical online tool upload
Your file travels over the internet, sits on someone else's computer for a while, and you wait for the upload and the download.
Mediaextractr no upload
The tool loads into your browser once, then works on your file locally. Nothing is sent, so nothing can leak.
When people use JSON path tester
Develop an extraction rule
Test the path before you put it in an ETL job, test assertion or config.
Explore an unknown response
Find every field called 'id' with $..id.
Learn the syntax
Try small expressions and watch how results change.
Check automation steps
Verify the selector used by a workflow tool or a monitoring check.
Mediaextractr vs typical upload tools
| MediaextractrPrivate | Typical upload tools | |
|---|---|---|
| Your file is uploaded | Never | Yes |
| Sign-up needed | No | Often, after a few files |
| Daily file limit | None | Often 1–2 free files |
| Watermark | Never | Sometimes |
| Wait for upload & download | No | Yes |
| Speed on very large files | Depends on your device | Depends on their servers |
JSONPath in five lines
$ is the root. A dot or brackets step into a key. * means everything at that level and .. searches at any depth. Brackets also take indexes, slices and filters.
A filter such as [?(@.price < 10)] keeps the items where the test is true, where @ stands for the current item.
- $.store.book[0].title gives the first title.
- $..price gives every price anywhere in the document.
- $.items[?(@.stock > 0)].name lists names of items in stock.
- $.items[-1:] gives the last item.
Debugging an expression that returns nothing
An empty result usually means a key is spelled differently or sits one level deeper than expected. Switch the view to paths and values, then try $..* to see what exists. The JSON tree viewer shows the whole structure, and the JSON formatter makes the data easy to read.
Working with real data
Test with a realistic sample, because the shape of real responses often differs from the docs. Keep in mind that a path returning one match in your sample may return several, or none, in other payloads, so try an example with a missing field too.
Questions, answered
What JSONPath syntax does this support?
The jsonpath-plus dialect: root, child, wildcard, recursive descent, slices, unions and filter expressions.
Is my sample data uploaded when I run a query?
No. The expression is evaluated against your JSON by code in this tab, so real API responses stay with you.
Why is it described as 'safe' mode?
Filter expressions are handled by the library's own interpreter instead of eval, so pasted data or paths cannot run code.
How do I get the path of each match?
Switch 'Show' to paths and values. You get a list of path and value pairs.
How do I test a filter?
Use brackets with a question mark, for example $.users[?(@.age >= 18)].name.
Will the tester run on my phone?
Yes, on current mobile browsers. Typing brackets and dollar signs is easier on a hardware keyboard, though.