Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use -vsync vfr to preserve VFR); (2) different audio sample rates not resampled (add -ar 48000 ); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run ffprobe on both source and output to compare timing.

Why is the audio out of sync after converting?

Common causes: (1) variable framerate source rendered as constant (use -vsync vfr to preserve VFR); (2) different audio sample rates not resampled (add -ar 48000 ); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run ffprobe on both source and output to compare timing.

Guide

Opus Audio Codec: Quality, Bitrates, Use Cases, and FFmpeg Encoding

PC By Pablo Cirre • Updated May 7, 2026

Opus Audio Codec: The Best All-Around Audio Format for the Web

Opus is the Swiss Army knife of audio codecs. Standardized by the IETF in RFC 6716 (2012) and developed jointly by Xiph.Org and Mozilla, Opus combines two very different audio technologies — the SILK codec (from Skype) for speech, and the CELT codec for music — into a single format that adapts dynamically to whatever it is encoding. The result is a codec that outperforms MP3, AAC, Vorbis, and WMA at nearly every bitrate while covering every use case from voice chat to high-quality music streaming.

Why Opus Beats Older Formats

At Low Bitrates (6–32 kbps): Voice and Communication

This is where Opus started — as a replacement for Speex and G.711 in VoIP applications. At 8–16 kbps, Opus produces intelligible, natural-sounding speech that sounds noticeably better than G.711 (standard telephone codec) or G.726 (ADPCM). At 32 kbps it delivers music that is indistinguishable from AM radio. No MP3 or AAC file sounds this good at 32 kbps.

At Medium Bitrates (64–128 kbps): Music Streaming

At 96 kbps, Opus achieves audio quality that is virtually transparent to most listeners for music — equivalent to MP3 at 160–192 kbps or AAC at 128–160 kbps. Streaming services that use Opus at 96 kbps are delivering noticeably better quality than FM radio (which is roughly equivalent to MP3 at 128 kbps).

At High Bitrates (128–320 kbps): Audiophile Use

Opus at 192 kbps is transparent (indistinguishable from lossless) for virtually all content under double-blind listening tests. Opus at 320 kbps is overkill for almost anything.

Technical Architecture

Opus is not a monolithic codec. It intelligently switches between two internal modes:

SILK mode (for speech ≤12 kHz bandwidth):

Optimized for human voice characteristics
Uses linear predictive coding (LPC) to model the vocal tract
Very efficient for pure voice; poor for music
Operates at 6–40 kbps

CELT mode (for music and wideband audio):

Transform codec using modified discrete cosine transform (MDCT)
Similar architecture to Vorbis; excellent for music and complex audio
Operates at 32–512 kbps
Operates at ultra-low latency (2.5–5ms frame size)

Hybrid mode: At 8–24 kHz, Opus runs both SILK and CELT simultaneously — SILK handles the low frequencies (voice fundamentals), CELT handles the highs (harmonics and music overtones).

Ultra-low latency: Opus frames can be as short as 2.5ms, giving algorithmic delay of just 5ms. This makes Opus suitable for real-time applications like phone calls, gaming voice chat, and live music performance — something MP3 (at 26ms algorithmic delay) and AAC (at 20–30ms) cannot match.

Variable bitrate (VBR): Opus uses VBR by default, allocating more bits to complex passages and fewer to silence or simple tones. This maximizes efficiency at any target quality level.

Channel support: Mono, stereo, and up to 255 channels via the Ambisonics extension (used in spatial audio for VR and 360° video).

Sample rates: 8, 12, 16, 24, 48 kHz (internally always processes at 48 kHz; resamples as needed).

Where Opus Is Used

WebRTC: Opus is the mandatory audio codec for WebRTC (RFC 7874). This means every Google Meet, Zoom Web, Microsoft Teams Web, Discord, and Jitsi call uses Opus when running in a browser. Billions of voice minutes per day are transmitted in Opus.

Discord: Discord's voice chat exclusively uses Opus for all audio compression.

WhatsApp and Signal: Voice messages and calls use Opus for compression.

Spotify: Uses Opus for audio streaming on all platforms (web and mobile), typically at 160 kbps (high quality) and 96 kbps (standard).

YouTube: Uses Opus in WebM containers for audio in many streams, particularly on mobile.

Web browsers: Chrome, Firefox, Edge, Safari, and Opera all support Opus natively in the Web Audio API and HTML5 <audio>/<video> elements.

Video games: Opus is used in online multiplayer games for voice chat (Source Engine, Unity, Unreal Engine all offer Opus integration).

Opus File Containers

Opus audio is almost always stored in the Ogg container (.opus or .ogg file extension). The Ogg/Opus format is standardized in RFC 7845. The .opus extension is preferred and unambiguous.

Opus can also be encapsulated in:

WebM/Matroska — for video content on the web (WebM requires Opus or Vorbis audio with VP8/VP9/AV1 video)
MP4 — supported since iOS 16 and modern Android; stored with codec=opus in the MP4 container
OGG — the original/default container

Encoding Opus with FFmpeg

# Convert MP3 to Opus at 96 kbps (web streaming quality)
ffmpeg -i input.mp3 -c:a libopus -b:a 96k output.opus

# High quality music archival at 160 kbps
ffmpeg -i input.flac -c:a libopus -b:a 160k -vbr on output.opus

# Voice call quality at 24 kbps
ffmpeg -i input.wav -c:a libopus -b:a 24k -vbr on output.opus

# Embed Opus in WebM video container
ffmpeg -i input.mp4 -c:v copy -c:a libopus -b:a 128k output.webm

# Batch convert a music library from FLAC to Opus
for f in *.flac; do
  ffmpeg -i "$f" -c:a libopus -b:a 160k "${f%.flac}.opus"
done

Opus vs. AAC vs. MP3 vs. Vorbis

Codec	Bitrate for transparency	Latency	Patent-free	Browser support
Opus	~128 kbps	5–20ms	✅ Royalty-free	✅ All modern browsers
AAC-LC	~160 kbps	20–30ms	❌ Licensed	✅ (with license)
MP3	~192 kbps	26ms	✅ (expired)	✅ All browsers
Vorbis	~160 kbps	20ms	✅ Royalty-free	✅ Modern browsers
WMA	~192 kbps	20ms	❌ Licensed	❌ Limited

Opus wins on quality-per-bit at every bitrate, has the lowest latency, and is completely royalty-free. Its only weakness is that the .opus format is not as universally supported by older hardware media players and car stereos as MP3.

Opus for Voice Recording and Podcasting

For voice content where file size matters:

32–48 kbps mono Opus sounds better than 128 kbps mono MP3
A 1-hour podcast encoded at 32 kbps Opus = ~14 MB (vs. ~56 MB at 128 kbps MP3)
Podcast hosting platforms accept MP3, but distributing internal recordings in Opus saves storage and bandwidth

For archival of voice recordings, Opus at 64 kbps stereo preserves far more nuance than MP3 at 128 kbps stereo while using half the space.

Playing Opus Files

Any modern media player supports .opus:

VLC — all platforms, no plugins needed
foobar2000 — with the foo_input_opus plugin (or natively in newer versions)
Winamp — with the in_opus plugin
mpv, mplayer — native support
Web browsers — native via <audio src="file.opus" controls>
Older iPods/iPhones: Not supported; convert to AAC for iOS compatibility
Android: Native support from Android 5.0 (API 21) onwards

Related conversions

Common video conversions that pair well with this guide:

Related conversions

Put what you just learned into practice — convert your files now in seconds, free and without registration.

Convert →

Convert →

Convert →

Convert →

Convert →

Convert →

Frequently Asked Questions

Yes, in controlled listening tests Opus consistently outperforms both MP3 and AAC at equivalent bitrates. At 96 kbps, Opus sounds roughly equivalent to MP3 at 192 kbps or AAC at 128 kbps. Opus is also royalty-free and has lower latency (5ms vs 20–26ms), making it superior for real-time communication. The main practical advantage of MP3 is broader compatibility with older hardware and software; AAC has an advantage in Apple ecosystem hardware. For web streaming, podcasting, voice chat, and new applications, Opus is the technically superior choice.

Sim, in controlled listening tests Opus consistently outperforms both MP3 e AAC at equivalent bitrates. At 96 kbps, Opus sounds roughly equivalent to MP3 at 192 kbps ou AAC at 128 kbps. Opus is also royalty-free e has baixaer latency (5ms vs 20–26ms), making it superior para real-time communication. The main practical advantage of MP3 is broader compatibilidade com older hardware e software; AAC has an advantage in Apple ecosystem hardware. para web streaming, podcasting, voice chat, e new aplicativos, Opus is the technically superior choice.

Ja, in controlled listening tests Opus consistently outperforms both MP3 und AAC at equivalent Bitrates. At 96 kbps, Opus sounds roughly equivalent to MP3 at 192 kbps oder AAC at 128 kbps. Opus is also royalty-free und has niedriger latency (5ms vs 20–26ms), making it superior für real-time communication. The main practical advantage von MP3 is broader Kompatibilität mit older hardware und Software; AAC has an advantage in Apple ecosystem hardware. für web streaming, podcasting, voice chat, und new Anwendungen, Opus is the technically superior choice.

Sí, in controlled listening tests Opus consistently outperforms both MP3 y AAC at equivalent bitrates. At 96 kbps, Opus sounds roughly equivalent to MP3 at 192 kbps o AAC at 128 kbps. Opus is also royalty-free y has bajaer latency (5ms vs 20–26ms), making it superior para real-time communication. The main practical advantage de MP3 is broader compatibilidad con older hardware y software; AAC has an advantage in Apple ecosystem hardware. para web streaming, podcasting, voice chat, y new aplicaciones, Opus is the technically superior choice.

AV1 is the most efficient (royalty-free, ~30% smaller than H.265) but encoding is slow. H.265 (HEVC) saves ~30–50% over H.264 and is supported by every modern phone and desktop. H.264 remains the safest baseline for legacy compatibility. Rule of thumb: archives → AV1, daily use → H.265, broadest reach → H.264.

Use .opus for audio-only Opus files stored in the Ogg container — this is the RFC-recommended extension and unambiguously identifies the format to media players. The .ogg extension also works but is ambiguous (Ogg can contain Vorbis, Speex, FLAC, or Opus audio). For Opus audio embedded in video, use .webm for VP8/VP9/AV1 video files or .mkv for Matroska containers. The .opus extension is recognized by all modern media players and browsers.

Use .opus para audio-only Opus arquivos stored no Ogg container — this is the RFC-recommended extension e unambiguously identifies the formato to media players. The .ogg extension also funciona mas is ambiguous (Ogg can contain Vorbis, Speex, FLAC, ou Opus audio). para Opus audio embedded in video, usar .webm para VP8/VP9/AV1 video arquivos ou .mkv para Matroska containers. The .opus extension is recognized by all moderno media players e browsers.

Use .opus für audio-only Opus Dateien stored im Ogg Container — this is the RFC-recommended extension und unambiguously identifies the Format to media players. The .ogg extension also works aber is ambiguous (Ogg can contain Vorbis, Speex, FLAC, oder Opus audio). für Opus audio embedded in video, verwenden .webm für VP8/VP9/AV1 video Dateien oder .mkv für Matroska Containers. The .opus extension is recognized by all modern media players und browsers.

Use .opus para audio-only Opus archivos stored en el Ogg contenedor — this is the RFC-recommended extension y unambiguously identifies the formato to media players. The .ogg extension also works pero is ambiguous (Ogg can contain Vorbis, Speex, FLAC, o Opus audio). para Opus audio embedded in video, usar .webm para VP8/VP9/AV1 video archivos o .mkv para Matroska contenedors. The .opus extension is recognized by all moderno media players y browsers.

CRF (Constant Rate Factor) is the best default for offline files: ffmpeg picks the bitrate frame-by-frame to maintain perceived quality. Two-pass is only better when you must hit an exact final size (DVD targets). Constant bitrate is for streaming with a fixed channel. For "smallest at quality X" always use CRF.

For high-quality transparent streaming, 128–160 kbps is the sweet spot — most listeners cannot distinguish this from lossless audio in blind tests. For storage-constrained applications like mobile streaming on data plans, 96 kbps delivers excellent quality. For voice or podcasts, 32–48 kbps mono produces speech that sounds better than 128 kbps MP3. For archival (not streaming), consider using FLAC instead of Opus, since lossless encoding incurs no quality loss at all.

For alta-quality transparente streaming, 128–160 kbps is the sweet spot — most listeners cannot distinguish this de sem perdas audio in blind tests. para storage-constrained aplicativos like mobile streaming on data plans, 96 kbps delivers excellent quality. para voice ou podcasts, 32–48 kbps mono produces speech that sounds melhor que 128 kbps MP3. para archival (not streaming), consider usando FLAC em vez de Opus, since sem perdas codificação incurs no quality loss at all.

For hoch-quality transparent streaming, 128–160 kbps is the sweet spot — most listeners cannot distinguish this von verlustfrei audio in blind tests. für storage-constrained Anwendungen like mobile streaming on data plans, 96 kbps delivers excellent quality. für voice oder podcasts, 32–48 kbps mono produces speech that sounds besser als 128 kbps MP3. für archival (not streaming), consider using FLAC anstatt Opus, since verlustfrei Codierung incurs no quality loss at all.

Common causes: (1) variable framerate source rendered as constant (use <code>-vsync vfr</code> to preserve VFR); (2) different audio sample rates not resampled (add <code>-ar 48000</code>); (3) container limitations (MP4 with variable framerate misbehaves — prefer MKV during editing, encode to MP4 only at the end). Always run <code>ffprobe</code> on both source and output to compare timing.

iOS 16+ natively supports .opus files. Older iPhones (iOS 15 and earlier) cannot play Opus directly — use VLC for iOS as a workaround, or convert Opus to AAC for native playback in the Music app. On Android, native Opus support was added in Android 5.0 (Lollipop, API 21). In web browsers, all modern versions of Chrome, Firefox, Edge, Opera, and Safari (14+) support Opus natively via the HTML5 audio element. Older car stereos and standalone audio players typically do not support Opus; convert to MP3 or AAC for those devices.

IOS 16+ natively suporta .opus files. Older iPhones (iOS 15 e earlier) cannot reproduzir Opus directly — usar VLC para iOS como um workaround, ou converter Opus to AAC para native playback no Music app. no Android, native Opus support was added in Android 5.0 (Lollipop, API 21). In web browsers, all moderno versions of Chrome, Firefox, Edge, Opera, e Safari (14+) support Opus natively via the HTML5 audio element. Older car stereos e standalone audio players tipicamente do not support Opus; converter to MP3 ou AAC para those devices.

IOS 16+ natively unterstützt .opus files. Older iPhones (iOS 15 und earlier) cannot abspielen Opus directly — verwenden VLC für iOS als ein workaround, oder umwandeln Opus to AAC für native playback im Music app. auf Android, native Opus support was added in Android 5.0 (Lollipop, API 21). In web browsers, all modern versions von Chrome, Firefox, Edge, Opera, und Safari (14+) support Opus natively via the HTML5 audio element. Older car stereos und standalone audio players typically do not support Opus; umwandeln to MP3 oder AAC für those devices.

IOS 16+ natively soporta .opus files. Older iPhones (iOS 15 y earlier) cannot reproducir Opus directly — usar VLC para iOS como un workaround, o convertir Opus to AAC para native playback en el Music app. en Android, native Opus support was added in Android 5.0 (Lollipop, API 21). In web browsers, all moderno versions de Chrome, Firefox, Edge, Opera, y Safari (14+) support Opus natively via the HTML5 audio element. Older car stereos y standalone audio players typically do not support Opus; convertir to MP3 o AAC para those devices.

Yes if you only change the container: <code>ffmpeg -i in.mkv -c copy out.mp4</code>. This remuxes the stream without re-encoding, takes seconds even for hours of footage. Limitations: codec must be supported by the target container (e.g. you cannot put H.264 in WebM, only VP8/VP9/AV1). To shrink size you must re-encode.