๐ฅ JSON Input
๐ Pointer Path List
๐ค Pointer Escape Tool
Enter a key name to auto-generate the escaped Pointer fragment
Input JSON to auto-generate all RFC 6901 paths, search, filter, extract values and handle escaping
Zero Dependencies ยท Works OfflineEnter a key name to auto-generate the escaped Pointer fragment
JSON Pointer Explorer is a free online developer tool that automatically traverses JSON data and generates all RFC 6901 standard JSON Pointer paths, displaying the corresponding value and type for each path. It supports path searching, type filtering, value extraction, and key name escaping. Ideal for API debugging, JSON Patch authoring, and JSON Schema path referencing. All processing happens locally in your browser โ no data is ever uploaded to servers.
1. Paste JSON data into the input box, or click "Load Example".
2. Click "Explore Paths" to generate the full Pointer path list.
3. Use the search box and type filters to quickly locate target paths.
4. Click any path to view its detailed value and copy it.
Developers writing JSON Patch can quickly find Pointer paths for target fields, avoiding manual path construction errors.
When writing JSON Schema $ref references, you need precise Pointer paths to sub-schema definitions.
When debugging complex JSON responses from REST APIs, quickly locate nested field paths and values.
JSON Pointer (RFC 6901) is an IETF standard for addressing values in JSON documents. An empty string "" represents the entire document, and /-separated paths reference sub-values. Special characters ~ and / in key names must be escaped: ~ becomes ~0, / becomes ~1. JSON Pointer is a core dependency of JSON Patch (RFC 6902) and JSON Schema. Compared to JSONPath, Pointer is simpler but can only reference a single deterministic location โ it does not support filtering or wildcards.
RFC 6901 standard for referencing JSON values using /-separated paths, e.g. /user/name.
~ becomes ~0, / becomes ~1. For example, key a/b~c becomes /a~1b~0c.
JSON Pointer is an RFC standard for precise single-value references. JSONPath supports filters/wildcards but is not standardized.
The empty string "" represents the entire root JSON document.
Arrays use numeric indices, e.g. /items/0 for the first element, /- for appending.
No. All processing happens locally in your browser.