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 Format: Modern Low-Latency Codec for Speech & Music

PC By Pablo Cirre • Updated May 7, 2026

Opus Audio Codec — Complete Format Guide

What Is Opus?

Opus is a modern, open-source, royalty-free audio codec developed by the Xiph.Org Foundation and Mozilla, standardised by the IETF as RFC 6716 in September 2012. It is designed to be the universal audio codec — excelling at voice communication, music streaming, and everything between, across a wide bitrate range from 6 kbps to 510 kbps, at latencies as low as 2.5 milliseconds.

Opus replaced CELT and SILK as the codec of choice for:

WebRTC — real-time browser-to-browser audio and video communication
Discord — voice chat across all platforms
Zoom, Microsoft Teams, Google Meet — enterprise video conferencing
Mumble, TeamSpeak — gaming voice chat
YouTube — audio in WebM containers (VP9 + Opus)
Firefox, Chrome, Edge, Safari 16.4+ — native HTML5 audio support

Dual-Mode Architecture: SILK + CELT

Opus's core innovation is a hybrid codec built from two fundamentally different engines:

SILK (Skype Internet Low-delay Codec)

Originally developed by Skype (acquired by Microsoft), SILK is optimised for speech signals:

Based on CELP (Code-Excited Linear Prediction) — models the human vocal tract as a time-varying linear filter
Extremely efficient for voiced speech: LPC analysis extracts spectral envelope; residual is coded with algebraic codebooks
Operates at 6–40 kbps
Excellent for low-latency, bandwidth-constrained voice calls
Native 8 kHz (NB), 12 kHz (MB), 16 kHz (WB), and 24 kHz (SWB) modes

CELT (Constrained Energy Lapped Transform)

Developed by Xiph.Org, CELT is optimised for music and generic audio:

Based on MDCT (Modified Discrete Cosine Transform) — same mathematical foundation as AAC, MP3, and Vorbis
Operates at 32–512 kbps with extremely low latency (5 ms algorithmic delay)
Provides full audio bandwidth up to 20 kHz
Particularly efficient for music, wideband voice, and mixed content

Hybrid Mode (SILK + CELT)

For bitrates and content where neither SILK nor CELT alone is optimal, Opus combines both:

SILK codes low-frequency bands (fundamental pitch and formants)
CELT codes high-frequency bands (harmonics, overtones, transients)
The combination provides superior speech quality at medium bitrates (16–32 kbps)

The Opus codec switches between these modes automatically based on bitrate, content analysis, and latency requirements — transparent to the application.

Bitrate Modes and Quality

Opus operates in three rate control modes:

Constant Bitrate (CBR)

Every frame uses exactly the specified bitrate. Used in streaming where buffer guarantees are required (RTP/RTCP, WebRTC). Slightly less efficient than VBR at a given average bitrate.

Variable Bitrate (VBR)

Bits are allocated dynamically per frame based on signal complexity. Simple silences use few bits; complex music uses many. More efficient than CBR at the same perceived quality.

Constrained VBR (CVBR)

VBR with a maximum bitrate ceiling. Used where bitrate must not exceed a bandwidth cap (e.g., mobile data plans).

Quality at Different Bitrates

Opus is remarkably efficient across an extraordinary bitrate range:

Bitrate	Mode	Appropriate Content
6–8 kbps	SILK	Voice-only, narrowband (intelligible but limited)
8–16 kbps	SILK	Voice wideband (good speech, phone quality)
16–32 kbps	SILK/CELT hybrid	High-quality voice; music with artefacts
32–48 kbps	CELT	Music (noticeable but acceptable artefacts)
64 kbps	CELT	Good music quality; comparable to MP3 128 kbps
96 kbps	CELT	Very good; exceeds MP3 192 kbps
128 kbps	CELT	Excellent; exceeds AAC 192 kbps
160–256 kbps	CELT	Near-transparent for most listeners
320+ kbps	CELT	Transparent; archival quality

Key comparison: Opus at 64 kbps achieves quality comparable to MP3 at 128 kbps — 50 % bitrate savings.

Low Latency: The Streaming Advantage

Opus's minimum algorithmic latency of 2.5 milliseconds (using 2.5 ms frames) is orders of magnitude lower than other codecs:

Codec	Algorithmic Delay	Use for Real-Time Communication
Opus	2.5–26.5 ms	Yes — designed for it
AAC-LC	~80–100 ms	Limited; noticeable echo in calls
HE-AAC	~200–400 ms	No — too much delay
MP3	~50–100 ms	Limited; echo issues
Vorbis	~60 ms	Marginal

This low latency makes Opus uniquely suitable for duplex voice communication (calls, gaming, conferencing) where codec delay contributes to echo and "talking over each other" problems.

Ogg-Opus Container

.opus files store Opus audio in an Ogg container (the same framing used by Vorbis). The file uses Vorbis Comment metadata (same as FLAC) for tags:

R128_TRACK_GAIN=-573   (ReplayGain normalisation value)
TITLE=Track Name
ARTIST=Artist Name
ALBUM=Album Title

R128 gain tags enable ReplayGain normalisation without re-encoding — playback software applies a post-decode gain adjustment to match loudness targets (EBU R128 standard).

WebM and WebRTC Containers

Beyond Ogg-Opus, Opus audio appears in:

WebM — Google's open video container for web; VP8/VP9/AV1 video + Opus audio; used natively by YouTube WebM streams
Matroska (MKV) — full support; excellent for archiving with VP9 or AV1 video
RTP/SRTP — packet-based real-time transport for WebRTC, SIP, and other voice protocols

Browser and Platform Support (2025)

Platform	Status	Notes
Chrome / Chromium	Full	Since Chrome 25 (2013)
Firefox	Full	Since Firefox 15 (2012)
Edge	Full	Chromium-based
Safari / iOS	Full	Since Safari 16.4 / iOS 16.4 (2023)
Android	Full	Since Android 4.4 (API 19)
VLC	Full	All platforms
ffmpeg	Full	Encode and decode
Discord	Native codec	Voice communications
Zoom / Teams	Core codec	Voice/video conferencing

Comparison: Opus vs. Other Codecs

Feature	Opus	AAC-LC	MP3	Vorbis
Royalty-free	Yes	No	Expired	Yes
Min latency	2.5 ms	~80 ms	~50 ms	~60 ms
Quality at 64 kbps	Excellent	Good	Fair	Good
Voice optimised	Yes (SILK)	Limited	No	No
Music optimised	Yes (CELT)	Yes	Yes	Yes
Browser support	Near-universal	Near-universal	Limited	Firefox/Chrome
WebRTC standard	Yes	No	No	No

Converting Opus Files

Opus → MP3: For hardware players without Opus support; convert via ffmpeg or KaijuConverter; note generation loss from transcoding Opus → AAC: Better compatibility on Apple devices; some quality loss from transcoding Opus → WAV/FLAC: Decode to PCM for audio editing; preserves Opus artefacts in lossless container FLAC/WAV → Opus: Optimal path; encode from lossless source to avoid transcoding artefacts; 96–128 kbps Opus for high quality archival

Opus Adoption Recommendations

For new projects requiring compressed audio:

Voice/VoIP/gaming: Opus at 32–64 kbps — better than all alternatives
Podcast/speech distribution: Opus at 48–64 kbps — excellent quality, smaller than AAC
Music streaming (web): Opus at 96–128 kbps — superior to AAC at equivalent bitrate
Music archival: FLAC (lossless) or Opus at 192+ kbps
Apple ecosystem: AAC — Opus Safari support arrived in 2023 but AAC remains safer for older devices

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

At comparable bitrates, Opus generally achieves better quality than AAC-LC, especially below 128 kbps. Opus also has significantly lower latency (2.5 ms vs 80+ ms), making it the required choice for real-time communication. However, AAC has broader hardware support (especially on Apple devices pre-2023) and wider ecosystem integration.

At comparable bitrates, Opus Geralmente achieves better quality than AAC-LC, especially below 128 kbps. Opus also has significantly baixaer latency (2.5 ms vs 80+ ms), making it the required choice para real-time communication. Porém, AAC has broader hardware support (especially on Apple devices pre-2023) e wider ecosystem integration.

At comparable Bitrates, Opus Generell achieves better quality than AAC-LC, especially below 128 kbps. Opus also has significantly niedriger latency (2.5 ms vs 80+ ms), making it the required choice für real-time communication. Jedoch, AAC has broader hardware support (especially on Apple devices pre-2023) und wider ecosystem integration.

At comparable bitrates, Opus Generalmente achieves better quality than AAC-LC, especially below 128 kbps. Opus also has significantly bajaer latency (2.5 ms vs 80+ ms), making it the required choice para real-time communication. Sin embargo, AAC has broader hardware support (especially on Apple devices pre-2023) y wider ecosystem integration.

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.

.opus is the standard extension for Opus audio in an Ogg container. Some tools use .oga (generic Ogg audio) or even .ogg (though .ogg conventionally means Vorbis). WebM files with Opus audio use the .webm extension. Always use .opus for clarity when the container is Ogg.

.opus is the padrão extension para Opus audio in an Ogg container. Some ferramentas usar .oga (generic Ogg audio) ou even .ogg (though .ogg conventionally means Vorbis). WebM arquivos com Opus audio usar the .webm extension. Always usar .opus para clarity when the container is Ogg.

.opus is the Standard extension für Opus audio in an Ogg Container. Some Werkzeuge verwenden .oga (generic Ogg audio) oder even .ogg (though .ogg conventionally means Vorbis). WebM Dateien mit Opus audio verwenden the .webm extension. Always verwenden .opus für clarity when the Container is Ogg.

.opus is the estándar extension para Opus audio in an Ogg contenedor. Some herramientas usar .oga (generic Ogg audio) o even .ogg (though .ogg conventionally means Vorbis). WebM archivos con Opus audio usar the .webm extension. Always usar .opus para clarity when the contenedor is Ogg.

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.

Yes, since iOS 16.4 (March 2023) Safari and AVFoundation natively support Opus. VLC for iOS also plays Opus. However, older iPhones (iOS 15 and earlier) and older Apple TV/HomePod models do not support Opus natively — convert to AAC (.m4a) for guaranteed Apple compatibility across all devices.

Sim, since iOS 16.4 (March 2023) Safari e AVFoundation natively support Opus. VLC para iOS also plays Opus. Porém, older iPhones (iOS 15 e earlier) e older Apple TV/HomePod models do not support Opus natively — converter to AAC (.m4a) para guaranteed Apple compatibilidade across todos os dispositivos.

Ja, since iOS 16.4 (March 2023) Safari und AVFoundation natively support Opus. VLC für iOS also plays Opus. Jedoch, older iPhones (iOS 15 und earlier) und older Apple TV/HomePod models do not support Opus natively — umwandeln to AAC (.m4a) für guaranteed Apple Kompatibilität across alle Geräte.

Sí, since iOS 16.4 (March 2023) Safari y AVFoundation natively support Opus. VLC para iOS also plays Opus. Sin embargo, older iPhones (iOS 15 y earlier) y older Apple TV/HomePod models do not support Opus natively — convertir to AAC (.m4a) para guaranteed Apple compatibilidad across todos los dispositivos.

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.

Discord uses Opus because it is optimised for real-time voice communication. Opus has 2.5–20 ms algorithmic latency (vs. 50–100 ms for MP3), making voice calls feel immediate rather than delayed. Opus also efficiently adapts to varying network conditions, dropping to lower bitrates when bandwidth is constrained while maintaining intelligible speech.

Discord uses Opus because it is optimised para real-time voice communication. Opus has 2.5–20 ms algorithmic latency (vs. 50–100 ms para MP3), making voice calls feel immediate em vez de delayed. Opus also efficiently adapts to varying network conditions, dropping to baixaer bitrates when bandwidth is constrained while maintaining intelligible speech.

Discord uses Opus because it is optimised für real-time voice communication. Opus has 2.5–20 ms algorithmic latency (vs. 50–100 ms für MP3), making voice calls feel immediate rather than delayed. Opus also efficiently adapts to varying network conditions, dropping to niedriger Bitrates when bandwidth is constrained while maintaining intelligible speech.

Discord uses Opus because it is optimised para real-time voice communication. Opus has 2.5–20 ms algorithmic latency (vs. 50–100 ms para MP3), making voice calls feel immediate rather than delayed. Opus also efficiently adapts to varying network conditions, dropping to bajaer bitrates when bandwidth is constrained while maintaining intelligible speech.

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.