Compare Two JSON Values

No. Both values are compared entirely on your device, and nothing is sent to a server - there’s no upload step at all. Turn off your Wi-Fi after the page loads and it still works. This page loads 4KB of JavaScript, gzipped - about what your browser’s network tab will show for this page’s own scripts.

No, and this is the main reason to use a JSON-aware diff instead of a plain text diff on the same content: two objects with identical keys and values in a different order compare as identical here. A plain-text diff (this site’s own `text-diff` tool) would report every line as changed just because the keys moved - genuinely useful for comparing source code or prose, genuinely misleading for comparing two JSON documents that happen to serialize their keys in a different order.

An element inserted or removed anywhere in an array - not just at the end - is recognized as exactly that one insertion or removal, with every other element still reported unchanged. The one honest limitation: if an inserted or removed element sits next to OTHER elements that were independently modified around the same time, this tool may pair a modified element with the wrong neighbor instead of catching the insertion cleanly - rare in practice, and the same tradeoff this site’s own CSV-compare tool already accepts and discloses for the equivalent case.

You’ll see a specific message naming which side (left or right, or both) failed to parse and why, rather than a blank result or a generic error - fix the JSON in that box and the comparison picks back up automatically.

The comparison stops recursing past 500 levels of nesting - far beyond any realistic document (a typical API response or config file is well under 20 levels deep) - as a safety limit against freezing or crashing the tab on a pathologically deep input. Past that depth, the affected part is conservatively reported as “changed” even if it’s actually identical, rather than risk a crash trying to check - an honest tradeoff for a case this unlikely to matter in practice.

When two elements at the same array position share enough content to look like the same thing modified (not two unrelated values), this tool recursively diffs them and shows exactly which nested key changed - not just a blanket “this element is different.” Two genuinely unrelated values landing at the same position are shown as one removed and one added, not forced into a misleading nested comparison.

This tool is paste-and-see by design (see the FAQ on this site’s own `json-minify-beautify` tool for the same reasoning) - open each file in a text editor, copy its contents, and paste. A file-upload step would add friction for the common case (comparing two API responses, two config snippets) without adding real capability, since the comparison itself only ever needs the text either way.