JSON Compare
Diff two JSON payloads from different sources and highlight what changed.
First source
Second source
About JSON Compare
JSON Compare diffs two JSON payloads structurally and highlights what was added, removed or changed — by key and value rather than by text line. That matters because two payloads can be semantically identical while looking completely different as text: key order, whitespace and formatting all become irrelevant in a structural diff.
Typical uses in QA: comparing an API response before and after a deploy, checking staging against production, or verifying that a migration changed exactly the fields it was supposed to. Paste both versions and the differences are listed explicitly instead of hiding in a wall of text.
How to use
- Paste the first payload into "JSON A" and the second into "JSON B".
- Click "Compare".
- Review the differences: added keys, removed keys and changed values are each called out with their paths.
- "Load sample" fills both sides with a small example so you can see the output format first.
Frequently asked questions
Does key order or formatting affect the comparison?
No. Both documents are parsed first, so only actual structure and values are compared. Reordered keys or different indentation produce no differences.
How are nested differences reported?
Each difference is reported with its path into the object (for example user.address.city), so you can locate the changed field in deeply nested payloads without scanning manually.
Can I diff two API environments safely?
Yes — the comparison runs entirely in your browser, so pasting responses from internal environments does not send them anywhere.