JSON Path Finder

JSON documents get deep fast. Nested arrays inside nested objects inside API responses are the norm, and finding the right path to a specific value — especially one you need to extract repeatedly in tests or pipelines — is surprisingly fiddly. This JSON path finder gives you an interactive tree view of any JSON and, when you click on a value, shows the exact JSONPath or JMESPath expression to reach it. No more counting array indices by hand.

The tree is collapsible and searchable. Click a key to expand, click a value to see its path, and use the search box to filter keys or values across the whole document. Copy the path with one click. Switch between JSONPath (the de-facto standard, used by Postman, jq-like tools, and many APIs) and JMESPath (used by AWS CLI, Ansible, and cloud-native tools). Both flavors produce queryable expressions that select your target value deterministically.

Once you have a path, the tool lets you evaluate it against the document and shows every matching value. This is useful for verifying the expression does what you expect before pasting it into your test assertion or pipeline config. For arrays, the tool offers both specific-index expressions (results[0].id) and wildcard expressions (results[*].id) so you can pick the one that fits your need. Multi-line JSON with gigabytes of data may need jq at the command line, but for most API responses and config files, this browser-based tool is faster and friendlier.

JSONPath was proposed by Stefan Gössner in 2007 as the JSON equivalent of XPath for XML. The syntax uses $ as the root, . to descend into objects, [n] for array indices, and [*] as a wildcard. $.store.book[0].title selects the title of the first book. JSONPath has several implementations with minor differences; RFC 9535 was published in 2024 to standardize.

JMESPath is an alternative query language standardized by the AWS community. It uses dot notation for object access, bracket notation with wildcards or slices for arrays, and pipes for transformation (results[].name | sort(@)). JMESPath is used in the AWS CLI's --query option, Ansible's json_query filter, and many cloud tools. It is slightly more expressive than JSONPath for transformation but has a different learning curve.

This tool parses your JSON into a tree, renders it as an interactive DOM, and on value selection generates the correct path in both syntaxes. For arrays, it offers both specific-index paths (useful for debugging one value) and wildcard paths (useful for extracting all values in an array). Evaluation uses a lightweight client-side JSONPath/JMESPath engine that handles the most common use cases; for very deep nested data or filter expressions with complex predicates, falling back to jq or a server-side tool is sometimes necessary. All processing is client-side so your JSON never leaves the browser.

Counting array indices by hand to write JSONPath queries is slow and error-prone. jq is powerful but command-line only and has its own syntax. IDE plugins for JSON paths help but lock you into an editor. This tool gives you an interactive tree view with one-click path copy, supports both JSONPath and JMESPath, evaluates paths live so you verify before using them, and runs client-side so your data stays private. Fastest way to turn an API response into a test assertion or a pipeline query.