JSON Compare: step by step
- Paste the original JSON on the left and the changed JSON on the right, or open or drop a file on each side.
- The Changes table lists every difference by path, such as
$.user.email, with the old and new value. - Below it, both documents are formatted the same way and compared line by line.
- Leave Sort keys on to ignore key order, or turn it off to see order changes too.
Why not just compare the text?
Two JSON files can hold exactly the same data and still look completely different: one minified, one indented, keys in another order. A plain text diff marks every line as changed. JSON Compare parses both sides first, formats them identically and sorts the keys, so the only differences left are real ones.
Reading the changes table
- Added: the key or array item exists only in the changed JSON.
- Removed: it exists only in the original.
- Changed: it's in both, with a different value or type, like
"42"becoming42.
Arrays are compared item by item by position. If one item is inserted at the start of a list, every item after it shows as changed, and the line-by-line view below makes the insertion easy to spot.
Common uses
Checking what an API now returns compared with last week, reviewing config changes before a deploy, comparing test fixtures with real output, and finding why two environments behave differently.
Frequently asked questions
Does key order matter?
Not with Sort keys on (the default). In JSON, objects with the same keys and values are equal whatever the order.
Is my JSON uploaded?
No. Both documents are parsed and compared in your browser.
What if one side isn't valid JSON?
The status bar shows which side has the error, with its line and column. Fix it with the JSON Validator and paste it back.
Can I compare plain text instead?
Yes, use the Diff Checker for any text, code or document.
Updated