> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alginte.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Schema Registry

> Register Avro, JSON Schema, and Protobuf schemas; evolve them across versions; manage compatibility per subject.

The **Schema Registry** page lists every subject with its type, latest
version, and effective compatibility/mode — showing whether a value is set on
the subject itself or inherited from the global default.

## Registering a schema

**Create Schema** opens as a resizable drawer (or arrives pre-filled from a
topic's [Schema tab](/guides/topics#the-topic-detail-page)):

1. Pick the **Schema Type** — AVRO, JSON, or PROTOBUF — and whether it's for
   the **key** or the **value**.
2. Pick a **Naming Strategy** — *TopicNameStrategy*, *RecordNameStrategy*, or
   *TopicRecordNameStrategy* — and fill in the topic and/or record name it
   asks for. The read-only **Subject** preview updates to exactly what will
   be registered, so there's never a surprise about the subject name.
3. Write the schema in the editor (seeded with a minimal template for the
   chosen type).
4. **Submit** — a *View Schema?* shortcut takes you to the new subject.

## The schema detail page

Per subject you get:

* An **info card** — type, versions, and the subject's compatibility and
  mode, with the same inherited-vs-explicit distinction as the list.
* The **schema editor** — read the current version, or **Edit** and submit:
  a successful submit registers the next version (subject to the
  compatibility rules).
* A **Compare versions** switch (appears once the subject has two or more
  versions) — a side-by-side diff of any two versions, the fastest way to
  answer "what changed between v3 and v7?".
* A **Subject Actions** menu — set or clear the subject's own
  **compatibility level** and **mode** (overriding the global default),
  delete a single version, or delete the subject.

<Note>
  Compatibility is what makes evolution safe: with a compatibility level set,
  the registry rejects a new version that would break existing consumers —
  the submit fails with the reason. Prefer fixing the schema over loosening
  the level.
</Note>