Toolvore

JSON Merge Patch

Apply an object-shaped JSON merge patch, preview null deletions and whole-array replacement, and download the resulting JSON locally.

This tool processes its input contents in your browser instead of sending them to a processing service. Page, asset and fixed usage-measurement requests are described on the Privacy page.

Apply RFC 7396 object-shaped merge patches with explicit null deletion and complete array/scalar replacement, retaining exact untouched numeric tokens.

How to use it

  1. 1Paste the target JSON and a separate merge patch.
  2. 2Apply it locally and inspect replacements and null deletions.
  3. 3Download or copy the resulting complete JSON document.

Example

Input
Target: {"a":"b","old":true} Patch: {"a":"c","old":null}
Output
{ "a": "c" }

The patch replaces a and deletes old. It does not call an HTTP endpoint.

What happens to your data

Patch application works on syntax trees in memory, preserving the two original texts separately. It sends no PATCH request and does not write an API resource, account or local file automatically.

Last updated November 2026

Preview a JSON Merge Patch against a target document before using it elsewhere. The patch resembles the object being changed: new members add data, existing members change and null-valued object members remove keys. It is a separate standard from JSON Patch's array of operations.

How it works

RFC 7396 applies a non-object patch by replacing the complete target value. An object patch recursively processes its members; an object target is created if the old value was not an object. Arrays are replaced as a whole rather than merged item by item. Setting an object member to null means deletion, so this format cannot express every change involving explicit null-as-data. Missing keys selected for deletion have no effect.

The local result preserves numeric source tokens and reports whether the produced value changed. No endpoint is contacted, saved configuration is modified or permission inferred. Original inputs remain separate. The combined merged values must also fit 128 KiB before pretty-printing and at most 5,000 values. The result is reparsed under those structural limits; a combined result that exceeds them fails rather than being truncated. Use the complete copy/download for downstream review.

Input is bounded to 128 KiB, depth 24 and 5,000 values; duplicate property names and unpaired Unicode surrogates fail. Results have a bounded preview, while copy/download contains the complete generated output. Editing input or settings invalidates old results. Examples are excluded from workflow activity.

Worked example: JSON Merge Patch example

Input
Target: {"a":"b","old":true} Patch: {"a":"c","old":null}
Result
{ "a": "c" }

The patch replaces a and deletes old. It does not call an HTTP endpoint.

Common use cases

  • Review an object-shaped API patch without sending it.
  • Apply a deliberate configuration overlay with documented deletion semantics.
  • Create small test fixtures while retaining exact large numeric IDs.

Frequently asked questions

Is this JSON Patch RFC 6902?+

No. RFC 6902 uses operation arrays such as add/remove/replace with paths. Merge Patch RFC 7396 uses an object-shaped document and null deletion.

Are arrays concatenated?+

No. A patch array replaces the complete old array or other target value.

Can null be assigned to a member?+

An object member whose patch value is null is removed. Use a different editing format when you need to assign explicit null as member data.