Loading audio tools…
Loading audio tools…
Convert any audio file to WebM/Opus, the best browser-native lossy format. Better than MP3 at the same bitrate.
People searching for an "MP3 converter" almost always want the same thing: a smaller, widely compatible audio file they can share, upload, or store without eating up space. Browsers can't encode true MP3 files natively, so this tool uses the best available browser-native alternative — WebM with Opus audio — which matches or beats MP3 quality at the same bitrate and is supported everywhere modern audio is played, including YouTube, Spotify uploads, and every major browser. Upload a file, pick a bitrate, and convert entirely in your browser using the Web Audio API — no install, no server upload.
Your audio never leaves your browser. All processing uses the Web Audio API locally.
Drop any audio file to convert
WAV, OGG, AAC, FLAC, M4A, MP4, WebM…
Upload your audio file
Click 'Choose File' or drag and drop any audio file onto the upload area.
Select a bitrate
Choose 128 kbps for small size, 192 kbps for a balanced result, or 320 kbps for the highest quality.
Click Convert
Hit the Convert button. The tool encodes your audio to WebM/Opus entirely in your browser.
Download the WebM/Opus file
Click Download to save the converted file. It will have a .webm extension.
MP3 is a lossy audio codec, meaning it shrinks file size by permanently discarding audio data using psychoacoustic modeling — algorithms that identify frequencies the human ear is unlikely to notice (masked by louder nearby frequencies, or outside typical hearing sensitivity) and remove them before compressing what's left. The tradeoff is a bitrate: more kilobits per second preserved means less data discarded and higher perceived quality, but a larger file. This is exactly the same tradeoff every lossy codec makes, including the one this tool actually uses.
Here's the important technical nuance: web browsers do not expose a native API for encoding true MP3 files. There is no built-in MP3 encoder in JavaScript's Web Audio API or MediaRecorder API. What browsers do support natively is Opus, a modern lossy codec built specifically for the web, which this tool uses to produce a WebM container file. Opus uses more advanced psychoacoustic modeling than the decades-old MP3 codec and consistently delivers equal or better perceived quality at the same bitrate — it's the format Discord, YouTube, and WhatsApp rely on internally for exactly this reason.
In practice, this means you get all the benefits people actually want from "MP3 conversion" — a smaller, shareable, widely compatible lossy audio file — using a codec that's arguably better suited to the job. The 128/192/320 kbps preset structure mirrors the bitrate options people expect from MP3 encoders, so the workflow feels familiar even though the underlying codec is different. If your target destination specifically requires a literal .mp3 file extension (some legacy hardware or older desktop software), you'll need a native encoder like FFmpeg or Audacity — no browser tool can produce a true MP3 container.
If you're deciding between formats, it helps to compare this against the other audio-tools converters. OGG Vorbis, handled by the OGG Converter, is another open lossy codec with similar goals but different container and licensing history — popular in games and open-source software. If your goal is simply a smaller file at the same sample rate without changing codec, the Compress Audio tool takes a different, resampling-based approach instead.
Lossy audio codecs like MP3, Opus, and AAC don't just compress audio — they also decide how to allocate the available bits across the duration of the file. Three encoding modes handle this differently:CBR (constant bitrate), VBR (variable bitrate), and ABR (average bitrate). Understanding the distinction helps explain why some files sound better than others at the same "bitrate."
CBR allocates exactly the same number of bits per second throughout the entire file, regardless of whether the audio at that moment is complex (dense music with many instruments) or simple (silence, or a single sustained note). The advantage is predictability: a 3-minute file at 192 kbps CBR will always be exactly the same size, which makes streaming bandwidth calculations straightforward. The disadvantage is inefficiency: during quiet or simple passages, you're allocating bits you don't need, and during complex passages, you might not have enough bits to avoid audible artifacts. Think of it as driving at a fixed speed regardless of road conditions.
This tool outputs CBR Opus because the browser's MediaRecorder API doesn't expose VBR encoding controls — it just encodes at the target bitrate you specify. For most use cases (podcasts, voice memos, music sharing), CBR is perfectly adequate. The inefficiency only matters if you're encoding hundreds of hours and storage or bandwidth is at a premium, in which case desktop encoders with VBR support (like FFmpeg's Opus encoder) are a better fit.
VBR adjusts the bitrate dynamically based on the complexity of the audio at each moment. During a complex orchestral passage, it allocates more bits to preserve detail; during silence or a simple vocal line, it drops to a lower bitrate since fewer bits are needed for transparent encoding. The result is better perceived quality for the same average file size, or smaller files at the same perceived quality compared to CBR. VBR Opus at an average of 128 kbps often sounds as good as CBR Opus at 160 kbps, because the bits are spent where they matter most.
The tradeoff is slightly less predictable file sizes (a 3-minute VBR file might be 3.1 MB or 2.9 MB depending on content complexity) and compatibility issues with very old hardware players that expect fixed bitrate. For web distribution, modern streaming, and archival, VBR is almost always the better choice, but browser-based encoding doesn't support it. If you need VBR Opus, use FFmpeg or Audacity on the desktop.
ABR is a middle ground: the encoder targets a specific average bitrate (like 192 kbps) but allows short-term fluctuation above and below that target to handle complexity variation. The final file size is close to what CBR would produce, but quality is better because the encoder has flexibility to allocate bits where needed. ABR is less common than CBR or VBR in modern encoders — most tools pick one of the two extremes — but some legacy MP3 encoders offered it as a compromise option.
Choosing a bitrate is fundamentally a tradeoff between file size and perceived audio quality. Lower bitrates discard more audio data, resulting in smaller files but also more audible compression artifacts — "underwater" sound, metallic ringing, loss of stereo imaging, or flattened dynamics. Higher bitrates preserve more detail, producing files that sound closer to the original source but take up more storage and bandwidth. The key question is: where's the threshold where further quality improvement becomes imperceptible for your specific content and listening conditions?
128 kbps Opus is roughly equivalent to 160–192 kbps MP3 in perceived quality, making it a solid choice for spoken word content where file size matters. Podcasts, audiobooks, voice memos, and lecture recordings sound clear and intelligible at 128 kbps, with file sizes around 1 MB per minute of audio. Music at 128 kbps Opus is acceptable for casual background listening on phone speakers or laptop built-ins, but audiophiles and anyone using good headphones will notice compressed highs, slightly muffled vocals, and reduced stereo width compared to higher bitrates.
Use 128 kbps when storage or bandwidth is constrained (mobile data uploads, email attachments, large podcast archives), when the content is primarily voice, or when the listening environment is noisy enough that subtle quality differences won't be noticed anyway. Don't use it for music you plan to keep long-term or critical listening scenarios.
192 kbps is the sweet spot for most use cases. Opus at this bitrate is perceptually transparent for the majority of listeners on typical consumer equipment — the compressed version sounds indistinguishable from the source unless you're A/B testing with high-end headphones and trained ears. File sizes land around 1.4 MB per minute, which is manageable for most storage and streaming scenarios. Music retains its fullness, vocals sound natural, and instrument separation is preserved.
Use 192 kbps as your default for mixed content (podcasts with music interludes, interview recordings with background ambience, or casual music libraries). It's the bitrate streaming services like Spotify use for their "high quality" tier, and it handles both speech and music gracefully without bloating file sizes.
320 kbps Opus is overkill for most scenarios, but it's the setting to use when quality is paramount and file size is secondary. At this bitrate, compression artifacts are virtually undetectable even on reference-grade equipment, and the file is suitable for archival purposes or further processing (though starting from lossless WAV/FLAC is always preferable if available). File sizes approach 2.4 MB per minute — still far smaller than uncompressed WAV, but large enough to matter if you're storing hundreds of hours.
Use 320 kbps for music you plan to keep indefinitely, for source material you might re-edit or remix later, or when the listening context demands maximum fidelity (studio monitoring, critical sound design work, personal music archives where you want zero regrets about quality loss). For anything destined for casual playback, streaming upload, or mobile consumption, 192 kbps is usually sufficient and saves considerable space.
One critical rule: avoid re-encoding lossy files whenever possible. If your source is already MP3, AAC, or another lossy format, converting it to Opus means you're applying two rounds of lossy compression, each discarding different audio information based on its own psychoacoustic model. The result compounds artifacts — you get the worst of both encoders' weaknesses rather than the best. Always convert from the highest-quality source available, ideally lossless formats like WAV, FLAC, or ALAC. If you only have a lossy source, keep it in its original format unless format compatibility or file size absolutely require conversion, and if you must re-encode, use the highest bitrate available to minimize additional loss.
Unlike most online tools, Toolivon processes everything directly in your browser using the Web APIs built into Chrome, Firefox, Safari, and Edge.
Last updated:
Your audio files never leave your device
All processing runs directly in your browser using built-in Web APIs — the Canvas API, Web Audio API, and WebAssembly. Nothing is uploaded to any server. There is no account, no email, and no data retention. You can verify this yourself: open your browser's DevTools Network tab and watch zero outbound file requests while the tool processes your audio files.
GDPR-friendly · Works offline after page load · No file size limits beyond your device memory