JSON Formatter
Format, minify and validate JSON for easier reading.
DeveloperProcessed locally
OpenAPI Compatibility Checker
Compare two OpenAPI 3.x specifications locally and review potentially breaking API contract changes by operation and field path.
Processed on this page. No uploads. Your input is not saved.
Compare two OpenAPI files before release. The specifications stay in this browser.
Paste JSON or YAML below, or choose a file.
Paste JSON or YAML below, or choose a file.
Each file: up to 2 MB and 1,000 operations. Supports OpenAPI 3.0, 3.1 and 3.2.
Compatibility findings
A clean result only means no risks were found by the checks listed here. This does not validate the full specification or test a running API.
What changes are checked?
The checker compares operations, parameters, request bodies, response codes and media types, plus common schema changes such as removed properties, newly required request properties, type changes and enum values. Findings include the affected operation and field path.
How are references handled?
References within a specification file are followed. External file or URL references are not fetched and appear as review findings. Recursive schemas are compared at their first occurrence and marked for review.
What is outside this check?
The result is a static contract review, not a complete OpenAPI conformance validator, runtime API test or security audit. Server behavior, authorization logic and complex schema composition can require manual review. The report says which references or recursive structures were not fully checked.
Review OpenAPI changes before releasing an API
Paste or choose the original and revised OpenAPI 3.0, 3.1 or 3.2 files. Check the severity and affected field path, then download a Markdown or JSON report for review.
Example and expected result
If the revised GET /users/{id} response makes an optional `email` field required, the report flags the changed response contract. Local `$ref` references are followed; external references and complex schema composition are called out for manual review. This is not a full specification validator or a test of the running API.