JSON Diff

Paste one JSON document into the Left box and the other into the Right box, and the tool lists exactly what changed between them. You get a running count of added, removed and changed entries, and each difference is shown with a readable path so you can find it in the source. Both sides are parsed in your browser as you type.

It is a structural diff. It parses both sides into real JSON and compares them semantically: objects key by key, arrays index by index, and everything else by value. That means reordered whitespace, indentation, or trailing commas in your formatting never show up as fake changes, which is the big advantage over a plain text diff.

Every difference is tagged with a path built from the keys and indexes that lead to it, like user.roles[0] or config.limits[2]. Keys that are not simple identifiers get bracket-quoted so the path stays unambiguous. Added and removed entries show the value, and changed entries show the old value and the new value side by side.

Arrays are compared strictly by position, index by index, not as unordered sets. So if you move an item from the start of a list to the end, the diff reports every position that shifted as changed rather than recognizing it as the same element moved. That is the honest tradeoff of an index-based structural compare. For plain text comparison instead, try the diff-checker tool.

No. Both documents are parsed and compared entirely in your browser, and nothing is sent to a server. The catch with any diff is that you need both versions to begin with, and the older one has often already vanished, which is exactly the copy history Relic is built to keep.