JSON Diff — Compare JSON Objects

Comparing two JSON payloads by eye is misery: keys arrive in different orders, one side is minified, and the actual change is a single nested value somewhere in the middle. Paste both JSON documents above and this diff shows you precisely what changed — with Sort keys on by default, so pure key-order differences and formatting noise disappear and only real value changes remain.

Because both sides are parsed as JSON first, you get a *semantic* comparison: arrays stay order-sensitive (reordering an array is a real change), nested objects are sorted recursively, and invalid JSON on either side is called out with the exact line and column instead of silently diffing garbage. Changed lines get word-level highlighting, so a one-token edit inside a long line is impossible to miss.

Typical uses: diffing API responses before and after a deploy, checking what a config management tool actually changed in a manifest, or verifying that two environments run the same settings.

FAQ

Does key order matter in a JSON diff?

Not here. With Sort keys enabled, object keys are sorted recursively before comparing, so {"a":1,"b":2} and {"b":2,"a":1} compare as identical — which matches JSON semantics, where object key order carries no meaning. Array order is still respected, because there it does.

What if one side isn't valid JSON?

You get a clear error naming which side failed — Original or Changed — with the line and column of the syntax problem, so you fix the payload instead of diffing broken input.

Is my JSON sent to a server?

No. In the browser UI the comparison runs locally on your machine; pasted payloads are never uploaded.