← All Tools
Json Path Finder🔒 100% local
Find all JSON paths in a JSON document. All processing occurs locally in your browser.
Json Path Finder: related tools
Walks every leaf of a JSON document and prints the path to it in dot and bracket notation starting from $, an equals sign, and the leaf's value. An object key extends the path with .key, and an array element with its numeric index in brackets. It is a complete enumeration of the document's leaves, computed in the browser with no request leaving the page.
JSON Path Finder: how to use it
- Paste the document into the text area.
- Press Find Paths.
- Read the list of path = value lines in the result block and copy the ones you need.
JSON Path Finder: worked example
{"user":{"name":"Ada","age":36}}becomes$.user.name = "Ada"
$.user.age = 36This is the tool's own dotted notation, not RFC 9535 JSONPath syntax - there are no filters, wildcards or recursive descents.
{"items":[{"id":1},{"id":2}]}becomes$.items[0].id = 1
$.items[1].id = 2JSON Path Finder: when to use it
- Working out the exact key path to a nested value before writing an accessor or a jq filter.
- Handing a colleague a full inventory of the fields present in an unfamiliar payload.
- Checking that a config document really contains the leaves your code expects.
JSON Path Finder: what it does not do
- It is an enumerator, not a query engine: you cannot select one path, filter by value, or use wildcards - every leaf is always dumped.
- An array of objects is expanded element by element, so a 500-row response produces 500 lines per column.
- Leaves are skipped silently when there is nothing scalar to print: an empty object, an empty array and a null value all contribute no line, which can make a document look emptier than it is.