Developer Utilities

JSON Pointer Explorer

Resolve RFC 6901 JSON Pointers and index leaf value paths.

JSON Pointer · RFC 6901
Supports / paths and # URI fragments; ~0 means ~ and ~1 means /.
Resolved value
"Ada"
Leaf pointer index
Shows up to the first 200 leaf values.
PointerValue preview
1
"Ada"
"admin"
"editor"
2
"Lin"
"viewer"
1
false

JSON Pointer Exploration

Resolve values with RFC 6901 paths. An empty string selects the full document; / separates tokens; ~ is encoded as ~0 and / as ~1 inside keys.

Supported Forms

  • Plain pointers such as /users/0/name
  • URI fragments such as #/users/0/name
  • The leaf index shows up to 200 values and lets you select a pointer

Frequently Asked Questions

What standard is JSON Pointer?
RFC 6901. Slash-separated paths locate values in a JSON document: /users/0/name points at the name field of the first user; the empty string points at the whole document. It underpins JSON Patch (RFC 6902), OpenAPI $ref references, and JSON Schema.
How do I write a path for keys containing / or ~?
Per the standard, ~ is escaped as ~0 and / as ~1: the key "a/b" is addressed as /a~1b. This is the classic gotcha — without escaping, the key silently splits into two levels.
URI fragment form (#/a/0) versus plain form?
The fragment form starts with # and is used to reference part of a JSON document from a URL — OpenAPI’s "$ref": "#/components/schemas/User" is exactly this. Both forms share the same path semantics, and the tool accepts either pasted directly.