Compare two JSON documents
See added, removed, changed, moved and renamed values with paths on both sides, then export a standards-based patch.
Structural, not textual
The diff walks both parsed documents, so formatting and key ordering do not create noise. Arrays can be compared by index or by an identifier field, which makes record reordering visible as moves rather than unrelated changes.
- Ignore selected JSONPaths and optionally ignore values
- Rename and move detection for object keys and array records
- RFC 6902 JSON Patch and RFC 7396 Merge Patch export
- Three-way merge with explicit conflict resolution — conflicts are never auto-applied
Merge with a human in the loop
For three-way merges, unresolved paths keep the left value in the preview and are clearly marked. Creating the merged document writes a new tab and leaves both sources untouched.
Questions
Can I compare a document with an older version?
Yes. Keep both documents open as tabs, or save snapshots in the API workbench. Diff runs in a worker against both sources.
Does it ignore array order?
Only when you choose identity matching with a key such as id. Index matching intentionally reports reordering as changes or moves.
Go further in the studio
This page is intentionally a single-purpose tool. The full studio adds synchronized views, profiling, data-quality rules, schema comparison, three-way merge, transformation pipelines, timelines and local persistence. Open it with the same document and continue where this page stops.