JSON Diff Tool

Paste JSON A and JSON B to see added, removed, and changed keys after both documents parse successfully.

Result

Ready.

Spot config and API drift quickly

Staging and production configs should differ only on purpose. A diff of exported settings JSON catches accidental feature flags or missing nested objects before a deploy window closes.

Contract testing companion

Save a golden response from v1 and compare v2 beta payloads during migration. Focus on renamed fields and null versus missing key semantics—both break clients that use strict optional chaining.

Limits of structural diff

Large arrays of log lines may produce noisy output. For repetitive collections, consider sorting by a stable id in both documents first, or diff a normalized subset.

FAQ

Does key order matter?
Objects are compared by key name, not insertion order. Arrays are compared positionally—reordered array elements register as changes at each index.
Are type changes detected?
Yes. A field switching from string "42" to number 42 appears as a value change with type implications for strict schema validators.
Can I diff minified and pretty JSON?
Whitespace differences are ignored after parse. Ensure both inputs are valid JSON; trailing commas or comments will fail parsing before diffing begins.