JSONPath Tester

Paste a JSON document and a JSONPath expression. The tool evaluates the path against the document and shows every matching value as a JSON array. Supports the common subset: $ root, .key dot navigation, [n] index (positive and negative), [*] wildcard, .. recursive descent, and ['key'] bracket-quoted keys. Useful for sanity-checking a JSONPath before pasting it into jq, Bruno, Postman, k6, or a CloudWatch query.

That subset is deliberate and it is worth knowing where it stops. Filter expressions like $.items[?(@.price > 10)], array slices like [1:3] and unions like [0,2] are not implemented and are reported as an unsupported bracket expression rather than silently returning nothing. Dot navigation also only accepts identifier-shaped names, so a key with a space or a hyphen has to be written in the bracket-quoted form.

The wider problem is that JSONPath was a blog post for twenty years before RFC 9535 standardised it in 2024, and the implementations that grew up in between do not agree. The order results come back in, whether a recursive descent visits a node before or after its children, what a filter does with a missing property, and whether the result is a flat list or a set of node references all vary by library. A path that behaves one way here can behave differently in the tool you paste it into, which is exactly why checking the shape of the result first is worth the detour.

A match of nothing and a match of null look different in the output but mean different things: an empty array means the path selected no nodes, while [null] means it selected one node whose value happens to be null. Reading the first as the second is a common source of confusion when a path is being used to assert that a field is absent.

Everything is evaluated in the page on the document you paste. Nothing is sent anywhere, which matters when the document is a production API response.