JSON Diff.

Compare JSON online - free and private

A JSON diff tool helps you compare two JSON files, API responses, config snapshots, or data exports without noisy formatting changes. Paste both documents above and the JSON compare tool reports real structural differences: added fields, removed fields, and changed values.

How to compare two JSON files in three steps

1. Paste the original JSON into the left editor.
2. Paste the JSON to compare on the right — and enable ignore-array-order if your arrays are really unordered sets.
3. Review and export the added, removed, and changed values by path.

Semantic JSON diff, not line-by-line noise

Unlike a normal text diff, this tool parses the JSON first. That means minified JSON, pretty-printed JSON, and reordered object keys compare correctly. The result is path-based, so you see changes like users[2].email instead of hunting through line numbers.

The difference is easy to see. These two documents are identical data:

{ "name": "Ada", "role": "admin", "active": true }

{
  "active": true,
  "role": "admin",
  "name": "Ada"
}

A line-based diff (git, VS Code, most “compare” sites) reports every line as changed. A structural diff reports no differences, because none exist. That is the whole point — you want to see the one field that actually changed, not 40 lines of reformatting.

When array order matters — and when it does not

By default arrays are compared by position, because in JSON [1, 2] genuinely is not [2, 1] — order is part of the data for things like ranked results or ordered steps. But plenty of arrays are really sets: tags, scopes, permissions, role IDs, feature flags. For those, a reordered list is not a change, and position-based comparison floods you with false diffs.

Turn on ignore-array-order for those cases and the comparison matches items by value instead of index. Most diff tools do not offer the choice and quietly pick one behaviour for you.

What developers use a JSON diff for

Reviewing API changes. Capture a response before and after a deploy and see precisely which fields moved, disappeared, or changed type — the kind of break that slips past a test suite.

Config drift. Compare a staging config against production to find the one flag that explains why they behave differently.

Debugging webhook payloads. Diff a payload that worked against one that failed, and the culprit usually falls straight out.

Test fixtures. When a snapshot test fails, a structural diff tells you whether the data actually changed or just got reserialised.

Why use this JSON compare tool?

It is fast, private, and built for nested JSON, with no file-size cap. That privacy matters more here than on most tools: the JSON you compare is usually a real API response or a production config, and several popular online diff tools default to saving your comparison behind a public share link. Nothing you paste here leaves your browser.

Need to clean the input first? Try JSON repair for broken JSON, JSON formatter to pretty-print, JSON validator to check syntax, or sort JSON keys to normalise both sides before a line-based comparison elsewhere. Reading the result is easier in the JSON viewer. See also our guide on how to compare JSON files.

A structural diff is also the honest way to check a merge. If you combine multiple JSON files into one, diffing the result against the original tells you whether the merge kept what you expected — a shallow merge that quietly dropped a nested block looks fine in the output and obvious in the diff.