DevKits

JSON Path Finder — Find JSONPath by Key or Value

Search JSON for keys or values and get back JSONPath expressions for every match. Reverse of a JSONPath tester — perfect when you know what you're looking for but not where it lives. 100% local.

Last updated:

535 chars · 11 lines
  • $.store.book[1].category
    stringmatched: value= "fiction"
    dot: store.book[1].category
  • $.store.book[2].category
    stringmatched: value= "fiction"
    dot: store.book[2].category
  • $.store.book[3].category
    stringmatched: value= "fiction"
    dot: store.book[3].category

Search JSON by key or value to get back the JSONPath (and dot-path) for every match. Reverse of a JSONPath tester — perfect when you know what you're looking for but not where it lives.

What is JSON Path Finder?

A JSON path finder does the opposite of a JSONPath tester. Instead of running a JSONPath expression against JSON and getting matching values, you supply the key or value substring and get back the JSONPath (and dot-path) for every occurrence. It's the fastest way to answer questions like 'where is the author field in this deeply nested API response?' or 'which paths in this config file mention `staging`?'. This tool walks the entire tree once and returns every match with its full path, node type, and a truncated value preview so you can click the right one immediately.

How to find JSONPath from a key or value

  1. 1Paste your JSON into the input editor on the left.
  2. 2Type a key substring, a value substring, or both. Results update as you type.
  3. 3Toggle 'Exact key' / 'Exact value' if substring matching is producing too many hits.
  4. 4Click the copy icon on any result row to copy the JSONPath to your clipboard.

Tips & Best Practices

  • Use both key and value filters together to precisely locate a specific field: key = 'author', value = 'Tolkien'.
  • For non-identifier keys (with dashes, spaces, or dots), the tool automatically switches to bracket notation ($['field-name']) in the JSONPath output so the expression parses correctly in downstream tools.
  • Results are capped at 500 matches. If you hit the cap, narrow the query — running an unfiltered search on large payloads isn't useful anyway.

Frequently Asked Questions

How is this different from a JSONPath tester?

A JSONPath tester runs an expression like $.store.book[*].author against JSON and returns matching values. This tool goes the other way: you say 'find every field named author with value containing Tolkien' and get back the JSONPath (and dot path) for each match.

What kinds of queries can I run?

You can filter by key (substring or exact), by value (substring or exact), or both simultaneously. When both are provided, results must match both dimensions. Case-sensitivity is a per-search toggle.

Which path format is returned?

Both. Each match shows a full JSONPath (e.g. $.store.book[0].author) and a dot-notation path (store.book[0].author). Non-identifier keys (with dashes, spaces, etc.) are auto-quoted in JSONPath output for correctness.

What's the maximum JSON size?

In practice, browsers handle documents up to a few MB smoothly. Results are capped at 500 matches per search to keep rendering responsive — narrow your query if you're hitting the cap.

Is my JSON uploaded anywhere?

No. All searching runs locally in your browser as client-side JavaScript.

Related Tools