Convert WAV to MP3 — bitrate math, the "CD quality" myth, and when to stay uncompressed
WAV is uncompressed PCM — every sample written out verbatim, which is why a three-minute song weighs 30 MB. MP3 throws most of those bytes away using psychoacoustic masking and lands at 3 MB for the same three minutes with no loss most listeners will notice. That's a 10× saving. Here's the honest guide to making the trade correctly: bitrate math, the "CD quality" myth, stereo-vs-mono, and the 44.1-vs-48 kHz question nobody explains.
What WAV actually is (and why it's so big)
A WAV file is almost literally a dump of the raw audio samples a microphone or DAW captured, wrapped in a tiny 44-byte header. No compression, no psychoacoustic trickery — every sample stored verbatim. Standard CD-quality WAV is 16 bits per sample, two channels (stereo), 44,100 samples per second. The arithmetic:
16 × 2 × 44100 = 1,411,200 bits/sec = 1411 kbps
That's 11× the data rate of a 128 kbps MP3 and 4× the rate of a 320 kbps MP3. A one-minute WAV at CD spec is about 10.1 MB. A one-minute 192 kbps MP3 is 1.4 MB. Same apparent audio, seven times less storage. That's why this conversion exists.
The "CD quality" myth
Audiophile forums love to say WAV is "CD quality" and MP3 is "not CD quality." Half true. WAV is literally the format on CDs (PCM, 16-bit, 44.1 kHz, stereo). But "CD quality" doesn't mean the human ear can hear the difference between a CD and a good MP3. Blind ABX testing consistently shows that trained listeners, on revealing equipment, struggle to reliably distinguish 192 kbps MP3 from lossless on typical pop/rock material. On earbuds, on a phone, in a car — essentially everyone gets 0/10 correct.
What you lose in an MP3 encode is almost entirely content the ear was going to mask anyway: quiet sounds under loud sounds, content above 16 kHz (which adult ears usually can't hear), redundancy between the two channels. That's the whole premise of lossy audio — throw away what no one can hear, keep what matters.
Bitrate choices — what the numbers actually mean
- 128 kbps — about 1 MB per minute. Fine for spoken word (lectures, audiobooks, podcasts, interviews). Noticeably compressed on music: cymbals sound papery, reverb tails collapse, the high end shimmer is gone.
- 192 kbps — our default, about 1.4 MB per minute. Transparent for most listeners on most music. The sensible middle.
- 256 kbps — about 1.9 MB per minute. The audible-improvement zone for trained ears on high-dynamic-range material: classical, well-mixed rock, jazz with lots of brush cymbal. Casual listening on earbuds: indistinguishable from 192.
- 320 kbps — the MP3 ceiling, about 2.4 MB per minute. Objectively bigger; subjectively usually indistinguishable from 256. Use if you're archiving or if you'll re-encode later and want the maximum headroom.
Honesty corner: if your WAV source is itself a mediocre recording — a phone voice memo, a Zoom export, a stock sample pack already in MP3 wrapped in a WAV header — re-encoding to MP3 320 doesn't recover fidelity that wasn't there. Match the bitrate to what the source actually contains. 192 is almost always right.
Sample rate: 44.1 vs 48 kHz
Two numbers dominate the world:
- 44.1 kHz — the CD standard. Music, streaming (Spotify, Apple Music), most standalone audio software.
- 48 kHz — the video standard. YouTube, film, broadcast TV, most DAWs set to a video project. Anything that will be paired with picture.
If your WAV was recorded for a video project, leave it at 48. If it's a music release going to streaming services, 44.1 is the standard. Our tool preserves the source sample rate by default because resampling is a quality-loss step you don't need unless something downstream demands a specific rate. Don't do it twice. Don't do it for no reason.
Stereo vs mono — when to drop a channel
Stereo WAV → stereo MP3 is the right default for music. But for speech-only content (interviews, narration, audiobooks, solo podcasts), stereo is lying: the recording was mono, the DAW just duplicated it to the L and R channels. Keeping it as stereo MP3 doubles the file with zero perceived gain.
- Music: always stereo. Even if the track is dominantly centered, the hall reverb, panned backing vocals, and stereo widening tricks live in the differential between L and R.
- Single-voice speech: drop to mono. A mono 128 kbps MP3 sounds as clean as a stereo 192, at roughly half the size.
- Interview / two-mic: check if the two voices are actually panned. If yes, stereo. If both voices are centered and only ambient room tone differs L to R, mono is fine.
The short version
- Open WAV to MP3.
- Drop your WAV file (or dozens — batch is supported).
- Pick bitrate: 192 kbps for music, 128 kbps mono for speech.
- Leave sample rate as source unless something downstream demands a specific rate.
- Click Download. Done — no upload, no watermark.
When NOT to convert to MP3
Three cases where MP3 is the wrong target:
- You're going to edit it further. Don't stack lossy conversions. Keep the WAV (or go WAV → FLAC for lossless compression), edit, then export the final to MP3.
- You're archiving. Storage is cheap. If the recording matters long-term, keep the WAV or compress losslessly to FLAC — FLAC is about 60% of WAV size and bit-identical on decode.
- Your target platform accepts lossless. Bandcamp, HDtracks, most mastering pipelines, most sync licensing requests — all want WAV or FLAC. Don't send them a lossy file when they asked for lossless.
Honest comparison — desktop and online alternatives
Audacity (free, desktop)
The right tool if you need to edit (trim silence, normalize, denoise) before export. Its MP3 export uses LAME — same encoder we use — so the output quality is identical at matching settings. Overkill if you just need format conversion with no editing. Also can't do batch export without a plugin.
iTunes / Apple Music (free, macOS/Windows)
Drag a WAV in, right-click → Create MP3 Version. Quick for a few files. Silently downsamples to 44.1 kHz and caps bitrate at whatever the app is set to (often 256 kbps VBR, not 320). Doesn't expose mono-downmix or per-file bitrate control. Fine for "I just need an MP3 in my library," wrong for professional delivery.
ffmpeg CLI (free, desktop, power tool)
The engine under the hood of almost every converter on the internet, including ours. ffmpeg -i input.wav -codec:a libmp3lame -b:a 192k output.mp3 is the canonical one-liner. Scripts beautifully for batches. Not friendly for people who don't want to type.
Online-Audio-Converter and similar sites
Upload your file to their server, server runs ffmpeg, you download. Works fine until you consider: your 30 MB WAV is now on someone else's disk with your IP in their logs, and if the recording is sensitive (client voiceover, unreleased music, legal deposition), that's a real problem. Free tiers frequently cap file size and re-encode at sub-optimal defaults.
VLC (free, desktop)
Can convert via Media → Convert / Save. UI is famously confusing, the MP3 preset defaults to 128 kbps with no indication, and batch mode requires command-line flags. Good playback tool, mediocre converter.
Our tool
Runs LAME (via ffmpeg.wasm) in your browser. Exposes bitrate, mono downmix, and sample rate explicitly. Batch-drops dozens of files at once. No upload, no watermark, no sign-up. Trade-off: first visit downloads the ffmpeg wasm (~25 MB, cached forever after), and it's single-threaded, so very long files (2 hour+ recordings) are slower than a desktop ffmpeg on the same hardware. For typical music/podcast lengths, the speed difference is invisible.
Other inputs we handle the same way
- FLAC → MP3 if you have lossless compressed archives
- AAC → MP3 when you've extracted from iTunes or video
- MP4 → MP3 pull audio out of a video file
- WAV → FLAC if you want lossless compression instead of lossy
Common questions
Does converting WAV to MP3 lose quality?
Yes, technically — MP3 is lossy. In practice, at 192 kbps or higher, the loss is imperceptible on typical playback equipment to typical listeners. At 128 kbps, music sounds compressed if you know what to listen for. Below 128, audible on anything.
Is 320 kbps MP3 "the same as" CD quality?
No — it's a lossy compression of CD quality. It's close enough that most people can't tell in a blind test, but the underlying bytes are different from the WAV source. If you need bit-perfect, use FLAC.
My WAV is 24-bit or 32-bit float — does that matter?
No. MP3 is always 16-bit on playback. The encoder dithers down during conversion. 24-bit WAV gives you more headroom during editing, but the final MP3 is identical to what you'd get from a 16-bit source.
Why is my MP3 still huge after conversion?
Almost always: you picked 320 kbps stereo on a long file. A 2-hour podcast at 320 is 288 MB. At 128 kbps mono it's 58 MB. For speech, drop the bitrate and go mono.
Does this work offline?
Yes, after first load. Visit the tool once to let your browser cache the ffmpeg wasm binary, then you can disconnect from the internet and drop files — conversion still runs locally. Truly private.
Can I convert multiple WAVs at once?
Yes. Drop a folder or select 50 files — they queue and convert one after another. Download as a zip when done. We've tested batches of 200+ short files without issue.
Will the ID3 metadata (title, artist, album) carry over?
If your WAV has embedded INFO chunks (most DAW exports do), we'll read them and write equivalent ID3v2 tags on the MP3. If it's a raw recorder dump with no metadata, the MP3 comes out untagged — you can fill in tags later with Mp3tag, Picard, or Apple Music.
Ready?
Convert WAV to MP3 →. Pick 192 kbps for music, 128 kbps mono for speech, keep the source sample rate, and trust the encoder. If you're archiving, go FLAC instead.