Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting WAV to MP3 takes a file that is roughly ten megabytes a minute and turns it into one about a tenth that size, which is normally the whole reason anyone does it. Drop the file above and it encodes inside your own browser, so an interview or a voice recording is never uploaded anywhere.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
WAV to MP3
A WAV stores every sample as a raw number with nothing clever applied, which is why its size depends almost entirely on its length. CD-quality stereo runs about 10 MB per minute whether the minute holds an orchestra or silence. Forty minutes is 400 MB, and an hour-long interview is around 600.
That collides with almost every limit that exists. Most email providers stop at 25 MB. Voice-note fields, submission portals, podcast hosts and messaging apps all sit well below the size of an untouched WAV. The format is not doing anything wrong — it was designed for editing, not for sending — but the file will not move, and that is what brings people here.
A phone voice memo, a Zoom recording, an interview and a lecture are speech, and speech is exceptionally cheap to encode. Balanced writes 160 kbps, at which a spoken recording is essentially indistinguishable from the original, and Small file at 96 holds up too. An hour of speech is about 72 MB at 160 and 43 MB at 96, down from 600.
Music needs more room. Balanced at 160 kbps is the setting worth taking for anything with instruments in it, and High quality at 320 is where the argument stops for all practical purposes. The one case that genuinely rewards the higher setting is live and acoustic material — audience noise, cymbals and long reverb tails are exactly what the encoder finds hardest.
This is a newer version of the same wall and it catches people unprepared. ElevenLabs, Suno and most text-to-speech exports hand back WAV because it is the format that loses nothing on the way out. A few minutes of generated narration is therefore tens of megabytes before anyone has done anything with it.
For that material the choice is easy: generated speech is speech, so the Small file band is enough and the result is what you actually publish or embed. Keep the WAV only if you intend to edit it further — once it is mixed and final, the MP3 is the useful copy and the WAV is just storage.
MP3 is lossy by design. It models what human hearing cannot detect — a quiet sound immediately after a loud one, frequencies masked by others nearby — and discards it. The removed audio is genuinely gone, and no later conversion brings it back.
What it leaves alone is the part people worry about most. Length, pitch, speed, and the intelligibility of speech are untouched. A conversation converted at 96 kbps transcribes exactly as well as the original, which matters if the recording is going to a transcription service afterwards.
Every MP3 encode discards a little audio, so encoding an MP3 again compounds it. If you need three versions at three bitrates, make all three from the WAV rather than making a small one from a large one.
The same rule decides what to archive. Keep the WAV if the recording will ever be edited, remixed or re-cut; it is the only copy that still holds everything. If it is a voice memo you will listen to once and file, converting and deleting the WAV is a perfectly reasonable thing to do with 600 MB.
A great many WAVs are stereo files carrying one microphone, duplicated across both channels. That is common in Zoom recordings, phone memos and single-source interviews. Encoding that as stereo spends twice the bitrate to say the same thing twice.
Where the source is genuinely one voice, mono at 96 kbps sounds identical to stereo at double the rate and produces a file half the size. Keep stereo for music, for anything with a stereo field worth preserving, and for recordings with two people on separate channels.
WAV has no real metadata convention. Some tools write a small INFO chunk, most write nothing, and the fields MP3 uses — title, artist, album, artwork — usually have no source to come from. Expect the MP3 to arrive unlabelled.
If the files are going into a music library or a podcast feed, plan on tagging them afterwards; any audio player or tag editor will do it. Nothing is lost in the conversion, because there was nothing there to lose.
Drop up to a hundred WAVs and each is encoded separately, then handed back together as a ZIP. This is the normal case rather than the exception — recorders, conference tools and voice-memo apps produce sessions in batches, not one file at a time.
Because nothing is uploaded, a large batch costs no bandwidth and waits in no queue. It costs processor time on your own machine, which is why a folder of long recordings is worth starting before you make coffee.
The encoder runs inside the browser tab, so the audio is never transmitted. Given what people convert here, that is not a small detail: interviews under embargo, medical and legal recordings, therapy sessions, and voice notes recorded in someone’s home.
It also means there is no upload to sit through and no daily allowance. The one ceiling is the free tier’s 100 MB a file, which at ten megabytes a minute is about ten minutes of CD-quality stereo — a 600 MB interview has to be split before it will convert.
| WAV | MP3 | |
|---|---|---|
| Full name | Waveform Audio | MPEG Audio Layer III |
| File extension | .wav, .wave | .mp3 |
| Media type | audio/wav | audio/mpeg |
| Compression | Uncompressed | Lossy — file size is bought with quality |
| First published | 1991 | 1993 |
| Published by | Microsoft | Fraunhofer IIS |
| Specification | RIFF WAVE | ISO/IEC 11172-3 |
| Licensing | Published, not standardised | Open standard |
| Standing today | Current | Current |
| Bit depth | 32 | — |
| Audio channels | up to 65,535 | up to 2 |
| Opens in a browser | Every browser | Every browser |
| Considered instead | FLAC, AIFF | AAC, OPUS, FLAC |
MP3 has nowhere to put the document properties, so that goes no further than the WAV. Worth checking before the original is deleted, and worth knowing if the point was to strip it.
WAV defines up to 65535 audio channels and MP3 up to 2. A surround mix is folded down rather than carried across.
Audacity reads both WAV and MP3, so there is a way to check the result against the original without a second tool.
The file gets substantially smaller, and it gets smaller by discarding detail. WAV keeps everything; MP3 keeps what the eye is poor at noticing. On a photograph that trade is close to free; on text, a screenshot or a line drawing it is visible as haloing around the edges.
The two are aimed at different work: WAV at editing and archiving, MP3 at handing a finished file over, phones and streaming. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.
WAV is Microsoft's format, published in 1991. It records 32 bits per channel.
MP3 comes from Fraunhofer IIS and dates from 1993, specified as ISO/IEC 11172-3. Audacity, VLC and iTunes all read it.
About a tenth, and the exact figure follows the band. A WAV runs roughly ten megabytes a minute regardless of what is in it, so an hour-long interview is around 600 MB; the same hour is about 72 MB on Balanced and 43 MB on Small file. That is usually the difference between a file that sends and one that does not.
The control offers three bands rather than a number, and for MP3 they resolve to 96, 160 and 320 kbps. For speech — interviews, voice memos, podcasts, narration — Small file is plenty. For music, High quality at 320 is the point past which almost nobody can hear a difference. If you are unsure, Balanced at 160 is the safe answer for anything.
Slightly, and usually not audibly. MP3 discards audio it judges you cannot hear, which is a real loss but a well-tuned one at 160 kbps and above. Speech survives this almost perfectly. Where it shows first is on cymbals, applause and reverb tails, which is why a live recording deserves a higher bitrate than a voice memo.
If it is a master, yes. MP3 is a one-way trip: converting the result back to WAV restores the file size and none of the audio. Keep the WAV as the archive copy and treat the MP3 as the copy you send. If the WAV is a voice memo you will never edit again, this hardly matters.
No. The encoding happens inside your browser, so the audio never reaches us or anyone else — which is worth knowing, because the WAVs people need to shrink are frequently interviews, therapy sessions, legal recordings and voice notes never meant to leave a phone. You can watch the network tab during the conversion and confirm nothing is sent.
This page converts one into the other. If you are choosing rather than converting, WAV vs MP3 answers which to use, for what, and what each is bad at.