Free WAV & FLAC to MP3 Converter — 320, 256, 192, 128 kbps, No Upload
A lossless-to-MP3 converter that runs entirely in your browser. Drop one WAV or FLAC file — or a whole batch — pick a bitrate (320, 256, 192 or 128 kbps), and download MP3s a few seconds later. There is no upload step, no queue on a server, no account and no file-size gate: your audio never leaves this tab. The decoding is done by a pure-JS WAV/FLAC decoder that preserves your file's native sample rate, and the encoding is a JavaScript port of LAME — the reference MP3 encoder — running in a background thread so the page stays responsive while long tracks convert.
This page is built for the people who actually care which number they pick: producers exporting previews, DJs packing crates, archivists shrinking a WAV folder, and anyone who has ever been asked by a platform for "an MP3, 320 kbps" and only had lossless files on hand.
What this converter does (and what it deliberately does not)
The pipeline is short and honest:
- Decode your WAV or FLAC to exact PCM samples at the file's native sample rate and channel count.
- Normalize anything MP3 cannot physically carry — sample rates above 48 kHz are resampled to 48 kHz, and surround files keep their first two channels.
- Encode to MP3 at constant bitrate (CBR) at the rate you selected, in a Web Worker.
What it deliberately does not do: it does not "improve" your sound, does not loudness-normalize, and does not write ID3 tags. MP3 is a delivery format — it carries exactly what your master gives it, minus what the codec throws away. If your source is quiet or clipping, fix that first: our free LUFS & true-peak normalizer measures and corrects loudness in the same in-browser way, before you encode.
WAV to MP3: what actually happens to your audio
A WAV file stores raw PCM samples — every waveform value, uncompressed. MP3 is perceptually lossy: the encoder models what the human ear can and cannot hear (masking effects, frequency sensitivity) and discards data that is statistically unlikely to be perceived. Bitrate is the budget it has to spend per second of audio:
- 320 kbps — the MP3 ceiling. Transparent or near-transparent on most modern material; the right choice when you want the smallest possible distance from the lossless original.
- 256 kbps — very close to 320 on pop/rock/EDM masters; a sensible default when 320 feels like overkill.
- 192 kbps — the practical middle: clearly smaller files, still fine for streaming previews, podcasts with music and DJ library builds.
- 128 kbps — the old MP3 standard. Audible artifacts on complex passages (cymbals, reverb tails, dense mixes); use it when size genuinely matters more than fidelity.
One honest caveat: a lossy encode is a one-way transformation. Converting WAV → MP3 loses data; converting that MP3 back to WAV recovers nothing. Keep your lossless masters, and treat every MP3 as a disposable copy. If you ever receive a low-bitrate MP3 and need to rescue detail from it before mastering, that is a different job — our mastering service runs AI detail restoration on lossy uploads as a standard step.
FLAC to MP3: the same job, one step smarter
FLAC is compressed lossless — smaller than WAV, bit-identical when decoded. This converter decodes FLAC with a pure-JS FLAC decoder, so a 24-bit/96 kHz FLAC archive converts with the same exactness as a WAV. Two practical notes:
- 96 kHz FLACs become 48 kHz MP3s. MP3 (MPEG-1 Layer III) tops out at 48 kHz sampling; anything above is resampled with a high-quality browser resampler. That is a format limit, not a defect of this tool.
- 24-bit depth does not survive. MP3 is a 16-bit-era perceptual codec; the dynamic range that matters in the output is set by the bitrate you choose, not by the source bit depth.
Why convert FLAC at all, if FLAC is better? Compatibility: MP3 still plays everywhere — old car stereos, cheap DAPs, every podcast host, every DJ booth, every form field that says "MP3 only." FLAC is the archive; MP3 is the courier.
Which bitrate should you pick?
A decision table that covers most real cases:
| Situation | Pick | Why |
|---|---|---|
| Platform demands "high quality MP3" | 320 kbps | No room for argument; closest to the master |
| Previews for clients / A&R | 256–320 kbps | Judgments about your mix should not be confounded by the codec |
| DJ crate for a gig | 192–256 kbps | Transparent enough on a club system, half the size |
| Podcast with music beds | 128–192 kbps | Speech dominates; music artifacts stay low |
| Archiving to a small drive | 192 kbps | Best size/quality tradeoff in blind tests |
If you don't know: choose 320 and stop thinking about it. Storage is cheap; a re-encode from a lost master is not possible.
Batch conversion
Drop a folder's worth of files at once. Each file appears as a row with its decoded facts — duration, sample rate, channels, input size — then a live encoding percentage, then the output size and a download button. Files encode one after another (they share a single encoder thread, which keeps memory flat even for long tracks). Changing the bitrate re-runs the whole batch at the new setting, and Download all saves every finished MP3 with its original name and an .mp3 extension.
Why "in your browser" matters here
Most online converters upload your file to a server, convert it in a queue, and keep a copy — of music that may not be released yet. Here, the entire pipeline (decode → resample → encode) is JavaScript executing on your own machine. Consequences that are practical, not philosophical:
- Privacy: unreleased tracks never cross the network.
- Speed: no upload bandwidth in the critical path; a 3-minute track typically encodes in a few seconds on a laptop.
- Availability: the page works offline once loaded, has no queue, and does not care about file size beyond your own RAM.
- No account, no watermark, no "3 free conversions per day."
Good source, good MP3
An MP3 can only ever be as good as the WAV or FLAC you feed it — the codec spends its bitrate budget on whatever is in the file. Before batch-exporting, it is worth checking the master against the numbers platforms actually look at: integrated loudness and true peak. The LUFS guide explains what −14 LUFS means for streaming normalization, and the true-peak guide covers why inter-sample peaks above −1 dBTP can add distortion after MP3 encoding. If you are matching a reference track's tempo or key before packing a set, the free BPM & key analyzer reads both from the file in the same in-browser way.
Frequently Asked Questions
Is this WAV to MP3 converter really free and unlimited?
Yes. It is a static page with a JavaScript encoder — there is no server to meter, so there is nothing to charge per conversion. No sign-up, no daily cap, no watermark.
Does converting FLAC to MP3 lose quality?
Yes, unavoidably: MP3 is lossy. The question is how much you can hear. At 320 kbps most listeners in most listening conditions cannot reliably distinguish a well-encoded MP3 from its source; at 128 kbps artifacts in cymbals and reverb become easy to hear. Keep the FLAC as your master copy.
What is the best bitrate for MP3?
320 kbps if size is not a problem — it is the MP3 maximum. 192 kbps is the best size/quality compromise for libraries. Match the table above to your situation, and never go below 128 kbps for music.
Can I convert multiple files at once?
Yes — drop as many files as you like (or select them in the file picker). They encode sequentially with per-file progress and download buttons, and "Download all" saves the finished batch.
Why does my 96 kHz FLAC come out as 48 kHz?
Because MP3 does not support sample rates above 48 kHz. The converter resamples with the browser's high-quality resampler instead of failing or silently misreporting the rate. The row shows "resampled 48 kHz" so you always know what happened.
Does the converter add ID3 tags or metadata?
No. The output is a clean MP3 audio stream. If you need tags (artist, artwork, BPM), add them in your tagging tool afterwards — that keeps the audio step predictable.
Is a browser MP3 encoder as good as desktop LAME?
It is LAME's algorithm — lamejs is a direct JavaScript port of the LAME encoder, and CBR output at a given bitrate is bit-comparable in behavior to the desktop encoder for practical purposes. What you give up versus desktop LAME is only the extra options (VBR presets, metadata, batch scripting), not audio quality at the same bitrate.
Do my files get uploaded anywhere?
No. Decoding and encoding run entirely in your browser tab. Turning off your network after the page loads does not stop conversions — there is simply no server involved.