JSON Pointer Resolver and Patch Tester
Locate a value with an RFC 6901 pointer or safely preview RFC 6902 add, remove, replace, move, copy, and test operations.
JSON FormatterBase64 Encoder/DecoderHex ConverterURL Encoder/DecoderFavicon Path CheckerGoogle PreviewIP AddressHash GeneratorHTML Encoder/DecoderJWT DecoderUUID v4 GeneratorJSON Pointer & Patch TesterCache-Control Header BuilderSRI Hash Generator & VerifierOAuth PKCE Generator & VerifierHAR Viewer & Sanitizersecurity.txt GeneratorCSP Header BuilderPermissions-Policy BuilderCORS Header GeneratorContent-Disposition GeneratorCookie Header ParserJWK Thumbprint CalculatorData URI Generator
What is a JSON Pointer?
JSON Pointer is a standard syntax for identifying one value inside a JSON document. An empty pointer identifies the complete document. Each additional reference token begins with /, so /user/profile/email selects the email member inside profile, which is inside user.
Array positions use zero-based indexes. For example, /roles/0 selects the first item in the roles array. Property names containing a slash escape it as ~1, while a literal tilde becomes ~0. The property a/b is therefore addressed as /a~1b.
What is JSON Patch?
JSON Patch describes changes as an ordered array of operations. It is commonly sent with an HTTP PATCH request using the application/json-patch+json media type. This tester supports all six RFC 6902 operations:
addinserts an object member or array element.removedeletes an existing value.replacechanges an existing value.moveremoves a value and inserts it elsewhere.copyduplicates a value at another path.teststops the patch unless a value matches.
Operations are applied sequentially. Each successful operation changes the document used by the next operation, so array indexes can shift after an insertion or removal.
JSON Patch example
[
{ "op": "replace", "path": "/status", "value": "published" },
{ "op": "add", "path": "/tags/-", "value": "featured" }
]
The special - token appends to an array when used by an add operation. Other array references must be non-negative indexes without leading zeros.
Testing API changes safely
Paste a representative document and patch, then inspect the resulting JSON before sending the request to an API. A successful result only confirms the patch's JSON and pointer behavior; the destination API may still enforce authorization, schema, validation, version, or concurrency rules.
Privacy
Documents and patches are parsed locally in your browser and are not uploaded to MiniUtil. Even so, remove secrets and personal data before copying examples into tickets, documentation, or chat systems.
Standards and related tools
The resolver follows RFC 6901, and the patch runner follows RFC 6902. Use the JSON Formatter for general validation or the JSONL Converter for newline-delimited records.
Keep working