a No file open
Create a new file or open an existing one from the sidebar
JSONPath Tester
Type a JSONPath expression and the matches update as you type.
How do I test a JSONPath expression?
Type a JSONPath expression into the query box and the matching values show up straight away. The document loaded above is the classic bookstore example, so the built-in examples like $..author and $.store.book[?(@.price<10)] already have something to match, press the help button next to the query box to see them.
To query your own data, press Ctrl+V or Cmd+V outside the query box and it opens in a new tab, or switch to Code view and paste it there. The copy button grabs the results as JSON.
- Press Ctrl+V or Cmd+V outside the query box to load your JSON.
- Type a JSONPath expression starting with $.
- Copy the matches with the copy button.
Example
$.store.book[?(@.price < 10)].title[
"Sayings of the Century",
"Moby Dick"
]Questions people ask
Which JSONPath syntax is supported?
Queries run on jsonpath-plus, which covers the usual syntax: $ for the root, dot and bracket child access, .. for recursive descent, * wildcards, slices like [0:2], unions like [0,1] and filters like [?(@.price<10)]. Most everyday queries look the same under RFC 9535, the JSONPath standard published in 2024, though filter details vary a little between implementations.
What's the difference between JSONPath and jq?
JSONPath selects values out of a document and it's built into lots of API testing tools and libraries. jq is a whole command line language that can also reshape and transform JSON. If you only need to point at data, JSONPath is the simpler of the two.
How do I find the path to a value I can see?
Switch to Tree view, right-click the value and choose Copy path. That's the JSON Path Finder.
Is my data uploaded anywhere?
No, this runs entirely in your browser, so nothing you paste is sent to a server. The only feature that sends data anywhere is the optional AI assistant, and only when you actually ask it something.