b2KIT

JSON Path Finder

Paste JSON and click any value to get its JSONPath or dot-notation path for use in code or queries.

Tested tool guide Tested browser tools Checked August 16, 2026

What JSON Path Finder does and how it behaves

JSON Path Finder maps a value inside pasted JSON to the sequence of object names and array indexes needed to reach it. After the JSON is parsed, clicking a displayed value produces its location in JSONPath or dot-notation form, making deeply nested data easier to address in code and query tools. The important distinction is that the result identifies the clicked location, not every occurrence of the same value. Two identical strings in different branches therefore have different paths.

How the result is produced

1

Selecting a node

Paste a complete, valid JSON value, then select a value in the displayed hierarchy. The resulting path starts from the document root and follows each containing object member or array position until it reaches that selection. Object members contribute their property names. Array elements contribute zero-based indexes, so the first element is addressed with index 0.

2

Reading path forms

JSONPath uses a root marker and a sequence of member or index selectors. Dot notation presents ordinary property names as dotted segments, while array positions remain indexed. Property names containing spaces, punctuation, or other characters that cannot form a plain dotted segment require a bracketed representation. Treat the displayed path as syntax, not as a copy of the selected value.

Good uses

  • Find the exact path to a nested field while preparing an API response mapping, such as locating a status inside an array of records rather than manually counting levels and indexes.
  • Translate a visually identified configuration value into a path that can be used by code, a JSONPath evaluator, a test assertion, or a data-extraction rule.
  • Compare two similarly named fields in separate JSON branches and capture the location of the intended one without confusing it with another occurrence of the same key or value.

Limits and checks

  • The pasted text must be valid JSON. JavaScript conveniences such as comments, trailing commas, single-quoted strings, undefined, and unquoted property names are not part of JSON and should not be treated as valid input.
  • A concrete array index refers to the element currently occupying that position. If elements are inserted, removed, or reordered later, the same path can point to a different element or no element.
  • JSONPath implementations do not all accept exactly the same syntax, especially older or extended dialects. Check that the consumer of the generated path supports its member-selector form before relying on it in production.

Common questions

Will the generated path find every value equal to the one I clicked?

No. The path describes the particular node selected in the pasted document. If the same string, number, boolean, or null appears elsewhere, those occurrences have their own locations. Finding all matching values requires a query with wildcard, recursive, or filter behavior supported by the destination JSONPath implementation, rather than the concrete location produced from one click.

Can I paste the JSONPath directly into JavaScript?

Not necessarily. JSONPath is a query syntax and is not a native JavaScript expression, so a JSONPath evaluator is normally needed for a path beginning at the JSONPath root. A dot-notation result may resemble JavaScript property access, but it still needs an object expression and valid handling for property names that require brackets or quoting.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools