JSON Pointer explorer

Resolve an RFC 6901 JSON Pointer and inspect a bounded node-path table with safe numeric parsing.

Your input

Outputs are cleared when the input changes.

Result

Enter your data or use the example, then run the tool.

Worked example

For {"a/b":{"~key":[42]}}, /a~1b/~0key/0 resolves to 42.

An empty pointer returns the entire document; a missing path is a clear error.

Method

Decode each pointer token according to RFC 6901 and read only an object’s own properties.

Numeric tokens are checked before native JSON parsing so unsafe integers, overflow and nonzero underflow are rejected.

Limits

JSON limit 5 MiB and depth 100; pointer at most 100 tokens. No JSONPath, JavaScript, URI fragments or remote refs.

Decimal fractions retain normal IEEE-754 JSON semantics; this is not an arbitrary-precision JSON decimal parser.

Sources

RFC 6901: JSON Pointer

Your inputs stay on this device. Only optional, consented page visits are measured. Input values, files, filenames and processing logs are not sent to Analytics.

When switching languages, text, settings and selected files are temporarily kept on this device. Transfers are removed after restoring; interrupted transfers are cleaned up on a later visit. Inputs and files are never uploaded.