JSONPath tester

How it works

Useful before using a JSONPath expression in real code — an ETL script, a transformation rule in an integration tool, or a field extraction in a data pipeline — to verify it selects exactly what you expect without having to rerun an entire processing job. Paste your JSON document, write your expression ($.store.books[*].title for example) and click "Run" to see the exact result immediately.

Which JSONPath syntax is supported?

This tool implements a deliberately simple subset of JSONPath, sufficient for most common uses: key access ($.key), nested access ($.key.nested), array index access ($.array[0]), and the wildcard character [*] which returns all elements of an array ($.array[*], including combined with other segments like $.items[*].name). However, conditional filters ([?(@.price > 10)]), recursive descent (..), and array slices ([1:3]) aren't implemented: an expression using them will return an explicit error rather than a silently incorrect result.

What happens if the path doesn't match anything?

If a requested key or index doesn't exist in the document, the tool displays a clear error message indicating which segment of the path failed, rather than silently returning an empty value — handy for quickly spotting a typo in a key name or a JSON structure different from what you expected.

Path evaluation runs 100% locally in your browser via WebAssembly: your JSON, even sensitive, never leaves your device.