Opus

Opus is a free, royalty-free audio codec standardized by the IETF as RFC 6716 in September 2012, jointly developed by Xiph.Org, Google, Skype/Microsoft, Mozilla, Broadcom and Octasic for both speech and music.

Extension

.opus

Full name

Opus Interactive Audio Codec

Introduced

2012

Vendor

Xiph.Org Foundation / IETF

What is inside the container

Opus is a codec, not a self-contained file format — it's most commonly delivered inside an Ogg container ("Ogg Opus," .opus extension) or inside WebM/Matroska for video-adjacent use, and it inherits Vorbis-comment-style metadata support from the Ogg container it typically travels in. Opus is distinctive among the formats here for scaling across an unusually wide bitrate range in a single codec, from narrowband speech around 6 kbit/s up to high-fidelity stereo music at 510 kbit/s, which is why it's become the default codec for both VoIP calls and music streaming on the same underlying technology.

How to open it

Browser Native HTML5 support in Chrome, Firefox and Edge; Safari added support in version 17

Windows / macOS / Linux VLC Media Player plays Opus fully across all three platforms

Cross-platform FFmpeg for command-line decoding and conversion

Real-time communication Built-in default codec in WebRTC, Discord voice, and WhatsApp voice messages

For archives

Opus is a lossy delivery/streaming format like MP3 or AAC and is not intended for archival preservation. Its real advantage for a DAM is efficiency and flexibility for delivery: a single Opus stream can be tuned for anything from a low-bandwidth voice memo to near-transparent music streaming, and being royalty-free removes any patent licensing concern that AAC carries. DAMs that stream audio previews to bandwidth-constrained users (mobile, international users on slower connections) increasingly favor Opus over MP3 for that specific tier, while keeping a lossless master (WAV/FLAC) as the true archived asset.

Opus emerged from an unusual degree of cross-industry collaboration for a codec: the IETF published it as RFC 6716 on September 11, 2012, combining Xiph.Org’s CELT codec (aimed at music) with Skype’s SILK codec (aimed at speech, contributed after Microsoft’s acquisition of Skype), with additional engineering input from Google, Broadcom, Mozilla and Octasic. The goal was a single codec that could handle the full range of interactive audio use cases — voice calls, video conferencing, live music, in-game chat — without forcing developers to choose between a speech-optimized and a music-optimized codec.

That flexibility is Opus’s defining technical trait: it can operate anywhere from roughly 6 kbit/s narrowband speech up to 510 kbit/s high-fidelity stereo, adjusting its internal balance between the speech-oriented and music-oriented coding modes automatically. Because it was standardized through the IETF as a free, open specification with no licensing fees, it sidestepped the patent questions that shaped both MP3’s and AAC’s histories, and browser and OS vendors adopted it quickly as the default codec for WebRTC-based real-time communication.

Use case	Typical bitrate	Example
Narrowband speech / VoIP	~6–20 kbit/s	Discord voice, WhatsApp voice messages
Wideband voice / video calls	~20–40 kbit/s	WebRTC video conferencing
Music streaming	96–256 kbit/s	General streaming delivery
High-fidelity stereo music	up to 510 kbit/s	Archival-quality streaming

For a DAM, Opus increasingly shows up in two places: as the codec inside voice and video call recordings ingested from meeting-recording or communication platforms, and as an efficient streaming-preview option for audio libraries serving bandwidth-constrained users. Its royalty-free status and consistently strong quality-per-bit make it an attractive default for new streaming pipelines, even where MP3 remains available as a maximum-compatibility fallback.

Frequently asked

Is Opus royalty-free for a DAM building its own streaming or transcoding pipeline?

Yes — Opus was standardized by the IETF as RFC 6716 in 2012 specifically as a free, open codec with no licensing fees, contributed to by Xiph.Org, Google, Microsoft/Skype, Mozilla and others. There's no patent royalty concern the way there is with AAC.

Why do meeting-recording and VoIP tools so often produce Opus audio for a DAM to ingest?

Because Opus is the default codec baked into WebRTC, the real-time communication standard underlying most browser-based video calling, so recordings exported from Zoom, Google Meet, Discord and similar platforms frequently contain Opus audio even if the file itself is wrapped in a different container like WebM or MP4.

Does Opus work well for both speech and music, or is it specialized like AMR?

Opus is explicitly designed to handle both well within a single codec, combining a speech-optimized coding mode (derived from Skype's SILK) with a music-optimized mode (derived from Xiph's CELT) and blending between them automatically based on content and bitrate.

Is Opus lossless like FLAC, or should a DAM avoid it for archival masters?

Opus is lossy compression, not lossless, so it belongs in a DAM's delivery/streaming tier rather than its archival tier. Keep a lossless WAV or FLAC master where fidelity needs to be preserved indefinitely.

Do all major browsers support playing Opus audio without a plugin?

Chrome, Firefox and Edge have supported Opus natively via HTML5 audio for years; Safari added native support starting in version 17. A DAM targeting older Safari versions should provide an MP3 or AAC fallback.

What file extension and container does Opus commonly use?

Most often .opus inside an Ogg container ("Ogg Opus"), though Opus audio also appears packaged inside WebM or MP4/M4A containers depending on the source application, particularly for video-call recordings.

How does Opus compare to MP3 for streaming preview quality at low bitrates?

Opus generally outperforms MP3 significantly at low bitrates (under roughly 64 kbit/s), which is a large part of why it's become the preferred choice for bandwidth-constrained streaming and voice applications rather than MP3.

Can a DAM convert legacy Opus voice recordings to a more universally compatible format for delivery?

Yes — FFmpeg decodes Opus and can re-encode to MP3, AAC, or a lossless format if the source quality warrants it, which is the standard approach for a DAM that needs to serve Opus-sourced content to older or non-WebRTC-aware playback environments.

Sources

The IETF published Opus as RFC 6716 on September 11, 2012, developed jointly by Xiph.Org, Skype/Microsoft, Google, Broadcom, Mozilla and Octasic. checked 2026-08-07 — Xiph.Org — Opus audio codec is now RFC6716