Is my JSON uploaded to a server?

No. Both documents are parsed and compared entirely in your browser with JavaScript. Nothing is sent over the network, which makes the tool safe for sensitive data.

Why are two differently ordered JSON files reported as identical?

By default the comparison is semantic: both sides are normalized (same indentation, keys sorted recursively) before diffing, so formatting and key order don't count as changes. Turn off the sort option to compare keys in their original order.

JSON Diff — Compare Two JSON Files Online

Compare two JSON documents and see the differences as a unified diff. Key order and indentation are ignored. Free, private, right in your browser.

Instant Private Zero cookies

Original

Modified

Differences

Why diff JSON semantically?

A plain text diff of two JSON files drowns real changes in formatting noise: reordered keys, different indentation, trailing commas moved around. This tool normalizes both documents first — consistent indentation, recursively sorted keys — so the diff shows what actually changed: values, added fields, removed entries.

How it works

Both sides are parsed locally (an invalid document is reported with its side and position), re-serialized in a canonical form, then compared line by line with the same algorithm used by version control tools. The result is a unified diff — - for removals, + for additions, with three lines of context — ready to paste into a ticket or a code review.

Frequently asked questions

Is my JSON uploaded to a server?: No. Both documents are parsed and compared entirely in your browser with JavaScript. Nothing is sent over the network, which makes the tool safe for sensitive data.
Why are two differently ordered JSON files reported as identical?: By default the comparison is semantic: both sides are normalized (same indentation, keys sorted recursively) before diffing, so formatting and key order don't count as changes. Turn off the sort option to compare keys in their original order.