🔍 JSON Diff Checker

SON diff compares two JSON documents and reports what’s different between them. A good JSON diff tool does this semantically — meaning it parses the data first and ignores differences that don’t actually change the meaning, like key order or whitespace, so you’re only shown real additions, removals, and value changes.

A plain text diff will flag two JSON files as “different” even when the underlying data is identical, just because a key moved position or the formatting changed. A JSON diff checker parses the structure first so you can quickly spot real changes—a new field in an API response, a value that changed, or a key that got removed—without wading through false positives.

Yes. The comparison runs entirely in your browser, so there’s no server-side file size limit — performance depends on your device and browser rather than a fixed cap. Very large files (tens of MB) may take a moment to render, but the diff itself works the same way regardless of size.

Yes. The tool walks the full structure recursively—objects inside objects, arrays of objects, arrays inside arrays—so a change 10 levels deep is caught and reported with its exact path (e.g. $.data.users[2].address.zip), not just flagged as “something changed” at the top level.

This usually happens with tools that do a plain text diff instead of a semantic one—they treat {"a":1,"b":2} them {"b":2,"a":1} as different because the characters are in a different order, even though the data is identical. This tool parses your JSON first and compares the actual values, so reordered keys never show up as a change.

Yes. You can paste minified or unformatted JSON directly — it’s parsed before comparison, so line breaks and indentation don’t matter either way.

The tool tells you which side is invalid and shows the parser’s error message (for example, a missing comma or unclosed brace) so you can fix the syntax before comparing.

Yes—turn on “Ignore array order.” Two arrays containing the same items in a different sequence will then be treated as equal instead of flagging every shifted index as a change.

If your arrays contain objects with a shared identifier field — id, _id, uuid, key, or slug — the tool automatically matches items by that field instead of by position. This means an item that moved from index 2 to index 5 is still correctly compared to itself, instead of being compared against whatever object happens to sit at index 2 now.

“Ignore array order” is a general-purpose alignment for any array (numbers, strings, or objects) using sequence matching. ” Match arrays by ID” is more precise for arrays of objects—it uses an actual identity field rather than guessing based on similarity, so it’s more reliable when items have changed internally as well as moved

Yes. Enter the field names, comma-separated, in the “Ignore keys” box (for example, – updatedAt, _id, __v) and they’ll be skipped at every level of the JSON, not just the top level.

No. The comparison logic runs entirely in your browser’s JavaScript engine — nothing is sent to a server. You can verify this yourself by opening your browser’s developer tools, switching to the Network tab, and running a comparison; no request will appear.

Yes, within the limits of your browser’s memory and performance, since the whole comparison happens client-side. Very large files (tens of MB) may be slower to render, but there’s no server-side size cap.

Click “Copy Compare Link” after entering both JSON documents. It generates a URL with both documents encoded into it—anyone who opens that link sees the exact same comparison loaded automatically, without needing to re-paste anything.