Developer Tools
JSON Diff & Compare
Compare two JSON documents and see exactly what changed — added, removed and modified values, listed by path. Comparison is semantic, so key order and formatting never get in the way. Everything runs in your browser.
See what actually changed, not what got reformatted
Comparing JSON by eye — or with a line diff — is painful when keys move around or indentation changes. This tool parses both documents and compares them by meaning, producing a clean, path-based list of every added, removed and modified value so you can spot a regression or confirm an update in seconds.
Great for
- API responses — diff a baseline against a new release.
- Config & fixtures — verify exactly what a change touched.
- Contract testing — catch unexpected schema drift.
- Code review — explain a JSON change at a glance.
Frequently asked questions
How is this different from a plain text diff?
A text diff compares line by line, so reformatting or reordering keys shows up as noise. This tool parses both sides into JSON and compares them semantically — key order and whitespace are ignored, and you get a precise list of value changes by path instead.
How are arrays compared?
Arrays are compared by position (index 0 to 0, 1 to 1, and so on). Items present on only one side are reported as added or removed; items at the same index that differ are reported as changed, recursing into nested objects and arrays.
What do added, removed and changed mean?
Added means the path exists only in the second (changed) document, removed means it exists only in the first (original), and changed means the path exists in both but the value differs. Each change shows the before and after value.
Is my data uploaded?
No. Both documents are parsed and compared locally in your browser. Nothing is sent to a server.