JSON Diff vs JSON Patch vs Merge Patch

Use a diff for human review

JSON Diff & Compare reports added, removed, and changed paths without claiming that the report is an update instruction. It is the right first step for code review, configuration checks, and deciding whether a patch is appropriate.

Use JSON Patch for precise operations

RFC 6902 represents updates as an ordered array of operations such as add, remove, and replace. Paths use JSON Pointer, so array indexes and exact locations can be addressed.

{ "name": "Ada", "active": false }

[
  { "op": "replace", "path": "/active", "value": true }
]

Use Merge Patch for object-shaped updates

RFC 7386 represents the desired changes as a partial JSON object. Object members merge recursively, while a null member removes the corresponding target member. Non-object patches replace the entire target.

{ "name": "Ada", "active": false, "role": "viewer" }

{ "active": true, "role": null }

Choose by contract and ambiguity

Choose the format the receiving API specifies. If you control the contract, JSON Patch is more explicit and handles arrays precisely. Merge Patch is easier to read for object updates, but cannot use null as an ordinary replacement value because null means removal.

1. Compare the source and target documents.
2. Confirm whether the receiving endpoint accepts RFC 6902 or RFC 7386.
3. Generate and review the patch.
4. Apply it locally to a copy and compare the result with the intended target.

Common questions

FAQ