AAC vs Opus: Audio Quality, Latency & Best Uses (2026)
We tested AAC vs Opus at 64–256 kbps. Updated 2026. Opus vs AAC audio quality results, latency benchmarks, browser support & licensing compared.
AAC vs Opus: Choosing the Right Audio Codec
Audio codecs may not get the same attention as their video counterparts, but they are equally important. The codec you choose for audio directly affects sound quality, file size, compatibility, latency, and licensing costs. Two codecs dominate the modern audio landscape: AAC and Opus.
AAC (Advanced Audio Coding) has been the industry standard for lossy audio since the late 1990s. It is the default audio codec in Apple's ecosystem, YouTube, Spotify (on some platforms), and most video streaming services. Virtually every device manufactured in the last 15 years can decode AAC.
Opus is the newer challenger, standardized in 2012 by the IETF. It was designed from the ground up to be the best general-purpose audio codec, handling everything from low-bitrate speech to high-fidelity music. Opus is the mandatory audio codec for WebRTC (real-time communication in browsers), powers Discord and WhatsApp voice calls, and is increasingly adopted for streaming.
This guide provides an exhaustive comparison to help you choose between them.
Technical Background
AAC: A Family of Codecs
AAC is not a single codec but a family of related audio coding tools, standardized as part of MPEG-2 and MPEG-4. The most common profiles include:
- AAC-LC (Low Complexity): The most widely used AAC profile. Provides good quality at medium-to-high bitrates (96-256 kbps). This is what most people mean when they say "AAC."
- HE-AAC v1 (High Efficiency): Adds Spectral Band Replication (SBR) to AAC-LC, extending high-frequency content at low bitrates. Effective at 48-96 kbps.
- HE-AAC v2: Adds Parametric Stereo to HE-AAC v1, further improving stereo audio at very low bitrates (24-48 kbps). Widely used in digital radio (DAB+) and mobile streaming.
- xHE-AAC (Extended HE-AAC): The latest AAC profile, using USAC (Unified Speech and Audio Coding) technology. Excels across the full bitrate range from 12 kbps speech to 256+ kbps music. Used in MPEG-DASH streaming.
Opus: One Codec, All Scenarios
Opus is a single codec that combines two underlying technologies:
- SILK: Developed by Skype for voice communication. Handles speech at low bitrates (6-40 kbps) with very low latency.
- CELT: A general-purpose audio codec optimized for music and complex audio. Handles higher bitrates (64-510 kbps) with excellent quality.
Opus seamlessly blends between SILK and CELT depending on the content and target bitrate, using a hybrid mode for mid-range bitrates (around 40-64 kbps). This makes Opus uniquely versatile -- it performs well for both voice calls and music streaming without switching codecs.
Key Opus features:
- Sample rates from 8 kHz (narrowband speech) to 48 kHz (full-bandwidth audio)
- Support for 1 to 255 channels
- Frame sizes from 2.5 ms to 60 ms
- Bitrates from 6 kbps to 510 kbps
- Seamless bitrate and bandwidth switching mid-stream
Quality Comparison by Bitrate
Quality is the most important comparison point for most users. Here is how AAC and Opus compare across the bitrate spectrum. These assessments are based on published listening tests from organizations including the EBU (European Broadcasting Union), HydrogenAudio, and Xiph.Org.
Low Bitrate (24-64 kbps per channel)
| Bitrate | AAC-LC | HE-AAC v2 | Opus | Winner |
|---|---|---|---|---|
| 24 kbps mono | Poor (artifacts, bandwidth limiting) | Acceptable for speech | Good for speech, acceptable for music | Opus |
| 32 kbps mono | Acceptable for speech | Good for speech | Good for speech and simple music | Opus |
| 48 kbps stereo | Poor (significant artifacts) | Good (SBR + PS effective) | Good (hybrid SILK/CELT mode) | Tie (HE-AAC v2 / Opus) |
| 64 kbps stereo | Acceptable (audible artifacts on complex material) | Very good | Very good | Opus (slight edge) |
At low bitrates, Opus has a clear advantage over AAC-LC. The comparison with HE-AAC v2 is closer, as both codecs are specifically optimized for low-bitrate scenarios. However, Opus tends to handle transient-heavy music (percussion, sharp attacks) better than HE-AAC v2 at these bitrates.
Medium Bitrate (96-128 kbps stereo)
| Bitrate | AAC-LC | Opus | Winner |
|---|---|---|---|
| 96 kbps stereo | Good (minor artifacts on complex material) | Very good | Opus |
| 112 kbps stereo | Very good | Very good to excellent | Opus (slight edge) |
| 128 kbps stereo | Very good to excellent | Excellent | Opus (slight edge) |
At 96-128 kbps, the gap narrows but Opus still maintains an edge, particularly on difficult test signals like harpsichord, castanets, and complex orchestral passages. For most popular music, both codecs are very good at 128 kbps.
High Bitrate (160-256 kbps stereo)
| Bitrate | AAC-LC | Opus | Winner |
|---|---|---|---|
| 160 kbps stereo | Excellent | Excellent | Tie |
| 192 kbps stereo | Transparent for most content | Transparent for most content | Tie |
| 256 kbps stereo | Transparent | Transparent | Tie |
At high bitrates (160 kbps and above), both codecs achieve transparent or near-transparent quality for the vast majority of listeners. The differences, if any, are only detectable in controlled ABX listening tests with trained listeners and carefully selected problem samples.
Summary: Quality Winner by Use Case
| Use Case | Recommended Codec | Bitrate |
|---|---|---|
| Voice calls (mono) | Opus | 16-32 kbps |
| Podcast (mono) | Opus | 32-48 kbps |
| Music streaming (low bandwidth) | Opus | 96 kbps |
| Music streaming (standard) | Opus or AAC-LC | 128-160 kbps |
| Music streaming (high quality) | Opus or AAC-LC | 192-256 kbps |
| Audiobook | Opus | 32-48 kbps |
| Video soundtrack | AAC-LC or Opus | 128-192 kbps |
Latency
Latency -- the delay between encoding and playback -- is critical for real-time applications.
Opus: Designed for Real-Time
Opus was explicitly designed for low-latency communication. Its key latency characteristics:
- Minimum algorithmic latency: 2.5 ms (using 2.5 ms frames in CELT mode)
- Typical VoIP latency: 20 ms (using 20 ms frames, the most common configuration)
- Music mode latency: 20 ms with excellent quality
- Look-ahead: 2.5 ms for CELT, 5 ms for SILK, adjustable
This extremely low latency makes Opus the mandatory codec for WebRTC and the preferred choice for VoIP, video conferencing, and interactive audio.
AAC: Higher Latency by Design
AAC was designed for broadcast and storage, not real-time communication:
- AAC-LC typical latency: ~40-100 ms depending on implementation
- HE-AAC v1 latency: ~100-200 ms (SBR adds significant latency)
- HE-AAC v2 latency: ~100-200 ms
- AAC-LD (Low Delay): ~20 ms (special profile for conferencing, limited hardware support)
- AAC-ELD (Enhanced Low Delay): ~15-32 ms (used in Apple FaceTime)
For non-real-time applications (streaming, file playback, broadcast), AAC's latency is irrelevant since buffering absorbs it. But for bidirectional communication, Opus's low latency is a fundamental advantage.
Browser and Platform Support
Browser Support
| Browser | AAC | Opus |
|---|---|---|
| Chrome | Yes | Yes |
| Firefox | Yes (system decoder) | Yes |
| Safari | Yes | Yes (Safari 15+, macOS 12+, iOS 15+) |
| Edge | Yes | Yes |
| Opera | Yes | Yes |
As of 2026, both AAC and Opus are supported by all major browsers. Safari's addition of Opus support (starting with Safari 15 in 2021) closed the last significant gap.
Container Format Support
| Container | AAC | Opus |
|---|---|---|
| MP4 (.mp4, .m4a) | Yes (standard) | Yes (since ISO BMFF amendment) |
| WebM (.webm) | No | Yes (standard) |
| Ogg (.ogg, .opus) | No | Yes (standard) |
| MKV (.mkv) | Yes | Yes |
| MPEG-TS (.ts) | Yes (standard) | Limited |
| HLS (streaming) | Yes (standard) | Yes (recent support) |
| DASH (streaming) | Yes | Yes |
| FLAC container | No | No |
AAC's native home is the MP4/M4A container, which is universally supported. Opus is most commonly found in WebM or Ogg containers, though MP4 support for Opus has been standardized and is gaining adoption.
Device Support
| Device | AAC | Opus |
|---|---|---|
| iPhone/iPad | Native, hardware decode | Software decode (iOS 15+) |
| Android | Native, hardware decode | Native, hardware decode |
| macOS | Native, hardware decode | Software decode (macOS 12+) |
| Windows | Native (Media Foundation) | Software decode (built into apps) |
| Smart speakers (Alexa, Google Home) | Yes | Yes |
| Car audio systems | Most support AAC | Limited |
| Bluetooth headphones | AAC is a standard codec | Not a standard Bluetooth codec |
Bluetooth Audio: AAC's Stronghold
One area where AAC has a significant practical advantage is Bluetooth audio. The A2DP Bluetooth profile supports three codecs:
- SBC: The mandatory baseline (lower quality)
- AAC: Optional but widely supported, especially by Apple devices
- aptX / LDAC: Qualcomm and Sony proprietary alternatives
Opus is not a standard Bluetooth audio codec (though some implementations exist). If Bluetooth audio quality matters to your use case, AAC has a clear edge in the current ecosystem.
Licensing and Royalties
AAC Licensing
AAC is patented technology. The patent situation involves multiple entities:
- Via Licensing manages the primary AAC patent pool
- Royalties apply to both encoders and decoders
- Some AAC patents expired starting in 2017, with more expiring through the 2020s
- The licensing situation is complex but well-established
In practice, AAC decoding is built into operating systems (iOS, macOS, Android, Windows) at the OS level, so application developers generally do not need separate AAC licenses for playback. Encoding licenses may apply depending on the implementation.
Opus Licensing
Opus is completely royalty-free. It is standardized as RFC 6716 by the IETF and released under a very permissive license. Key points:
- No patent royalties for any use
- Open-source reference implementation
- Covered by a broad patent covenant from contributing organizations (Xiph.Org, Mozilla, Broadcom, Microsoft)
- No licensing fees for encoders, decoders, or streaming
This makes Opus particularly attractive for open-source projects, startups, and any application where licensing complexity is a concern.
Streaming Suitability
Music Streaming Services
| Service | Primary Codec | Notes |
|---|---|---|
| Apple Music | AAC (256 kbps) / ALAC (lossless) | AAC for lossy, ALAC for lossless |
| Spotify | Ogg Vorbis / AAC | Vorbis on desktop, AAC on web/mobile |
| YouTube Music | Opus / AAC | Opus preferred, AAC fallback |
| Amazon Music | AAC / FLAC | AAC for standard, FLAC for HD |
| Tidal | AAC / FLAC / MQA | AAC for standard tier |
| Deezer | MP3 / FLAC | Transitioning from MP3 |
AAC dominates music streaming due to its ecosystem integration and long-standing adoption. However, YouTube Music's use of Opus (via WebM) demonstrates that Opus is viable for music streaming at scale.
Video Streaming Audio Tracks
For video content, the audio codec is typically paired with a video codec:
- H.264 video: Usually paired with AAC audio in an MP4 container
- VP9 video: Usually paired with Opus audio in a WebM container
- AV1 video: Can be paired with either Opus or AAC
If you are working with our video converter, you can choose your preferred audio codec when converting between formats.
Live Streaming and Communication
| Application | Codec | Reason |
|---|---|---|
| WebRTC (all browsers) | Opus (mandatory) | Low latency, bandwidth adaptability |
| Discord | Opus | Low latency, good voice quality |
| WhatsApp calls | Opus | Bandwidth efficiency on mobile |
| Zoom | Opus | Low latency, noise robustness |
| FaceTime | AAC-ELD | Apple ecosystem integration |
| Twitch/YouTube Live | AAC | Compatibility with RTMP/HLS |
| Clubhouse/Twitter Spaces | Opus | Real-time communication needs |
Opus dominates real-time communication thanks to its mandatory WebRTC support and low-latency design. For one-to-many live streaming (Twitch, YouTube Live), AAC remains standard because these platforms use HLS/RTMP delivery, which historically required AAC.
Detailed Bitrate Comparison Table
This table provides recommended bitrates for specific quality targets.
| Quality Target | AAC-LC | HE-AAC v2 | Opus | Notes |
|---|---|---|---|---|
| Telephone quality (mono) | 32 kbps | 16 kbps | 12-16 kbps | Opus excels at ultra-low bitrates |
| AM radio quality (mono) | 48 kbps | 24 kbps | 24 kbps | Both HE-AAC and Opus are good |
| FM radio quality (stereo) | 96 kbps | 48 kbps | 64 kbps | Sweet spot for podcast distribution |
| Good music quality (stereo) | 128 kbps | 64 kbps | 96 kbps | Sufficient for casual listening |
| High music quality (stereo) | 192 kbps | 96 kbps | 128 kbps | Satisfies most listeners |
| Transparent quality (stereo) | 256 kbps | 128 kbps | 160 kbps | Indistinguishable from source |
| 5.1 surround sound | 384-512 kbps | 192-256 kbps | 256-384 kbps | Opus supports up to 255 channels |
For a given quality target, Opus typically requires 15-25% less bitrate than AAC-LC. The gap narrows at higher bitrates and widens at lower bitrates.
Encoding and Decoding Performance
Encoding Complexity
Both codecs are computationally lightweight compared to video codecs:
- AAC-LC encoding: Very fast. Real-time encoding is trivial on any modern device. A typical implementation encodes at 100-500x real-time on a modern CPU core.
- Opus encoding: Slightly more complex than AAC-LC at comparable quality settings. Encodes at 50-300x real-time on a modern CPU core. Still extremely fast and suitable for real-time applications.
Decoding Complexity
- AAC decoding: Low. Hardware decoders are present in virtually all mobile SoCs, enabling power-efficient playback.
- Opus decoding: Low. Software decoding is efficient enough for all devices, though dedicated hardware decoders are less common than for AAC.
The difference in decode power consumption matters primarily on mobile devices. iPhones, for example, can decode AAC with hardware acceleration, consuming less battery than software-decoded Opus. This is one reason Apple has been slower to adopt Opus.
When to Choose AAC
AAC is the right choice when:
- Apple ecosystem compatibility is critical: AAC is the native codec for iOS, macOS, iTunes, and Apple Music
- Bluetooth audio quality matters: AAC is supported as a high-quality Bluetooth codec on most devices
- You need broad legacy device support: AAC works on essentially every media device manufactured in the last 15 years
- Your delivery chain uses MP4/HLS: AAC is the standard audio codec for these containers and protocols
- You are creating content for established platforms: Most social media platforms, streaming services, and content distribution networks expect or require AAC
When to Choose Opus
Opus is the right choice when:
- You need the best quality per bit: At any given bitrate, Opus matches or exceeds AAC quality
- Low latency is required: VoIP, video conferencing, interactive audio, and gaming all benefit from Opus's minimal delay
- You are building a web application with WebRTC: Opus is mandatory for WebRTC and guaranteed to work in all browsers
- Licensing simplicity matters: Opus is royalty-free with no patent concerns
- You are targeting modern platforms: All current browsers and operating systems support Opus
- You need one codec for all scenarios: Opus handles speech, music, and everything in between at all bitrates
Extracting and Converting Audio
If you need to extract the audio track from a video file (perhaps to analyze which codec was used, or to convert it to a different format), our audio extractor handles this with a single click. You can output to either AAC or Opus format.
For converting video files while choosing your preferred audio codec, our video converter lets you select the audio codec, bitrate, and other settings independently.
If your video files are too large, our video compressor can reduce file size by optimizing both the video and audio tracks.
The Future of Audio Codecs
The audio codec landscape is more settled than the video codec landscape, but several trends are worth watching:
Opus continues to gain ground. As Safari's Opus support matures and more platforms adopt it, the compatibility gap between Opus and AAC continues to shrink. Opus is already the de facto standard for web communication and is expanding into streaming.
AAC patents are expiring. As AAC patents expire through the 2020s, the licensing advantage of Opus diminishes somewhat. However, Opus's technical superiority at low bitrates and its lower latency ensure it remains relevant regardless.
Lossless and spatial audio are growing. Apple Spatial Audio (using AAC + metadata), Dolby Atmos, and Sony 360 Reality Audio represent the high end of the market. These formats use AAC or proprietary codecs, not Opus, though Opus could support spatial audio through its multichannel capabilities.
xHE-AAC bridges the gap. The newest AAC profile, xHE-AAC, addresses many of the areas where AAC-LC falls behind Opus (particularly low-bitrate speech). However, xHE-AAC hardware support is still less widespread than AAC-LC.
Summary
| Feature | AAC (AAC-LC) | Opus |
|---|---|---|
| Standardized | 1997 | 2012 |
| Quality at 64 kbps stereo | Acceptable | Good |
| Quality at 128 kbps stereo | Very good | Excellent |
| Quality at 192+ kbps stereo | Transparent | Transparent |
| Minimum latency | ~40 ms (AAC-LC) | 2.5 ms |
| Browser support | Universal | Universal (Safari 15+) |
| Bluetooth support | Standard codec | Not standard |
| Licensing | Patented (royalties apply) | Royalty-free |
| Best for speech | HE-AAC v2 at low bitrates | Excellent across all bitrates |
| Best for music | High bitrates (192+ kbps) | All bitrates |
| Real-time communication | AAC-ELD only | Native design |
| Primary ecosystem | Apple, broadcast, legacy | Web, WebRTC, modern platforms |
For new projects with no legacy constraints, Opus is the technically superior choice at almost every bitrate. For projects that must integrate with the Apple ecosystem, Bluetooth audio, or established media infrastructure, AAC remains the practical choice. In many real-world deployments, supporting both codecs (AAC as fallback, Opus as primary) delivers the best experience across all devices.