How to Convert MP3 to Opus

Opus is substantially more efficient than MP3. At 64 kbps, Opus typically sounds better than MP3 at 128 kbps. For web audio, background music, and streaming, this efficiency translates directly to bandwidth cost and page load speed. Common use cases for MP3-to-Opus conversion: converting background music for web applications (reduces load time), preparing audio for WebRTC applications, creating smaller audio assets for Progressive Web Apps, and converting podcast audio for distribution to apps that support Opus (reducing hosting storage costs). Opus is also used by Discord for voice channels and WhatsApp for voice messages — both take advantage of its low-bitrate speech quality.

Converting MP3 to Opus is a lossy-to-lossy transcode. Each generation of lossy encoding introduces some quality degradation. The MP3's compression artifacts will be present in the Opus output. To minimize transcoding penalty, set the Opus output bitrate reasonably high relative to the source MP3 bitrate: Source MP3 at 128 kbps: encode Opus at 96–128 kbps. Source MP3 at 192 kbps: encode Opus at 128–160 kbps. Source MP3 at 320 kbps: encode Opus at 128–192 kbps. Setting Opus bitrate above 160 kbps yields diminishing returns — Opus is already highly efficient at 128 kbps for music.

AudioUtils uses FFmpeg compiled to WebAssembly. The conversion: FFmpeg decodes the MP3 using the LAME decoder, obtains raw PCM samples, and encodes them using libopus into an OGG container with Opus audio. The output is an .opus file (OGG container with Opus codec). This plays natively in Chrome, Firefox, Edge, and Android apps. It does not play natively on Safari or iOS without a polyfill or additional codec support. Conversion runs entirely locally. MP3 files are typically 3–10 MB for songs, and conversion completes quickly — usually in a few seconds.

Opus is the recommended codec for web audio in many contexts. The Web Audio API, MediaRecorder API, and WebRTC all support Opus natively in modern browsers. For HTML5 audio elements, Opus in an OGG container serves on Chrome, Firefox, and Edge. To cover Safari, provide an AAC (M4A) fallback: This pattern — Opus primary, AAC fallback — delivers the best quality-per-byte to browsers that support Opus while remaining compatible with Safari. For background music on websites, converting your MP3 library to Opus can meaningfully reduce asset sizes and improve page performance metrics.

Opus bitrate recommendations by use case: 6–24 kbps — narrowband voice (telephone quality). Not useful for music. 32 kbps — wideband voice. Suitable for speech-only content like podcasts. 48–64 kbps — general audio including simple music. Used by Discord voice channels. 96 kbps — music streaming. Near-transparent quality for most content. 128 kbps — high-quality music. Transparent to virtually all listeners. 160–192 kbps — very high quality. Rarely needed for Opus. For converting MP3 music to Opus for web delivery, 96–128 kbps is the standard target. This provides excellent quality while achieving 30–50% smaller files than the equivalent MP3.

Safari and iOS do not natively support Opus/OGG. If your audience primarily uses Apple devices or Safari, Opus may not be the right target format. Consider AAC or MP3 instead. Some audio editing software does not import Opus. If you need to edit the converted file, convert to WAV first for maximum compatibility. Opus files may not be accepted by podcast platforms, streaming services, or broadcast tools that have specific format requirements. Check your platform's accepted formats before converting an entire library. For personal use (playback on modern devices), Opus is excellent. For professional delivery with broad compatibility requirements, assess whether the efficiency gains justify the compatibility tradeoffs.