What JSON Patch is
An ordered set of changes for a JSON document
JSON Patch is a standard format for expressing targeted changes to JSON. A patch is an array of operations. Each operation identifies a location with JSON Pointer and adds, removes, replaces, moves, copies, or tests a value.
Applying RFC 6902 patches
Validate first, then apply every operation in sequence
Operation order matters. UtilityDock validates the document, patch array, operation fields, and JSON Pointer syntax before application. It then applies each operation to a copy of the input and stops with a detailed message if any step fails.
Common developer workflows
Test update payloads without changing source files
- Confirm an API patch request produces the intended response
- Test add, remove, and replace operations against fixtures
- Verify test operations before an optimistic update
- Preview configuration changes before deployment
- Reproduce a patch failure from logs or a bug report
- Convert a machine-readable patch into reviewable output
API versioning
Preview how a compatible patch changes a payload
Apply a proposed RFC 6902 request to a saved API document and inspect the updated result before integration. A successful local result confirms patch mechanics, but it does not replace the receiving API's own validation, authorization, or business rules.
Configuration management
Review deterministic changes to structured settings
JSON Patch can describe focused configuration changes without replacing the complete file. UtilityDock keeps the original source visible, applies operations to an isolated copy, and lets you export the updated JSON using readable or compact formatting.
Example
Replace a version and append a feature
| Input | JSON |
|---|---|
| Document | {"version":1,"features":["format"]} |
| Patch | [{"op":"replace","path":"/version","value":2},{"op":"add","path":"/features/-","value":"patch"}] |
| Updated | {"version":2,"features":["format","patch"]} |
Data Toolkit
Continue with every UtilityDock data workflow
FAQ
Questions about applying JSON Patch
Does UtilityDock upload my document or patch?
No. Your files never leave your computer. Parsing, validation, patch application, preview, copying, and download creation all happen locally inside your browser.
Which RFC 6902 operations are supported?
The applier supports add, remove, replace, move, copy, and test operations. Paths and from references use RFC 6901 JSON Pointer syntax.
What happens when an operation fails?
Application stops at the first failing operation. UtilityDock reports its position, operation type, path, and a specific reason such as a missing object member, invalid array index, or failed test.
Does applying a patch change my original file?
No. UtilityDock applies the operations to an in-browser copy. Your original source remains unchanged, and the updated JSON is available as a separate preview and download.
Can this tool generate or edit a JSON Patch?
No. Use the JSON Patch Generator to create a patch from two documents. Version 1 of this utility validates and applies an existing patch without interactive editing or history.