What JSON Pointer is
A precise address for any value in JSON
JSON Pointer is an IETF standard for identifying a value inside a JSON document. A pointer follows object keys and array indexes from the root, so /users/0/name selects the name field of the first user. It is simpler and more narrowly defined than a query language.
Common developer workflows
Move from a large document to one exact node
- Locate a deeply nested API response field
- Copy a stable reference into an issue or test
- Inspect value types before writing integration code
- Find repeated keys across different branches
- Confirm an array index in an example payload
- Review configuration without editing the source
API debugging
Identify the failing response field unambiguously
Paste a request or response body, search for the relevant key, and copy its generated pointer into a bug report, automated test, or validation message. Because the explorer shows type, depth, child count, and value together, unexpected shapes are easier to spot.
Schema references
Understand paths used by JSON tooling
JSON Schema validators commonly report instance locations using JSON Pointer-style paths. The same notation also appears in references and other JSON standards. This explorer helps you trace those paths without applying a schema or changing the document.
Examples
Keys become escaped pointer tokens
| JSON location | JSON Pointer | Meaning |
|---|---|---|
| Document root | empty string | The complete document |
| First user name | /users/0/name | Object key, array index, object key |
| Key named api/version | /api~1version | Slash escaped as ~1 |
| Key named active~draft | /active~0draft | Tilde escaped as ~0 |
Data Toolkit
Continue with every UtilityDock data workflow
FAQ
Questions about JSON Pointer navigation
Does UtilityDock upload my JSON?
No. Your files never leave your computer. Parsing, validation, tree creation, searching, and copying all happen locally inside your browser.
What standard does this JSON Pointer explorer use?
It generates RFC 6901 JSON Pointers. Each path starts at the document root and identifies object properties or array indexes.
Why is the root pointer empty?
RFC 6901 defines the empty string as the pointer to the entire JSON document. UtilityDock labels it clearly as the root while copying the standards-compliant empty value.
How are slashes and tildes handled in property names?
A slash in a property name becomes ~1 and a tilde becomes ~0 inside a JSON Pointer token.
Can I edit JSON or apply JSON Patch operations here?
No. Version 1 is a read-only explorer for validation, navigation, search, inspection, and copying references.