How to Find the Path to Any Value in JSON Online
To find the path to a value in JSON, load your document into a JSON path finder and either type a dot and bracket path like data.items[0].name to see the value it points to, or browse the auto-generated list of every leaf path and click the one you want. This is far faster than counting brackets by eye in a deeply nested payload, and it gives you a path string you can paste straight into code. Here is how to do it end to end.
What the JSON Path Finder does
The tool does two complementary jobs. First, it evaluates a path you type: enter user.address.city and it walks the structure and returns exactly the matched value, updating live as you type. Second, it discovers paths for you: after loading your JSON it lists every leaf path β each terminal value in the document β with a preview, so you can explore an unfamiliar response without guessing. Click any listed path and it drops into the input and evaluates instantly.
Step by step
- Paste your JSON into the input and click Load JSON to parse it. Malformed JSON is rejected here, so you know the structure is valid before you explore.
- Type a path using dot notation for object keys and bracket notation for array indexes, for example
results[2].tags[0]. The matched value appears as you type. - Or browse the leaf-path list the tool generates and click an entry to evaluate it β handy when you do not yet know the field names.
- Copy the matched value or the full path list to reuse in your code, tests or documentation.
Path syntax you can use
| You want | Path syntax | Notes |
|---|---|---|
| An object key | user.name | Dot notation |
| An array element | items[0] | Zero-based index |
| Nested mix | data.rows[3].id | Combine freely |
| A key with special chars | config["api-key"] | Bracket + quotes |
| Root prefix | $.data.id | Leading $ optional, ignored |
If a path does not match anything, the tool says so clearly instead of throwing an error β which lets you tell the difference between a value that is genuinely missing and one that is present but null.
Why it runs in your browser
Every parse and evaluation happens locally in your browser with JavaScript. Your JSON is never uploaded or stored, so inspecting a private API response, an auth token payload, or a confidential data structure carries no exposure risk. As an installed PWA the finder also works offline, and because there is no round-trip to a server, results appear instantly even on large documents. Deeply nested structures are handled recursively, with very large documents capped at a sensible number of listed paths to keep the interface responsive.
Try the JSON Path Finder β free and 100% in your browser.
FAQ
Do I write the path with a leading dollar sign?
You can, but you do not have to. A leading $ is optional and simply ignored, so both $.data.id and data.id resolve to the same value. Use whichever matches the convention in your codebase.
How do I reference an array element versus an object key?
Use bracket notation with a numeric index for arrays, like items[0], and dot notation for object keys, like item.name. You combine them freely in one path, for example data.items[0].name.
What if my key contains a hyphen or a space?
Wrap it in bracket notation with quotes, such as config["api-key"]. Dot notation only works for simple identifiers, so quoted brackets are the safe way to reference any awkward key name.
Can the tool show me every path without me typing anything?
Yes. After you load your JSON it automatically lists every leaf path with a value preview. This is the fastest way to explore a response whose field names you do not yet know β just scan and click.
Related free tools
- JSON Diff β compare two documents and jump to changed paths.
- JSON Formatter β pretty-print before you explore.
- JSON Validator β confirm the document parses first.
- JSON to TypeScript β turn explored fields into typed interfaces.
Built by ByteVancer
ByteTools is a free product of ByteVancer, a software and web development studio building web apps, SaaS and custom software. When your data work outgrows a browser utility, explore how ByteVancer can build the API, integration or product you need.
Recommended reading
JSON Path Tips: Best Practices and Common Pitfalls
Expert tips for writing reliable JSON paths: quoting tricky keys, handling nulls vs missing values, indexing arrays safely, and avoiding brittle selectors.
JSON Path Finder Use Cases: Real Developer Workflows
Real scenarios where a JSON path finder speeds you up: debugging API payloads, writing selectors, mapping fields between systems, and building test assertions.
XOR Cipher Use Cases: CTFs, Learning, and Puzzles
Real use cases for the XOR cipher, from CTF challenges and teaching bitwise logic to lightweight obfuscation, with concrete worked examples.
XOR Cipher Tips: Keys, Security, and Common Mistakes
Pro tips and common mistakes for the repeating-key XOR cipher: key length, reuse pitfalls, format choices, and when to switch to real encryption.