JSON diff
Compare two JSON documents structurally, so reordered keys do not show up as changes.
Runs in your browser — nothing you type here is sent anywhere.
before
after
arrays
Arrays compare position by position, so a reordered list reads as a change at every index that moved. Object keys never depend on order, either way.
2
added
1
removed
5
changed
8 differences: 2 added, 1 removed, 5 changed.
added
before
(absent)
after
["fast-path"]
removed
before
true
after
(absent)
changed
before
"iad"
after
"sfo"
changed
before
"sfo"
after
"iad"
changed
before
3
after
5
added
before
(absent)
after
true
changed
before
3
after
5
number → string
before
2500
after
"2500"
A text diff on JSON is mostly noise. Key order is not meaningful, formatting varies, and a single reserialisation makes every line look modified when nothing changed.
Both sides are parsed and compared as data. What comes back is a list of paths that were added, removed or changed, with old and new values — which is the actual answer to 'what is different about this response'.
What people open it for
- Finding the real difference between two API responses
- Checking what a migration changed in a JSON document
- Comparing two config objects without formatting noise
In the terminal
tools jsondiff
Every utility is also a command in the desktop's shell.