# 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-operator-version: v26.1.4
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "true"
page-eol-date: April 30, 2025
latest-console-tag: v3.7.3
latest-connect-version: 4.93.0
docname: rpk/rpk-registry/rpk-registry-compatibility-level-set
page-component-name: streaming
page-version: "24.1"
page-component-version: "24.1"
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/v/24.1/modules/reference/pages/rpk/rpk-registry/rpk-registry-compatibility-level-set.adoc
page-git-created-date: "2023-12-22"
page-git-modified-date: "2024-07-24"
support-status: past end-of-life
---

<!-- Source: https://docs.redpanda.com/streaming/24.1/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.

## [](#concept)Concept

### [](#levels)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 10) 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 | - | Set the global level in addition to subject levels. |
| -h, --help | - | Help for set. |
| --level | string | Level to set, one of NONE, BACKWARD,BACKWARD_TRANSITIVE, FORWARD,FORWARD_TRANSITIVE, FULL, FULL_TRANSITIVE. |
| --config | string | Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD, and /etc/redpanda/redpanda.yaml. |
| -X, --config-opt | stringArray | Override rpk configuration settings. See rpk -X or execute rpk -X help for inline detail or rpk -X list for terser detail. |
| --format | string | Output format: json,yaml,text,wide,help. Default: text. |
| --profile | string | Profile to use. See rpk profile for more details. |
| -v, --verbose | - | Enable verbose logging. |