Queue the files
Drop as many WAVs as you need. They are processed one at a time, so memory use stays bounded even when the folder is large.
Browser tool · nothing uploaded
Drop several WAVs, pick a bitrate or a target file size, and let the queue run. Everything is encoded on this device; the files are never uploaded.
Optional. The bitrate is calculated from the duration; it cannot exceed 320 kbps.
The MP3s were written in this tab. The WAVs were not uploaded.
convertwavtomp3.com converts WAV files to MP3 in batches, in the browser; files are never uploaded.
The WAV file is read from your disk, its audio track is decoded, and the samples are re-encoded as MP3. The output is written in this tab and offered as a download. There is no upload endpoint, no account and no queue.
If you need the reverse direction, or a different source format, this page is deliberately single-purpose. The how-it-works page explains the engine, the browser requirements and the cases where the converter will refuse a file rather than write a broken one.
Drop as many WAVs as you need. They are processed one at a time, so memory use stays bounded even when the folder is large.
A target size in MB is converted into a CBR bitrate from each file's duration. If the target is too small for the duration, the page says so instead of pretending.
Individual downloads stay available. A ZIP is offered when the total output is under 500 MB, because a larger ZIP would have to sit in memory.
| Property | Result | Notes |
|---|---|---|
| Queue | Sequential | One file at a time keeps memory bounded. |
| Target size | Computed CBR bitrate | From duration; clamped to the MP3 range. |
| Bitrate | 64–320 kbps CBR | CBR is predictable; VBR is not offered. |
| ZIP | Under 500 MB total | Larger batches download individually. |
| Naming | Source base name + .mp3 | Duplicates are numbered in the ZIP. |
| Metadata | Basic tags may carry | Not guaranteed across players. |
Container overhead and encoder padding move the final byte count by a small amount. The page shows the estimate before conversion, not a guarantee after it.
How the browser queue handles a folder of WAVs, how names and ZIPs work, and the point where a desktop tool is the better choice.
GuideBrowser, Music app, Audacity and Terminal ffmpeg. What each one does with a WAV, which one writes MP3, and how to avoid an unnecessary upload.
GuideThe bitrate math behind a target file size, worked examples for podcasts and music, and the cases where the target is impossible.
Drop the files or select several in the picker. The queue processes them sequentially. A browser folder picker is not used because support is uneven and it can sweep in files you did not mean to convert.
It is bitrate math: target bytes × 8 ÷ duration. The result is clamped to the MP3 range. If the target is too small for the duration, the lowest rate still produces a larger file, and the page tells you before you start.
No upload limit. The practical limit is memory and how long you want to wait. The queue is sequential and each finished file is released to a download.
No. Audacity is a desktop editor with a batch macro system. This is a browser converter for the common case: a folder of WAVs that need to become MP3s. The guide explains when Audacity is the better tool.
No. The WAVs are read from disk and processed in this tab. There is no upload endpoint.
Yes. Each output keeps the source base name and changes the extension to .mp3. Duplicate names in the ZIP are numbered instead of overwritten.
The full support matrix and browser requirements are on how it works. Privacy details are on privacy.