WAV to MP3 Converter

You finish recording a podcast episode, or a voice memo, or a field recording captured on a handheld recorder, and the file that comes out is enormous — an hour of audio easily runs several hundred megabytes as a raw WAV. That’s fine for editing, where you want every bit of detail available, but it’s a real problem the moment you try to actually send the thing anywhere. Email attachments choke on it. Cloud storage quotas get eaten up fast. Podcast hosting platforms and messaging apps either reject the file outright or take forever to upload it over anything less than a fast connection. This tool solves that specific step: it takes a WAV file and compresses it down into an MP3, with a size and quality tradeoff you control.

Why WAV files get so big so fast

A WAV file stores audio essentially uncompressed — every single sample, captured at whatever rate and bit depth the recording was made at, with nothing removed or approximated. That’s exactly what you want while you’re recording and editing, since you’re preserving maximum detail to work with. But it comes at a real cost in file size: a standard CD-quality WAV recording runs around 10 megabytes per minute, so a 45-minute podcast episode can easily land north of 400MB before you’ve even started thinking about how to share it. MP3 uses lossy compression to shrink that dramatically — often down to a tenth of the size or smaller — by discarding audio detail that’s calculated to be the least noticeable to human hearing. For spoken word and most music, a well-chosen MP3 bitrate keeps the result sounding essentially the same to a casual listener while cutting the file down to something you can actually attach to an email.

Picking a bitrate that actually fits what you’re compressing

You get four options here — 128, 192, 256, and 320 kbps — and the right one depends heavily on what’s in the recording. For spoken-word content like podcasts, interviews, and voice memos, 128 or 192 kbps is usually plenty; voice doesn’t have the wide frequency range and dynamic complexity that music does, so it compresses cleanly even at lower settings, and most listeners won’t be able to tell the difference on a phone speaker or a pair of earbuds. For music — a demo, a mixdown, a recording meant for critical listening — 256 or 320 kbps is the safer choice, since music tends to reveal compression artifacts more readily, especially in cymbals, sustained notes, and busy mixes.

There’s no harm in erring toward a higher bitrate if you’re not sure and file size isn’t a hard constraint; the tradeoff only really bites when you’re up against an actual upload limit or trying to keep an email attachment small. If you do hit a size ceiling, dropping from 320 to 192 typically saves close to half the file size and is barely audible on spoken content — a far better trade than trying to trim the recording itself.

Who ends up needing this

Podcasters are probably the most common case: recording software and USB microphones frequently default to WAV output, and every episode needs to get shrunk down to MP3 before it goes anywhere near a hosting platform, which almost universally expects compressed audio rather than raw recordings. Musicians run into the same wall sharing rough mixes or demos with bandmates, collaborators, or a client — a WAV bounced straight out of a DAW is enormous, and nobody wants to wait ten minutes for a demo to download just to give quick feedback on it. And plenty of people just record voice memos and field audio on a dedicated recorder rather than a phone, and those devices default to WAV as their native format, meaning literally every file that comes off the device needs converting before it’s shareable at all.

A few things worth knowing

• This tool processes one file at a time, so if you’ve got a whole episode’s worth of segments, you’ll be running them through individually.
• MP3 compression is one-directional — once you’ve picked a bitrate and converted, you can’t get back the detail that gets discarded at a lower setting, so keep your original WAV around if you might need to re-export at a higher quality later.
• If the output still sounds noticeably worse than you’d like at 320 kbps, the issue is more likely in the original recording (background noise, clipping, a bad microphone) than in the compression itself — MP3 encoding won’t fix underlying recording problems.

Where the actual conversion happens

The heavy lifting is done by FFmpeg, compiled to WebAssembly so it can run directly inside your browser tab instead of on a remote server. The engine — around 30MB — downloads the first time you use this tool or any other audio or video tool on the site during your visit, and then stays cached in your browser for the rest of the session, so subsequent conversions start up quickly without repeating that download. Your WAV file itself is never uploaded anywhere; the encoding happens locally, on your own device, using your own machine’s processing power. For a raw recording that might be unreleased music, an unpublished podcast episode, or a personal voice memo, that’s a meaningful thing to not have to think about — you convert it, you download it, and it never passed through anyone else’s server along the way.