Skip to content
Sealpaste

Delete all recent work?

This removes the 0 items saved in this browser. Your settings stay.

Stop saving recent work?

New work won't be saved in this browser. The 0 items already saved can stay or go.

Compare Two JSON Documents

Original JSON

Paste the original JSON, or

Changed JSON

Paste the changed JSON, or

Differences
Ready
Runs in your browser. Nothing you paste is uploaded unless you share it.

Compare two JSON documents by meaning, not text: key order is ignored and each difference is listed with its path, like $.limits.rps

See what really changed between two JSON documents. Key order and formatting are ignored; each difference comes with its exact path.

How to use it

  1. Paste the original JSON on the left and the changed JSON on the right (or open files).
  2. Tick "Ignore array order" if [1, 2] and [2, 1] should count as equal.
  3. Read the result side by side (inline on a phone), or switch to Table for each difference with its path.

Examples

Reordered keys are not a change

Input
Left:  {"a": 1, "b": 2}
Right: {"b": 2, "a": 1.0}
Result
No differences

Key order and number formatting (1 vs 1.0) do not matter in JSON.

Changes with paths

Input
Left:  {"limits": {"rps": 100}, "owners": ["ana"]}
Right: {"limits": {"rps": 250}, "owners": ["ana", "li"]}
Result
changed  $.limits.rps   100 → 250
added    $.owners[1]    "li"

Why a text diff is the wrong tool for JSON

Two API responses can be identical in meaning and still look completely different: keys come back in another order, a serializer writes 1.0 instead of 1, indentation changes. A line-by-line diff flags all of that as changes and hides the one field that actually moved.

This compare parses both sides and walks the trees. Objects are matched by key, numbers by value, and the result is a short list you can act on: the path, the old value and the new value. A value that changes kind, such as 1 to "1", shows as Type changed in the table.

Reading the paths

Paths use JSONPath notation, the same you would use in jq, Postman tests or JSONPath libraries:

PathMeans
$The whole document
$.user.emailKey "email" inside key "user"
$.items[2]Third item of the "items" array
$["first name"]A key with a space or special character

Questions

Does it ignore the order of keys?
Yes. JSON objects are unordered, so {"a":1,"b":2} equals {"b":2,"a":1}.
Can I see the two documents side by side?
Yes, that is the default view. Both sides are shown with keys sorted A–Z, so only real changes are highlighted. Switch to Inline for one column, or to Table for a list of paths with old and new values.
Can it ignore the order of array items?
Yes, tick "Ignore array order". Without it, items are compared by position, so [1, 2] and [2, 1] differ. With it, items are matched by value, so [1, 2, 3] equals [3, 1, 2], and only items without a match are reported as added or removed.
Is 1 the same as 1.0?
Yes. Numbers are compared by value, so 1, 1.0 and 1e0 are equal. Very large integers are compared digit by digit, so no precision is lost.
What if one side isn’t valid JSON?
Nothing is compared. The page names the side, the line, the column and the reason, so you can fix it first.
Is my JSON uploaded?
No. Everything runs in your browser, so your JSON stays on your device. Nothing you paste is uploaded unless you share a result, which is locked with your password first. We don’t save or log what you paste.

Related tools