Comparing two JSON objects means finding exactly which keys were added, removed or changed between them. To diff JSON, paste both versions into a JSON diff tool and read the list of differences by path. This is far more reliable than eyeballing two payloads. Here is how to do it and what the results mean.
Put the original JSON on the left and the changed JSON on the right.
The tool walks both objects key by key and records every difference.
Each change shows its full path, like user.address.city, so you know exactly what moved.
Copy the added/removed/changed report into a code review or bug ticket.
How does a JSON diff decide what changed?
A structural diff compares the two values recursively. For objects it matches by key, so the order of keys does not matter. For arrays, position matters — element 0 is compared to element 0. The JSON diff tool reports three kinds of change: added (in B only), removed (in A only) and changed (different values).
When is comparing JSON useful?
Use it to see what changed between two API responses, to review a config change, to debug why a request now behaves differently, or to confirm a migration kept the data intact. Pair it with the JSON formatter to tidy each side first, and explore more in the developer tools.
Tip: Format both JSON documents first so the inputs are valid and consistent — it makes the diff cleaner and avoids false “changes” from stray whitespace inside strings.
Compare your JSON now
Paste two JSON objects and see exactly what changed — free, in your browser.
Open the JSON Diff tool →Frequently Asked Questions
How do I compare two JSON files?
Paste each into a JSON diff tool and compare. It lists what was added, removed and changed, by path.
Does key order affect the result?
No — objects are matched by key, so reordering keys is not a change. Array order does matter.
Is my JSON uploaded?
No — both documents are compared in your browser and never sent anywhere.