{ ≠JSON Diff

When comparing API responses or configuration files, spotting changes manually is tedious and error-prone. JSON Diff deeply compares two JSON documents and visualizes every difference in a collapsible tree: added fields in green, removed fields in red, value changes in yellow, and type changes in orange. Nested objects and arrays are compared recursively.

How to Use

1
Paste JSON
Paste the original JSON on the left and the comparison JSON on the right. Click 'Load Example' to load sample data.
2
Review the result
The diff tree appears immediately below. Icons indicate: + added, − removed, ~ changed, ⚠ type changed, = equal.
3
Toggle equal fields
Check 'Show equal fields' to also display unchanged fields. By default only changed fields are shown.
4
Collapse and expand
Click any object or array header to collapse or expand its subtree, letting you focus on the changes that matter.

Tips

💡Great for comparing API response versions or configuration file revisions.
💡For deeply nested JSON, collapse unchanged subtrees to focus on the differences.
💡The stat badges at the top give you a quick count of added, removed, and changed fields.
💡If both JSONs are identical, a blue badge confirms there are no differences.

FAQ

Q. Does array order matter when comparing?: A. Yes. Arrays are compared by index by default, so elements with the same value in different positions will be shown as changed. This reflects how most programs interpret arrays.
Q. Can it handle deeply nested JSON?: A. Yes. The tool compares recursively with no depth limit. You can collapse unchanged subtrees in the tree view to focus on what changed.
Q. When is JSON Diff most useful?: A. It is especially helpful for comparing API response versions, reviewing configuration file changes before deployment, or diffing database snapshots.
Q. What happens if two JSON documents are identical?: A. The tool displays a blue "No differences" badge. It can detect even invisible differences such as trailing spaces or Unicode normalization differences.