Immersive Audio Model and Formats (IAMF) decoding support

at a glance

reference routes

why it exists

Before native IAMF support, sites wanting immersive audio had two main options, per the feature explainer:

• License proprietary spatial formats — which can impose royalty costs on hardware manufacturers and fragment the ecosystem.
• Build complex Web Audio node graphs in application JavaScript to simulate immersiveness — significant development effort, and the result does not travel as a single standard bitstream.

IAMF is the Alliance for Open Media's answer: an open, royalty-free container-and-model standard for channel-based, scene-based (Ambisonics), and object-based audio, with a reference implementation (iamf-tools) that Chrome embeds. Native decoding lets the browser render one standard bitstream to arbitrary headphone and surround-speaker setups, so media providers only need to package content with an IAMF-enabled encoder. The explainer notes that initial support focuses on royalty-free multichannel beds and surround audio, with native object-based streams (elements repositioned in real time) planned for future iterations.

how it works: container and playback path

IAMF reaches the renderer as an audio track inside a standard MP4 file, per IAMF §6 (IAMF in ISO-BMFF):

1. The track's sample description box (stsd) carries an IA Sample Entry — AudioSampleEntry('iamf') — which contains a mandatory IA Configuration Box (iacb, configurationVersion = 1) holding the sequence's descriptor OBUs. (The explainer loosely calls iacb the “sample entry descriptor box”; per the spec the sample entry type is iamf and iacb is the configuration box inside it.)

The encapsulation in spec syntax (IAMF §6.2, quoted):

class IASampleEntry extends AudioSampleEntry('iamf') {
  IAConfigurationBox ia_configuration_box;
}

class IAConfigurationBox extends Box('iacb') {
  unsigned int (8) configurationVersion = 1;
  leb128() configOBUs_size;
  unsigned int (8 x configOBUs_size) configOBUs;
}

Playback path, end to end:

2. The page appends MP4 segments through MSE: MediaSource.isTypeSupported() → addSourceBuffer() → SourceBuffer.appendBuffer(). When the declared codecs string matches iamf/iamf.*, Chromium's MSE stream-parser factory builds its MP4 stream parser with has_iamf = true (stream_parser_factory.cc).
3. The demuxed IA Samples feed IamfAudioDecoder, a software decoder built on the bundled iamf_tools library (built in by default — media_use_iamf_tools = true in media_options.gni; no platform/hardware IAMF path is enabled, enable_platform_iamf_audio = false).
4. The decoder renders to a target hardware layout: it decodes for the device's output layout, emitting signed-32-bit PCM, and records whether it down-mixed, up-mixed, or passed the mix through. Direct file playback (<audio src>) does not use this path — the FFmpeg demuxer has no IAMF handling in the sources read — so delivery is via MSE.

syntax: the codecs parameter

The developer-facing string is the codecs parameter of the MSE MIME type, defined by IAMF §6.4 on top of RFC 6381:

iamf.<primary_profile>.<additional_profile>.<sub-codec elements>

# e.g. IAMF (simple profile only) carrying an Opus substream:
audio/mp4; codecs="iamf.000.000.opus"

Profile fields are three digits each (0–255): 0 Simple, 1 Base, 2 Base-Enhanced, 3–255 reserved. The sub-codec element is the codecs string the stream would have outside IAMF: opus, mp4a.40.2 (AAC-LC), fLaC, or ipcm. The full field-by-field grammar, Chromium's parser rules, and worked valid/invalid strings are on the child page: the iamf.* codecs parameter.

decoding and rendering behavior

Once a stream initializes, IamfAudioDecoder (iamf_audio_decoder.cc) imposes a concrete behavior contract:

Decoder support for AudioCodec::kIAMF is compiled in when IAMF audio is enabled at build time (IsDecoderIamfBuiltInAudioType() in supported_types.cc) and — per media_options.gni — gated at runtime by the kIamfAudioDecoding feature (see the warn-block for its current state).

examples

Capability detection and MSE setup for an IAMF (simple profile, Opus substream) audio track:

const mime = 'audio/mp4; codecs="iamf.000.000.opus"';

if (!MediaSource.isTypeSupported(mime)) {
  // No IAMF decoding in this browser/build — fall back to a flat mix.
  throw new Error('IAMF playback not supported');
}

const mediaSource = new MediaSource();
const audio = document.querySelector('audio');
audio.src = URL.createObjectURL(mediaSource);

mediaSource.addEventListener('sourceopen', async () => {
  const sourceBuffer = mediaSource.addSourceBuffer(mime);
  const segment = await fetch('/media/immersive-segment.mp4');
  sourceBuffer.appendBuffer(await segment.arrayBuffer());
  sourceBuffer.addEventListener('updateend', () => audio.play(), { once: true });
}, { once: true });

Try real bitstreams: Chromium's own test files include an IAMF stereo and an IAMF 7.1.4 sample, and AOMedia hosts an IAMF binaural web demo (verified 200, 2026-07-29). The sister Chrome Platform Showcase route for this feature returned 404 at fetch time (2026-07-29), so no live embed is included here — the snippets above and the AOMedia demo are the runnable path.

web platform tests

No upstream WPT coverage was found for IAMF playback: there is no IAMF-named test under wpt/media-source, and the mediasource-is-type-supported suite does not enumerate an iamf string (both checked 2026-07-29). Chromium exercises the decoder with its own media test data (the crsrc bitstreams linked above) and the iamf_audio_decoder_unittest.cc unit suite.

browser compatibility

Interim table. There is no BCD entry for IAMF anywhere under browser-compat-data and no webstatus.dev feature (zero matches, 2026-07-29). Rows below are compiled from the linked primary sources, not from BCD.

security and privacy

• No new script-visible surface. The feature adds a codec family to the existing MSE support matrix — no new interfaces, methods, events, permissions, or storage. Fingerprinting exposure via isTypeSupported() differences already exists for every codec; IAMF support state adds one more bit to that existing vector.
• Parser/decoder attack surface. Support introduces a new demux+decode path fed by remote media. The decoder is the AOM reference implementation (iamf-tools) running inside Chromium's sandboxed media pipeline; malformed-stream hardening is inherited from that project rather than specified for web developers.
• No encrypted content. Encrypted configurations are rejected at decoder initialization (kUnsupportedEncryptionMode), so IAMF playback cannot be combined with EME on this path — there is no DRM or license-handling surface to reason about.
• Playback policies unchanged. Autoplay, volume, and output-device selection keep their existing HTML-media semantics; the decoder renders to the device-selected output layout without exposing spatial scene contents to script.

specifications

see also

• Chrome Platform Status — IAMF decoding support (API record) · tracking bug crbug.com/535279329
• AOMediaCodec/iamf-tools — encoder + reference decoder · binaural web demo
• Chromium IamfAudioDecoder · codec-string parser · kIamfAudioDecoding flag
• MDN — Media Source Extensions API (the host API; MDN has no IAMF coverage — API URL 404, zero search hits, 2026-07-29)
• Test media: IAMF stereo · IAMF 7.1.4 (Chromium test data)