What JSON Merge Patch is
A document-shaped instruction for updating JSON
JSON Merge Patch describes changes using familiar JSON structure. Object members are merged recursively, new values are added or replaced, and null removes a member. This utility applies that document to a separate local copy of your input.
RFC 7386 overview
Recursive objects and complete-value replacements
When the patch is an object, RFC 7386 processes each member against the corresponding target member. When the patch is an array or another JSON type, it replaces the target value completely. An empty object preserves an existing object but turns a non-object target into an empty object.
Merge Patch vs JSON Patch
Readable partial documents or precise operation lists
Merge Patch is concise for common object updates. JSON Patch uses ordered RFC 6902 operations and RFC 6901 paths, allowing precise array changes, tests, moves, and copies. Use the format required by the receiving API or configuration system.
Common API workflows
Preview an update response before sending a request
- Test an
application/merge-patch+jsonbody - Confirm which optional fields will be removed
- Preview partial account or resource updates
- Verify integration-test fixtures locally
- Review whole-array replacements before submission
- Share the resulting resource state in code review
Configuration management
Apply a focused settings update without changing the source
Paste a saved configuration document and a proposed Merge Patch to see the resulting state. For example, a patch can change a theme, remove a retired flag with null, and add a new setting while preserving unrelated members. The original text remains available for comparison.
Example
Change one property, remove another, and add a third
| Input | JSON |
|---|---|
| Document | {"version":1,"debug":true} |
| Merge Patch | {"version":2,"debug":null,"public":true} |
| Updated | {"version":2,"public":true} |
Data Toolkit
Continue with every UtilityDock data workflow
FAQ
Questions about applying JSON Merge Patch
Does UtilityDock upload my document or Merge Patch?
No. Your files never leave your computer. Validation, RFC 7386 application, preview, copying, and download creation all happen locally inside your browser.
Can an RFC 7386 Merge Patch be any JSON value?
Yes. An object patch merges members recursively. An array, string, number, boolean, or null patch replaces the target document as a complete value.
What does null do in a JSON Merge Patch object?
A null member removes the matching property from the target object. It does not set that property to a JSON null value.
How are arrays handled?
RFC 7386 replaces an array as a complete value. It does not merge or address individual array items. UtilityDock displays a warning when an array replacement occurs.
How is Merge Patch different from JSON Patch?
Merge Patch uses a partial JSON document. JSON Patch uses an ordered RFC 6902 operation array with RFC 6901 paths, making it suitable for precise array positions, tests, moves, and copies.
Does this utility modify my original file?
No. The original input remains unchanged. UtilityDock creates a separate updated preview that you can copy or download.