Skip to content

Revise codec registration entry requirements #921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
marcoscaceres wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Revise codec registration entry requirements #921

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fdf79eb
Revise codec registration entry requirements
marcoscaceres Jan 15, 2026
a882e6e
Apply suggestion from @Copilot
marcoscaceres Jan 15, 2026
de23050
Apply suggestion from @marcoscaceres
marcoscaceres Jan 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
75 changes: 42 additions & 33 deletions codec_registry.src.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,23 @@
Registration Entry Requirements {#registration-entry-requirements}
==================================================================

1. Each entry must include a unique <a>codec string</a>, a common name string, and a
link to the codec's specification.
2. The <a>codec string</a> must be crafted as follows:
To register an entry, file an issue in the
[WebCodecs GitHub issue tracker](https://github.com/w3c/webcodecs/issues/)
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 <a>codec string</a>, a common name string, and a
link to the codec's public <dfn>registration specification</dfn>.
2. The <a>codec string</a> requirements are as follows:
1. If the <a>codec string</a> 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
Expand All @@ -58,41 +72,34 @@
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
1. Recognized codec strings.
2. {{EncodedAudioChunk}} or {{EncodedVideoChunk}} internal data.
3. {{AudioDecoderConfig}} or {{VideoDecoderConfig}} description bytes.
4. Expectations for {{EncodedAudioChunk}} or {{EncodedVideoChunk}}
{{EncodedVideoChunk/[[type]]}}
{{EncodedVideoChunk/[[type]]}}.
4. Where applicable, a registration specification may include a section
describing extensions to {{VideoEncoderConfig}} or {{AudioEncoderConfig}}
dictionaries.
5. Candidate entries must be announced by filing an issue in the
[WebCodecs GitHub issue tracker](https://github.com/w3c/webcodecs/issues/)
so they can be discussed and evaluated for compliance before being added to
the registry. The Media Working Group may 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. If the Working Group reaches consensus to accept the candidate,
a pull request should be drafted (either by editors or by the party
requesting the candidate registration) to register the candidate.
The registry editors will review and merge the pull request.
6. 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 <a>codec string</a> to better qualify the codec,
adjustments to the codec name string, and modification of the link to the
codec's specification.

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 <a>codec string</a> to better qualify the codec,
adjustments to the codec name string, and modification of the link to the
codec's specification.

Audio Codec Registry {#audio-codec-registry}
============================================

<table class='data'>
<tr>
<td>**codec string**</td>
<td>**common name**</td>
<td>**public specification**</td>
</tr>
<thead>
<tr>
<th>Codec string</th>
<th>Common name</th>
<th>Registration specification</th>
</tr>
</thead>
<tr>
<td>flac</td>
<td>Flac</td>
Expand Down Expand Up @@ -153,11 +160,13 @@
============================================

<table class='data'>
<tr>
<td>**codec string**</td>
<td>**common name**</td>
<td>**specification**</td>
</tr>
<thead>
<tr>
<th>Codec string</th>
<th>Common name</th>
<th>Registration specification</th>
</tr>
</thead>
<tr>
<td>av01.\*</td>
<td>AV1</td>
Expand Down