JSON Property Path Inspector guide
Resolve one explicit property or array path in a JSON document and copy the selected value.
What this tool does
JSON Property Path Inspector parses a complete JSON document, follows a simple path, and displays the value found at that location. It supports dot properties such as $.settings.theme, numeric array indexes such as $.items[0], and double-quoted bracket keys such as $["full.name"].
The result includes a normalized path, the resolved value type, and a formatted representation of the value. Objects and arrays are displayed as indented JSON, strings remain valid JSON string values, and numbers, booleans, and null retain their JSON meanings.
This is deliberately a property-path inspector rather than a complete JSONPath query engine. Wildcards, filters, slices, unions, scripts, and recursive descent are not supported. The narrower syntax makes each lookup deterministic and avoids evaluating code from the entered path.
How to use it
- Paste a valid JSON object, array, or primitive value.
- Enter a path beginning with
$, or enter a top-level property directly. - Use dot notation for simple property names.
- Use
[0]for an array index or["key.with.dots"]for a complex key. - Select Inspect path and copy the resolved value.
Use $ by itself to inspect the entire root value. Array indexes start at zero, matching JavaScript and common JSON tooling.
Benefits
- Resolves explicit object and array paths without executing code
- Supports complex property names through quoted brackets
- Distinguishes arrays, objects, strings, numbers, booleans, and null
- Reports the exact segment where traversal fails
- Keeps the JSON document entirely in the browser
Syntax and limitations
JSON object keys are case-sensitive. user.name and user.Name can refer to different values. A numeric bracket token is treated as a zero-based index or numeric property, while quoted brackets represent string keys. Single-quoted bracket keys are not accepted because JSON itself defines double-quoted strings.
The tool performs one direct lookup and does not search for every matching property. It also does not modify the source, validate a schema, infer optional fields, or evaluate expressions. If a path stops at a string or number before all tokens are consumed, the report explains that the current value cannot contain the next segment.