Any time you have two versions of a JSON structure and need to know exactly what changed, a JSON diff tool is faster and more reliable than reading both documents manually.
Common scenarios
API response debugging — Compare what an endpoint returned before and after a deploy to spot unintended changes.
Configuration drift — Check whether a config file has drifted from the expected baseline (e.g. Terraform state, feature flags).
Data migration validation — After migrating records, compare a sample from the source and destination to confirm fidelity.
Code review — Include a JSON diff in a PR when changing API contracts or database schemas to make the impact immediately visible.
Test assertions — When a snapshot test fails, paste old and new payloads here to understand what changed.
Reading the diff output
+ green lines — Fields that exist in JSON B but not in JSON A (added).
– red lines — Fields that exist in JSON A but not in JSON B (removed).
A field that changed value appears as both a red removal and a green addition at the same path.
Paths use dot notation for object keys (user.address.city) and bracket notation for arrays (items[0].price).