WebCodecs Codec Registry

1. Organization

This registry maintains a mapping between codec strings and registration specifications as described below.

2. Registration Entry Requirements

To register an entry, file an issue in the WebCodecs GitHub issue tracker so it can be discussed and evaluated for compliance before being added to the registry.

The Media Working Group might seek expertise from outside the Working Group as part of its evaluation, e.g., from the codec specification editors or relevant standards group. If the codec specification is not publicly available, it must be made available to the Working Group for evaluation. For the entry to be included, there needs to be interest from at least one implementer in the Working Group. If the Working Group reaches consensus to accept the candidate entry, send a pull request (either by editors or by the party requesting the candidate registration) that meets the following requirements:

1. A unique codec string, a common name string, and a link to the codec’s public registration specification.

2. The codec string requirements are as follows:

   1. If the codec string contains a fixed prefix with variable suffix values, the suffix must be represented by an asterisk and the registration’s public specification must describe how to fully qualify the variable portion of the string.

   2. Otherwise, if the codec is recognized by multiple strings, a single preferred string should be listed and the registration’s specification must list the other allowed strings.

   3. Otherwise, the codec is identified by a simple fixed string.

3. Each registration’s specification must include a sequence of sections describing:

   1. Recognized codec strings.

   2. EncodedAudioChunk or EncodedVideoChunk internal data.

   3. AudioDecoderConfig or VideoDecoderConfig description bytes.

   4. Expectations for EncodedAudioChunk or EncodedVideoChunk [[type]].

4. Where applicable, a registration specification may include a section describing extensions to the dictionaries used in the configure(), decode() and encode() methods of the decoder and encoder interfaces (e.g., AudioDecoderConfig, VideoDecoderConfig, AudioEncoderConfig, VideoEncoderConfig, VideoEncoderEncodeOptions).

Once consensus is reached by the Working Group, the registry editors will review and merge the pull request.

Existing entries cannot be deleted or deprecated. They may be changed after being published through the same process as candidate entries. Possible changes include expansion of the codec string to better qualify the codec, adjustments to the codec name string, and modification of the link to the codec’s specification.

3. Audio Codec Registry

4. Video Codec Registry

5. Privacy Considerations

Please refer to the section Privacy Considerations in [WEBCODECS].

6. Security Considerations

Please refer to the section Security Considerations in [WEBCODECS].