# AV1 — Containers and HDR

Canonical URL: https://encode.wiki/codecs/video/av1/#containers-and-hdr
Document ID: docs/codecs/video/av1
Section ID: containers-and-hdr
Content version: ca42e61ede0a24f789d7287a0001244ad22f4abf
Status: current
License: CC BY-SA 4.0
Checksum (SHA-256): 6f231318004addabe10196672c93efde558977dbc7ac6254ee4b44ee173d5249

## Containers and HDR

**AV1 container mappings**

| Relationship | Project or format | Evidence and scope | Status |
| --- | --- | --- | --- |
| Carried By | [ISO Base Media File Format](/containers/isobmff/) | Uses the av01 sample entry and av1C configuration box. Scope: Container Mapping. Sources: [AV1 Codec ISO Media File Format Binding](https://aomediacodec.github.io/av1-isobmff/). | Normative |
| Carried By | [Matroska](/containers/matroska/) | Uses the V_AV1 Codec ID and an AV1CodecConfigurationRecord in CodecPrivate. Scope: Container Mapping. Sources: [Matroska codec mappings](https://www.matroska.org/technical/codec_specs.html). | Normative |
| Carried By | [WebM](/containers/webm/) | AV1-in-WebM is implemented in common tools, but the current public WebM codec list does not document it. Scope: Container Mapping. Sources: [WebM container guidelines](https://www.webmproject.org/docs/container/), [Matroska codec mappings](https://www.matroska.org/technical/codec_specs.html). | Common Implementation |

[Open the complete typed relationship catalog](/api/v1/catalog.json).

- **MP4/ISOBMFF:** `av01` sample entry with an `av1C` configuration box, per AOMedia's [ISOBMFF binding](https://aomediacodec.github.io/av1-isobmff/).
- **Matroska:** codec ID `V_AV1`. **WebM:** AV1 in WebM is widely supported by browsers and muxers, although the WebM container guidelines still only list VP8 and VP9.
- **IVF and raw OBU** (`.obu`) files are what standalone encoders write; remux them into MP4 or MKV for playback.

AV1 signals colour with the standard CICP values (primaries, transfer, matrix, range) in the sequence header and carries HDR10 mastering-display and content-light metadata in metadata OBUs. HDR10+ uses ITU-T T.35 metadata OBUs ([AOMedia spec](https://aomediacodec.github.io/av1-hdr10plus/)), and Dolby Vision has an AV1-based profile (profile 10). HLG needs only the transfer characteristic.

**AV1 HDR signalling**

| Relationship | Project or format | Evidence and scope | Status |
| --- | --- | --- | --- |
| Signals | [HDR10](/hdr/) | AV1 carries CICP color signaling plus mastering-display and content-light metadata. Scope: Bitstream. Sources: [AV1 Bitstream & Decoding Process Specification](https://aomediacodec.github.io/av1-spec/av1-spec.pdf). | Normative |
| Signals | [HDR10+](/hdr/) | HDR10+ metadata is carried in an AV1 ITU-T T.35 Metadata OBU. Scope: Bitstream. Sources: [HDR10+ Metadata Handling Specification for AV1](https://aomediacodec.github.io/av1-hdr10plus/). | Normative |
| Signals | [Hybrid Log-Gamma](/hdr/) | HLG can be identified through CICP transfer characteristic 18; application support is separate. Scope: Bitstream. Sources: [AV1 Bitstream & Decoding Process Specification](https://aomediacodec.github.io/av1-spec/av1-spec.pdf). | Normative |

[Open the complete typed relationship catalog](/api/v1/catalog.json).