About this utility
How to use JSON Schema Compatibility Diff
Compare JSON Schemas for type changes, newly required or removed properties, narrowed enums, and tightened numeric ranges.
What to provide
Paste the schema currently accepted by existing producers or consumers.
Paste the proposed schema. The report assumes existing instances should remain valid.
- Paste, type, or drag and drop a supported text file into the input area.
- Place the second value or file in the adjacent panel. Sensitive fields are masked by default.
- Review the input and the clearly labeled output behavior.
- Select “Run tool” or press Ctrl/Command + Enter, then copy, download, or move the result back into the first input for another pass.
Use “Swap inputs” to reverse the comparison without copying either value.
What the result means
A compatibility table with JSON paths and precise constraint changes.
Privacy and safety
This utility is loaded as browser code and processes your input only in this tab. OmniCastConverter has no upload endpoint and never stores your content, filenames, tokens, or secrets. Generated markup and code are shown as inert text and are never executed.
Limitations
- Everything is processed in this browser tab. Input, filenames, keys, and output are never uploaded or saved. $ref graphs, unevaluated keywords, vocabularies, annotations, and producer-versus-consumer variance can require a fuller compatibility policy.
Try the included example
Select “Load example” at any time to restore this tested sample.
{"type":"object","properties":{"name":{"type":"string"},"age":{"type":"number"}}}{"type":"object","required":["name"],"properties":{"name":{"type":"string"},"age":{"type":"integer"}}}