What JSON Patch is
A compact list of changes between JSON documents
JSON Patch describes how to transform one JSON document into another. Instead of sending the complete updated document, a patch lists ordered operations such as adding a property, removing an array item, or replacing a value.
RFC 6902 overview
Standard operations with precise JSON Pointer paths
RFC 6902 defines JSON Patch as an array of operation objects. Each operation uses a JSON Pointer path from RFC 6901. UtilityDock generates add, remove, and replace operations in an order that transforms JSON A into JSON B.
Common developer workflows
Turn a before-and-after example into reusable change data
- Create a patch fixture for an automated test
- Document the exact change between API payloads
- Review configuration changes before deployment
- Generate an update request body for a compatible API
- Compare saved application-state snapshots
- Share a machine-readable change set in a code review
API versioning
Describe changes between response or request versions
Paste a version-one payload into JSON A and the version-two payload into JSON B. The resulting patch makes added fields, removed fields, and changed defaults explicit. Always confirm that the receiving API supports RFC 6902 before sending a generated patch.
Configuration updates
Review targeted changes without losing surrounding context
JSON Patch is useful when a configuration system accepts partial updates. The preview provides a concise change list while the original editors remain visible for comparison. Array operations are index-based, so reordered arrays deserve an additional review.
Example
Change one value and add one property
| Document | JSON |
|---|---|
| JSON A | {"version":1} |
| JSON B | {"version":2,"active":true} |
| Patch | [{"op":"replace","path":"/version","value":2},{"op":"add","path":"/active","value":true}] |
Data Toolkit
Continue with every UtilityDock data workflow
FAQ
Questions about generating JSON Patch
Does UtilityDock upload either JSON document?
No. Your files never leave your computer. Parsing, validation, comparison, patch generation, preview, copying, and download creation all happen locally inside your browser.
What JSON Patch operations can this generator create?
Version 1 creates add, remove, and replace operations. Those operations are sufficient to transform JSON A into JSON B. It does not infer move, copy, or test operations.
Are the generated paths standards compliant?
Yes. Every path is an RFC 6901 JSON Pointer as required by RFC 6902. Slashes and tildes in object keys are escaped correctly.
How are arrays compared?
Arrays are compared by index. Reordered values may therefore become replace operations rather than move operations, and the generator displays a warning whenever arrays are involved.
Can UtilityDock apply or edit the generated patch?
No. Version 1 generates, previews, copies, and downloads a patch. It does not apply, merge, or edit patch operations.