Original

Changed

  • 100% Free
  • No Sign-Up
  • No Credit Card
  • No Free Trial
  • No Pro Tier
  • No Watermarks

Nothing is uploaded. Just open it and start.

See what actually changed between two JSON documents

Free, no sign-up. Paste two versions of a config file, an API response or a data export, and get a clear list of what was added, removed and changed — ignoring key order and formatting, with arrays of records matched by id. Export the difference as a JSON Patch. Everything runs in your browser.

Structural, not line-based

Every added, removed and changed value, listed by its path.

Order doesn't matter

Key order and formatting are ignored; arrays can be matched by id.

Side by side

Keys sorted and records lined up by id; click a change to jump to it.

Patches, apply and merge

JSON Patch or Merge Patch out, apply a patch in, or merge with a common base.

Exact numbers

64-bit ids and huge numbers are compared digit for digit.

Private

Runs in your browser. Nothing you paste is uploaded.

Frequently asked questions

How is this different from a normal text diff?
A text diff compares lines, so reordered keys, different indentation or a reformatted file show up as changes even when the data is identical. JSON Diff parses both documents and compares the data itself: it reports each key or value that was added, removed or changed, with its path (like users[2].email), and ignores key order, whitespace and how numbers are written (1 and 1.0 are the same).
How are arrays compared?
By default, items that are objects with an id (id, _id, uuid, key, slug, code or name — or a key you choose in Options) are matched by that id wherever they sit, so a reordered list of records only reports real edits, shown as paths like owners[id=17].role. Arrays without such a key are compared by position, and "How arrays were matched" says which way each list went and why (for example, ids that repeat). You can switch to strictly by position, or to Ignore order, which only reports items found in one list but not the other.
Can I ignore fields like timestamps?
Yes. In Options, list what to ignore, separated by commas: a key name such as updatedAt is skipped wherever it appears, and a path such as items[*].meta.updatedAt or $.a.b only there. You can also set a number tolerance, and compare text ignoring case or extra spaces.
What is the Patch tab?
The difference as a JSON Patch (RFC 6902) — operations that turn the original into the changed document — or as a Merge Patch (RFC 7386). "Minimal" moves and edits records that have ids instead of replacing everything by position, so a reordered list stays small; "Strict" compares by position. A JSON Patch reproduces the changed document exactly, ignoring none of your options; a Merge Patch can't set a value to null (null means delete), and the tool warns you when that matters. The Apply patch tab does the reverse: paste a patch and see the result, or the exact step that fails, and Merge combines both documents with a common ancestor and lists conflicts.
Does it handle big numbers correctly?
Yes. Standard JavaScript rounds integers above 2^53, so a 64-bit id such as 9007199254740993 would silently become 9007199254740992 and two different ids could look the same. JSON Diff keeps every number exactly as written and compares it digit for digit — long decimals too, so 0.1000000000000000001 is not the same as 0.1.
Is my JSON uploaded?
No. Parsing and comparing happen entirely in your browser, in the background so even huge or deeply nested files don't freeze the page; nothing is sent anywhere. Both documents and your options are remembered in this browser only — press Clear to remove them. Share makes a link that carries both documents in the link itself.

Spotted a bug or have a suggestion?

Found something broken, have an idea, or just want to say thanks about any of our tools? Every message reaches a real person.