JSON Compare

Spotting real differences between two JSON documents

Comparing two JSON files with a normal text diff is frustrating. If the keys are in a different order or the indentation differs, almost every line is flagged even though the data is identical. This tool compares the data itself, so it ignores formatting and key order and shows only the values that genuinely changed. It is useful for checking API responses before and after a change, comparing configuration across environments, or reviewing what an update did to a record.

Each difference is listed with its exact path, such as user.address.city or items[3].price, along with the old and new values. Added and removed keys are shown separately from changed values, so you can quickly tell whether a field disappeared or simply has a different value. That path-based view makes it easy to jump to the right place in large documents.

Arrays need a little thought. They are compared position by position, because order matters in most JSON arrays. If one list has an extra item inserted near the start, every following item may be reported as changed, even though only one thing was added. In that case, sorting both arrays the same way before comparing gives a clearer result. Watch for type differences too: the number 10 and the string '10' look similar but are reported as different, which often explains bugs between services. Paste both documents, review the list, and copy the paths you need. Everything runs locally, so production responses and private records never leave your device. It is also a quick way to confirm that a refactor really left the output unchanged.