JSON Compare

// HOW TO USE

1. 01Paste two JSON documents — Original on the left, Modified on the right.
2. 02Click Compare. Each differing path is shown with its kind: added (green), removed (red), modified (yellow), unchanged (grey).
3. 03Copy Diff exports a flat patch-style summary you can paste into a PR description or test failure note.

// WHEN TO USE

Use this when you need to verify that an API response matches a known-good baseline, or to audit what changed between two versions of a payload. It's faster than eyeballing minified JSON and more precise than a plain text diff — results are path-level, so a renamed key is 'removed + added' rather than a line-level noise change. Reach for it in contract testing, regression runs, and side-by-side environment checks (staging vs production).

// WHAT BUGS THIS FINDS

• Unintended field removal

  A refactor silently drops a field the client depends on — Compare flags the path as 'removed' immediately rather than waiting for a downstream test to fail.

• Type change without a version bump

  A numeric ID changes from integer to string; text diff may not catch it but JSON Compare shows kind: modified with the before/after types.

• New undocumented fields

  A backend adds fields not present in the contract — surfaces as 'added' paths that the consumer may mishandle or inadvertently rely on.

• Structural drift across environments

  Staging and production responses differ because a feature flag or config value affects serialization — Compare makes the exact paths visible.

// QA USE CASES