Changelog
What changed in the converters and the guides, most recent first. Corrections are listed here too, because a site that quietly edits its mistakes is harder to trust than one that records them.
8 September 2026
First public release.
- MP3 to WAV converter, running entirely in the browser, with 16-bit, 24-bit, and 32-bit float output.
- WAV to MP3 converter using LAME, at 96 to 320 kbps.
- Source sample rate is read from the file header and preserved by default, rather than following the audio device rate.
- Batch conversion with sequential processing and a single ZIP download, built in the browser.
- Encoding moved to a Web Worker so long files do not freeze the page.
- WAV file size calculator.
- Guides covering MP3 versus WAV, converting in both directions, bit depth and sample rate, and MP3 bitrate.
Verification carried out before release: WAV output at all three bit depths decoded with ffmpeg
and confirmed as pcm_s16le, pcm_s24le, and pcm_f32le with
correct durations, sample rates, and channel counts. Integer output round-trips within one least
significant bit, float output is bit exact, and clipping was tested with input above full scale.
MP3 output confirmed as valid MPEG-1 Layer III at the requested bitrate. ZIP archives extracted
with Windows and checked against source checksums, including filenames containing accented
characters.
Under consideration
Nothing here is promised, and some of it may turn out to be a bad idea.
- Variable bitrate MP3 output, which gives better quality per megabyte but makes the output size unpredictable.
- Remembering your output settings between visits, which would mean storing something in your browser. Currently nothing is stored at all.
- Trimming start and end points before conversion, for cutting silence off long recordings.
- Support for more input formats, since the browser can already decode M4A, OGG, and FLAC.
- Translations, given how much of the traffic to converters like this one is not from English speaking countries.
If one of these would make a real difference to how you work, say so through the help page. Requests from people who actually use the tool carry more weight than guesses about what people might want.
Corrections
No corrections have been needed yet. When one is, it will be listed here with the date, the page affected, what was wrong, and what it says now.