Initializing... drag & drop files here
Supports: MP3
.weba container.WEBA (.weba) is the audio-only flavor of Google's WebM container, carrying an Opus or Vorbis stream and the MIME type audio/webm. The WebM Project is shepherded by Google with contributions from Mozilla and Opera, and the audio codecs inside it — Opus (IETF RFC 6716) and Vorbis (Xiph.Org) — are royalty-free. Converting MP3 to WEBA is most useful when you want smaller files than MP3 at equivalent perceived quality, or when you're already serving WebM video and want a matching audio-only fallback.
.weba keeps the toolchain (FFmpeg, libvpx, libopus) and CDN MIME setup identical.| Property | MP3 | WEBA (WebM Audio) |
|---|---|---|
| Container | MPEG audio elementary stream (.mp3) |
WebM / Matroska subset (.weba) |
| Audio codecs | MPEG-1/2 Layer III | Opus or Vorbis |
| MIME type | audio/mpeg |
audio/webm |
| Standardized | ISO/IEC 11172-3 (1993) | WebM 2010; Opus RFC 6716 (2012) |
| Licensing | Patents expired April 2017 (royalty-free since) | Royalty-free since launch |
| Typical bitrate | 128-320 kbps | 32-192 kbps (Opus); 96-256 kbps (Vorbis) |
| Quality at 96 kbps | Audible artifacts on transients | Near-transparent (Opus) |
| Sample rates | 8-48 kHz | Opus internally resamples to 48 kHz; Vorbis 8-192 kHz |
| Native browser support | Universal (all browsers, all versions) | Chrome 25+, Firefox 16+, Edge 17+, Safari 18.4+ |
| Hardware playback | Universal — every car stereo, MP3 player, hi-fi | WebM-capable devices only (smart TVs, modern phones) |
| Best for | Maximum compatibility, offline players | Web delivery, modern HTML5 audio |
Opus's quality curve is steeper than MP3's — you can drop the bitrate significantly without obvious artifacts. These are practical targets, not hard rules.
| Bitrate | Use case | Notes |
|---|---|---|
| 24-32 kbps | Mono speech, voice memos | Where MP3 needs 64-96 kbps to sound similar |
| 48-64 kbps | Stereo speech, podcasts | Good headroom for background music in interviews |
| 96 kbps | Music (casual listening) | Generally transparent for most listeners on most material |
| 128 kbps | Music (archival web delivery) | Effectively indistinguishable from source on most tracks |
| 160-192 kbps | Music (audiophile, complex material) | Diminishing returns past ~160 kbps for Opus |
Three common reasons: file size (Opus at 64 kbps roughly matches MP3 at 128 kbps in perceived quality, halving bandwidth), matching an existing WebM video pipeline so all your media uses the same container and MIME setup, and avoiding the legacy MP3 codec on a fully modern web stack. If your audience plays files in car stereos, old MP3 players, or apps that predate 2015, stick with MP3.
Pick Opus unless you have a specific reason not to. Opus is newer (IETF, 2012), has higher quality at every bitrate Xiph and independent listening tests have measured, supports low-latency framing, and is what modern browsers prefer. Vorbis is older (1.0 released 2002) and is mostly there for compatibility with content encoded before Opus existed.
Safari support depends on the version. Safari 18.4 (released April 2025 with macOS 15.4 / iOS 18.4 / iPadOS 18.4 / visionOS 2.4) added native playback of Opus in Ogg containers and improved WebM audio handling. Older Safari versions (11-18.3) play Opus only when packaged in a CAF file. For broad compatibility today, either require Safari 18.4+ or serve a parallel MP3 source via <source> fallback in your <audio> element. Chrome, Firefox, and Edge have played WEBA natively for over a decade.
If you started with a 128 kbps MP3 and re-encode to a 64 kbps Opus WEBA, the output is roughly 50% the size of the source. Keep in mind you cannot recover audio quality lost in the original MP3 encode — re-encoding MP3 to a lower-bitrate Opus is lossy on top of lossy. For best results, encode to WEBA from the original WAV/FLAC master if you have it; for the reverse direction see WAV to WEBA or use MP3 to OGG if you want an Ogg container with Vorbis instead.
Same container (WebM, a subset of Matroska), different content. .webm typically contains video plus audio; .weba is audio-only with no video track. Browsers treat both as audio/webm or video/webm MIME types depending on what's inside. Using .weba for audio-only files makes server-side MIME detection and asset organization cleaner.
The Audio Codec dropdown shows every codec the underlying engine supports — AAC, MP3, FLAC, Opus, Vorbis, PCM variants, and more — and AAC is the global default across audio conversions. For WEBA output specifically, change the dropdown to Opus (recommended) or Vorbis. Both are standards-compliant inside a WebM container; AAC inside .weba is non-standard and most browsers will refuse to play it.
Yes. Drop the whole folder or shift-select all tracks at upload. The same codec, bitrate, channel, and sample rate settings apply to every file in the queue, so you get a consistent encode across the album.
Yes. Toggle Trim, enter Start Time and Duration in either seconds or HH:MM:SS.sss format, and the converter extracts that segment during encoding — useful for clipping an intro out of a podcast episode or making a ringtone-length sample. For more involved cutting, the dedicated Audio Cutter tool gives you visual timeline controls. Or convert in the opposite direction with WEBA to MP3.
Opus internally resamples everything to 48 kHz before encoding, so picking 48000 Hz avoids a redundant downsample step. If your source MP3 is 44.1 kHz (CD-derived material) you can leave it on Original — Opus will resample either way. Don't pick 8 kHz unless you're targeting telephone-band voice; you'll lose all the high-frequency content for no real file-size benefit at modern bitrates.