Report

Help us improve this tool

JSON Schema Compatibility Diff

Compare two JSON Schemas for breaking changes in required fields, properties, and enums.

O M T

Compare JSON Schema versions

API teams evolve schemas by adding fields, tightening enums, or promoting properties to required. Paste an older baseline schema and a newer candidate to highlight likely breaking changes before you ship a contract bump.

Validate individual schemas with the JSON Schema Validator and generate fixtures using JSON Schema Faker.

Frequently Asked Questions

What counts as breaking?

Removed properties, type changes, enum values that disappear, and newly required fields are flagged as breaking because payloads that satisfied the older schema may fail validation against the newer one.

Are $ref pointers resolved?

This diff compares the schema JSON you paste. External references are not fetched; inline subschemas and nested properties blocks are compared recursively.