# rpk registry compatibility-level set

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: rpk registry compatibility-level set
latest-redpanda-tag: v26.2.1
latest-console-tag: v3.10.0
latest-operator-version: v26.2.2
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "false"
page-eol-date: July 28, 2027
latest-connect-version: 4.105.0
docname: rpk/rpk-registry/rpk-registry-compatibility-level-set
page-component-name: streaming
page-version: "26.2"
page-component-version: "26.2"
page-component-title: Streaming
page-relative-src-path: rpk/rpk-registry/rpk-registry-compatibility-level-set.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/main/modules/reference/pages/rpk/rpk-registry/rpk-registry-compatibility-level-set.adoc
description: Set the global or per-subject compatibility levels. Running this command without a subject sets the global compatibility level.
page-git-created-date: "2023-12-22"
page-git-modified-date: "2026-08-17"
support-status: supported
---

<!-- Source: https://docs.redpanda.com/streaming/current/reference/rpk/rpk-registry/rpk-registry-compatibility-level-set.md -->

Set the global or per-subject compatibility levels.

Running this command without a subject sets the global compatibility level. To set the global level at the same time as per-subject levels, use the `--global` flag.

LEVELS:

-   BACKWARD (`default`): Consumers using the new schema (for example, version 10) can read data from producers using the previous schema (for example, version 9).

-   `BACKWARD_TRANSITIVE`: Consumers using the new schema (for example, version . can read data from producers using all previous schemas (for example, versions 1-9).

-   `FORWARD`: Consumers using the previous schema (for example, version 9) can read data from producers using the new schema (for example, version 10).

-   `FORWARD_TRANSITIVE`: Consumers using any previous schema (for example, versions 1-9) can read data from producers using the new schema (for example, version 10).

-   `FULL`: A new schema and the previous schema (for example, versions 10 and 9) are both backward and forward compatible with each other.

-   `FULL_TRANSITIVE`: Each schema is both backward and forward compatible with all registered schemas.

-   `NONE`: No schema compatibility checks are done.


## [](#usage)Usage

```bash
rpk registry compatibility-level set <subject...> [flags]
```

## [](#flags)Flags

| Value | Type | Description |
| --- | --- | --- |
| --global | bool | Set the global level in addition to subject levels. |
| --level | string | Level to set, see the help text of this command for the full list. |

## [](#global-flags)Global flags

| Value | Type | Description |
| --- | --- | --- |
| --config | string | Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml. |
| -X, --config-opt | stringArray | Override rpk configuration settings; -X help for detail or -X list for terser detail. |
| --ignore-profile | bool | Ignore rpk.yaml and redpanda.yaml; use default settings. |
| --profile | string | rpk profile to use. |
| -v, --verbose | bool | Enable verbose logging. |