Avro Schema Evolution Checker
Diff two Apache Avro record schemas for added, removed, and changed fields with reader-writer compatibility hints in the browser.
Compare Avro writer and reader schemas for safe evolution
Event pipelines evolve: producers emit older record layouts while consumers upgrade to newer fields. Avro compatibility depends on field additions, removals, type changes, and whether new fields ship with defaults. Paste a writer (older producer) schema and a reader (newer consumer) schema to see a field-level diff and a quick compatibility hint.
How to read the diff
- added_with_default, new reader fields that older writers omit are usually safe when a default is present.
- added_without_default, likely breaking unless every writer already emits the field.
- type_changed, review Avro promotion rules for your library version.
- removed_in_reader, reader no longer expects a writer field (often OK when reading forward-compatible payloads).
Validate individual schemas with Avro Schema Validator and format JSON with Avro Formatter.
Frequently Asked Questions
Do both sides need to be records?
Yes. This diff focuses on top-level record schemas with fields arrays, which is the common Kafka/Confluent use case.
Is backward/forward compatibility guaranteed?
No. The tool highlights likely issues; always run your serializer tests and schema registry checks before deploying.
Where is data processed?
Entirely in your browser. Schemas are not transmitted to a server.