Complete guide to comparing JSON and detecting changes
JSON Diff (JSON Difference/Comparison) is a technique to compare two JSON documents and identify differences. Unlike simple text comparison, JSON Diff understands JSON structure and semantics, detecting meaningful changes like field additions, removals, type changes, and value modifications. Our tool automatically categorizes changes by impact level (Breaking/Risky/Safe) to help you quickly assess API compatibility.
Copy the original JSON response from your API or file. Ensure it's valid JSON format. You can use our built-in JSON validator to check.
Paste the old JSON in the left panel and the new JSON in the right panel. Our tool supports formatted, minified, or raw JSON input.
Click the "Compare" button. Our engine will automatically analyze both JSON documents, infer schemas, and detect all differences.
Review the categorized results: Breaking Changes (red), Risky Changes (yellow), and Safe Changes (green). Download the report or share with your team.
Breaking Changes: Field removals, incompatible type changes (e.g., string→number), required field becoming nullable. These changes will likely break existing clients and require immediate attention.
Risky Changes: Nullability changes (non-null→nullable or vice versa), array structure changes, enum value changes. These changes might break some clients depending on their implementation.
Safe Changes: New field additions, new enum values, description changes. These changes are generally backward compatible and safe to deploy.
Compare v1 and v2 API responses to create migration guides and identify breaking changes for clients.
Integrate JSON Diff into your pipeline to automatically detect breaking changes before deployment.
Verify that backend changes maintain contract compatibility with frontend applications.
Generate clear diff reports to help reviewers understand API changes in pull requests.