JSON Three-way Merge Review
Reconcile two JSON revisions against a common base and expose atomic-array and scalar conflicts.
Loading tool…
How to use JSON Three-way Merge Review
Automatically preserve independent object edits using a declared ancestor. When changes conflict, review the path and choose a whole-side policy instead of silently inventing a resolution.
- Enter common base json, left revision json, right revision json.
- Choose the settings for json three-way merge review, then run the tool.
- Review the result and any limitations before copying or downloading it.
Good to know
- 100,000 characters per document,10,000 values,40 levels and1000 conflicts. Arrays are compared/replaced as complete values.
- A side preference applies to every conflict, including deletion. Report-only emits no merged document if conflicts remain.
- Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.
Common questions
Why is a common ancestor required?
It distinguishes a change made on one side from an edit made differently on both sides.
Is this input sent to a server?
No. The application processes this input inside your browser tab and does not save it to persistent storage.
Keep going with related tools
All data →JSON Diff
Compare JSON values structurally and list added, removed, or changed paths.
DataJSON Merge Patch Workbench
Apply RFC7396 object-shaped merge patches or draft a patch between two JSON documents.
DataJSON Patch Applier
Apply bounded add, remove, replace, move, copy and test operations to a cloned JSON value.
DataKeyed JSON Record Reconciler
Apply explicit whole-record keyed upserts and deletions while preserving stable source order.
TextConservative Three-way Text Merge
Reconcile two literal line revisions against a common base, with explicit conflict evidence and human side, base or custom decisions.