List every position in a JSON document with the RFC 6901 pointer that names it, resolve a pointer to its value, and get the tilde and slash escaping right.
Waiting for JSON
Every position in the document with the RFC 6901 pointer that names it.
The positions appear here
Every addressable position with its pointer, its dot path, and a preview of what it holds.
JSON Pointer Explorer runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Every addressable position in a document, with the pointer that names it and a preview of what it holds. Type a pointer to see what it resolves to, or filter the list and copy the one you need.
Pointers rather than dot paths, because JSON Pointer is RFC 6901 and it is what JSON Patch, JSON Schema references, OpenAPI and most validation error messages are written in. When a validator reports that a particular path must be a number, this is the notation it is speaking. A dot path is friendlier to read and is not a standard, so both are shown and the pointer is the one you copy.
The escaping is the part people get wrong. Inside a pointer token a tilde is written as tilde-zero and a slash as tilde-one. The order matters coming back: unescape the slash form first and a tilde followed by a one and a zero wrongly becomes a slash instead of the literal it stands for. A key containing a slash is rare and the resulting pointer is unreadable, which is exactly when a tool that gets it right earns its place.
The empty pointer means the whole document rather than nothing, which surprises people and is correct. A pointer ending in a hyphen means one past the end of an array; it exists so a JSON Patch can append, and it never resolves on a read — so it is reported as not found rather than as an error, because that is what it is.
When a pointer does not resolve, the token it failed at is named, which is more useful than a plain failure: it tells you how far the path was right. Nothing is uploaded — the document is parsed in the page.
The RFC 6901 notation for one position in a JSON document, written as slash-separated tokens from the root. It is the form JSON Patch, JSON Schema references and most validation errors use.
Escape it as tilde-one inside the token. A tilde itself is escaped as tilde-zero. The order matters when decoding, which is the detail most hand-written implementations get wrong.
Because that is what the specification says it means. It is a zero-length sequence of tokens, which addresses the root. Useful in a patch that replaces the entire document.
Because it means one past the end of an array. It exists so a patch can append an element and has nothing to point at on a read, which is why it is reported as not found rather than as a malformed pointer.
JSONPath is a query language with wildcards and filters that can match many positions. A JSON Pointer names exactly one and has a specification behind it, which is why patches and schemas use it.
No. It is parsed in your browser, so a document containing real data never leaves the page.