Opus

Opus
Name	Opus
Developer	Xiph.Org Foundation; IETF codec working group
Released	2012
Latest release	1.3.1
Operating system	Cross-platform
License	BSD

Opus

Opus is a lossy audio codec standardized by the Internet Engineering Task Force and developed by the Xiph.Org Foundation in collaboration with developers from Skype Technologies S.A., Mozilla Foundation, and others. It combines elements from the SPEEX and CELT codecs and was published as RFC 6716 to provide a single, versatile format for interactive speech, music, and general audio transmission across applications such as VoIP, streaming, conferencing, and file storage. The codec emphasizes low latency, widebitrate scalability, and royalty-free licensing to encourage broad adoption by companies and projects including Mozilla Firefox, Google Chrome, WhatsApp, Discord (software), and Zoom Video Communications.

Overview

Opus targets realtime and non-realtime audio use, offering bitrates from 6 kbit/s to 510 kbit/s and sampling rates from 8 kHz to 48 kHz. It integrates the linear prediction techniques from SPEEX for narrowband speech and the transform coding techniques from CELT for music, enabling seamless mode switching and hybrid modes for mixed-content frames. The codec was standardized through meetings of the IETF Audio/Video Transport Working Group and documented in RFC 6716, promoting interoperability among clients such as FFmpeg, GStreamer, VLC media player, and media frameworks used by Android (operating system) and iOS. Its royalty-free policy was advocated by organizations including Mozilla Foundation and Xiph.Org Foundation, and influenced adoption by platforms such as YouTube, Facebook, and Microsoft Teams.

History and development

Development began in the late 2000s when contributors from Skype Technologies S.A. and the Xiph.Org Foundation sought a unified codec to replace multiple narrowband and wideband codecs. Early prototypes merged CELT, designed by Jean-Marc Valin and members of Xiph.Org Foundation, with elements of Speex; Jean-Marc Valin later played a key role in the standardization process at the IETF. The codec underwent multiple interoperability tests and submissions to the IETF, culminating in the publication of RFC 6716 in 2012. Subsequent maintenance and feature additions were driven by contributors including engineers from Mozilla Foundation, Google LLC, and independent developers, with updates coordinated through public repositories hosted on platforms like GitHub. Industry events such as the WebRTC project meetings and conferences like IETF meetings and FOSDEM showcased implementations and interoperability results, accelerating deployment across products from Apple Inc., Google, and open-source projects.

Technical design and features

Technically, the codec operates in three principal modes: a narrowband/speech-optimized linear predictive coding mode derived from SPEEX, a transform-based low-delay mode derived from CELT, and a hybrid mode that combines both for mid-to-high frequencies. Frame sizes range from 2.5 ms to 60 ms to trade off latency against coding efficiency; the shortest frames enable interactive use in VoIP and WebRTC while longer frames improve compression for streaming services. Opus supports variable bitrate (VBR), constant bitrate (CBR), and constrained VBR, along with inband signaling for features like forward error correction and packet loss concealment used by systems such as RFC 3550-based RTP stacks. The codec exposes complexity levels and channel-coupling strategies for mono, stereo, and multichannel audio, meeting requirements of consumer products like Sonos (company) and professional solutions from Dolby Laboratories partners. Cryptographic transport is typically handled by DTLS or SRTP in realtime applications, while file encapsulation often uses containers supported by Matroska and Ogg (container).

Implementations and software ecosystem

Reference implementations are maintained in C by contributors affiliated with Xiph.Org Foundation and hosted on GitHub. Major multimedia frameworks provide bindings: FFmpeg includes encoder and decoder support, GStreamer offers plugins, and players like VLC media player and MPlayer support playback. Web platforms integrated Opus via the Web Audio API and WebRTC stacks implemented in browsers such as Mozilla Firefox and Google Chrome. Server-side ecosystems including Asterisk (PBX) and FreeSWITCH implement Opus for telephony, while cloud providers like Amazon Web Services and Google Cloud Platform facilitate transcoding workflows through managed services interfacing with libraries such as libopus. Hardware vendors and DSP manufacturers have produced instruction-tuned implementations for architectures like ARM and x86 and provided NEON and SSE optimizations integrated into mobile platforms from Samsung and Qualcomm.

Applications and use cases

Opus is widely used for interactive communications (conference calling, gaming chat), media streaming (music and podcasts), and archival of mixed-content recordings. Services such as WhatsApp, Discord (software), Zoom Video Communications, and Skype adopt Opus for voice and group audio to balance bandwidth and latency across heterogeneous networks including mobile carriers like Verizon and Vodafone. Web realtime applications built on WebRTC leverage Opus to unify codec negotiation across browsers and signaling systems like SIP (Session Initiation Protocol). Content distribution networks and streaming platforms including YouTube and SoundCloud make use of Opus for low-bitrate music distribution, while open-source projects like Audacity provide import/export pipelines via libopus.

Reception and standards compliance

Opus received praise from standards bodies and industry for its flexibility, low latency, and audio quality across bitrates, earning endorsements during IETF standardization and adoption by major browser vendors. Independent listening tests and codec comparisons by universities and research groups showed Opus outperforming legacy codecs such as MP3, AAC (codec), and Vorbis at comparable bitrates for many content types. Its royalty-free status under permissive licensing encouraged use in open-source stacks and by commercial vendors; however, some producers maintained legacy compatibility with codecs standardized by ISO/IEC and MPEG families. Opus remains part of audio profiles recommended for WebRTC applications and is included in multimedia profiles of container standards like Matroska and streaming recommendations from consortiums such as W3C.

Category:Audio codecs