How to convert wav to 320 kbps mp3 — free, no upload
- Step 1Open the converter — Load the wav-to-mp3 tool. The FFmpeg WebAssembly engine loads on first use and is cached for later.
- Step 2Drop your master WAV — Drag a single
.wavonto the dropzone. It's read into browser memory only — no upload. Any sample rate and bit depth (16/24/32-bit float), mono or stereo, is accepted. - Step 3Select 320 kbps — In the Bitrate dropdown choose
320 kbps · best. This sets FFmpeg's-b:a 320k, the highest CBR the tool offers. - Step 4Encode — Run it.
libmp3lametranscodes the WAV to a 320 kbps MP3 on your CPU via WebAssembly. A full-length track encodes in a few seconds; encode time scales with duration. - Step 5Download the 320 MP3 — Save the resulting
.mp3. Tags and cover art from the WAV are written into ID3v2.3. - Step 6Confirm it's true 320 CBR — Check the file's properties in any player or with a media inspector — bitrate should read 320 kbps. If you also want consistent loudness across an album, run each track through loudness-normalizer before converting.
320 kbps versus the lower options
Why 320 kbps is the pick for music masters, and what you give up by stepping down. Sizes are approximate per minute of stereo audio at constant bitrate.
| Option | FFmpeg -b:a | ~Size / min (stereo) | Trade-off vs 320 |
|---|---|---|---|
| 320 kbps · best | 320k | ~2.4 MB | Reference point — near-transparent for music |
| 256 kbps | 256k | ~1.9 MB | ~20% smaller; transparent to most ears, faint loss on dense mixes |
| 192 kbps · default | 192k | ~1.4 MB | ~40% smaller; fine for casual listening, audible on cymbals/reverb tails to trained ears |
| 128 kbps | 128k | ~0.94 MB | ~60% smaller; clearly not master quality, fine for spoken word |
| 64 kbps | 64k | ~0.47 MB | Voice-only; not for music |
What 320 CBR preserves and what it doesn't
The converter encodes at 320 kbps; it does not resample, remix, or re-master. These are the properties that pass through unchanged.
| Property | At 320 kbps | If you need to change it |
|---|---|---|
| Sample rate | Preserved (e.g. 44.1 or 48 kHz unchanged) | Use sample-rate-converter first |
| Channels | Preserved (stereo stays stereo) | Downmix before converting if you need mono |
| Tags / cover art | Copied to ID3v2.3 | Edit with id3-editor |
| Loudness | Encoded as-is from the WAV | Match album loudness with loudness-normalizer |
| Peaks above 0 dBFS (float WAV) | May clip on encode | Tame with true-peak-limiter |
Cookbook
320 kbps decisions for music workflows. The FFmpeg shown is what the browser engine runs; you only choose the bitrate.
Album track to download-quality 320 MP3
A mastered 44.1 kHz 16-bit stereo track exported as WAV, encoded at 320 kbps for a download store or your own library. Sample rate and tags pass through.
Source: 04_chorus_master.wav (44.1 kHz / 16-bit / stereo)
Option: 320 kbps · best
Engine runs:
ffmpeg -i 04_chorus_master.wav -c:a libmp3lame -b:a 320k \
-map_metadata 0 -id3v2_version 3 04_chorus_master.mp3
Result: 04_chorus_master.mp3 (320 kbps CBR, 44.1 kHz stereo)Keeping the album's loudness consistent first
If different tracks were mastered at different loudness, normalize them before converting so the 320 MP3s play at a consistent level across the album.
Per track:
1. loudness-normalizer (/audio-tools/loudness-normalizer)
-> EBU R128 to -14 LUFS (streaming target)
2. wav-to-mp3 -> 320 kbps · best
Result: an album of 320 MP3s at matched loudness.24-bit master to 320 MP3 (with peak safety)
A 24-bit float master can have inter-sample peaks above 0 dBFS that clip when encoded. Run a true-peak limiter first, then encode at 320.
1. true-peak-limiter (/audio-tools/true-peak-limiter)
ceiling -1.0 dBTP
2. wav-to-mp3 -> 320 kbps
Engine runs (step 2):
ffmpeg -i master_limited.wav -c:a libmp3lame -b:a 320k \
-map_metadata 0 -id3v2_version 3 master_limited.mp3Why not just use FLAC?
If you truly want lossless, FLAC is the answer, not 320 MP3. But for a portable, universally playable file at the highest practical quality, 320 CBR MP3 wins on compatibility. Choose per use.
Goal -> tool: Lossless archive -> wav-to-flac (/audio-tools/wav-to-flac) Universal high-Q -> wav-to-mp3 @ 320 kbps (this tool) FLAC is smaller-than-WAV and lossless but not all players/car-stereos support it; 320 MP3 plays everywhere.
320 vs 256 size budget for a release
If you're shipping a full album as a download bundle, 320 versus 256 is a real size difference. 256 is transparent to most listeners; 320 is the safe choice if storage isn't tight.
12-track album, ~45 min total: @ 320 kbps -> ~108 MB bundle @ 256 kbps -> ~86 MB bundle Difference: ~22 MB. For a download store, 320 is standard; for bandwidth-tight delivery, 256 is a defensible step down.
Edge cases and what actually happens
You expected VBR V0 as 'highest quality'
By designSome encoders treat VBR V0 as the top tier. This tool offers CBR only, and 320 kbps is its highest setting. 320 CBR is a hair larger than V0 on average but is the most compatible high-quality MP3 — there is no V0/VBR mode here.
Master WAV exceeds your tier's size or duration limit
BlockedFree tier caps at 50 MB / 30 minutes per file; Pro at 200 MB / 120 minutes; Pro-media and Developer at 100 GB / unlimited. A long high-rate WAV can exceed the byte limit quickly. Upgrade or split the file before converting.
Float master clips when encoded at 320
Quality caution32-bit float WAVs can hold peaks above 0 dBFS that survive in the file but clip on MP3 encode. The 320 MP3 will still be created but may distort on the loudest moments. Limit true peaks first with true-peak-limiter.
Source is a 96 kHz high-res WAV
Sample rate preserved320 kbps at 96 kHz is preserved as-is, but a 96 kHz MP3 is unusual and some players reject it. For a release, resample to 44.1 or 48 kHz with sample-rate-converter before the 320 encode.
The WAV was decoded from a lossy source
Quality cautionEncoding a lossy-origin WAV to 320 MP3 does not restore fidelity it never had, and adds a second lossy pass. 320 minimizes added artifacts, but the ceiling is set by the original source. Use a true lossless master for best results.
320 file is bigger than expected
Expected320 CBR is the largest of the five bitrates — about 2.4 MB per stereo minute. For a 45-minute mix that's roughly 108 MB. If you need it smaller without dropping below 'good music quality', 256 kbps is the next step; for a hard size cap use audio-compressor.
Cover art looks missing in some players
PreservedArt is written as an ID3v2.3 attached_pic. Most players read it, but a few mobile apps cache thumbnails aggressively and show the old one. The art is in the file — verify with a desktop tagger or id3-editor.
Multichannel master dropped in
Channels preservedChannel layout passes through, so a surround master would produce a multichannel MP3 that many players mishandle. For a 320 stereo release, downmix to stereo before converting.
Engine bundle didn't load
Load errorFFmpeg's WebAssembly downloads on first use. If blocked or offline before caching, the encode can't run. Reconnect and reload; after the first load it works offline.
Encode is slow on a very long track
ExpectedWebAssembly runs on the CPU, so a 15-minute master at 320 takes longer than a 3-minute single. It still completes locally with no upload; just give it time on long files or older machines.
Frequently asked questions
Is 320 kbps really the best quality this tool offers?
Yes. The five options are 320, 256, 192, 128, and 64 kbps, all constant bitrate via libmp3lame. 320 kbps is the top and the standard for download-quality music. There is no higher CBR and no VBR V0 mode.
Will a 320 MP3 sound identical to my WAV?
Effectively yes for most listeners on most material — 320 CBR is near-transparent. It is still lossy, so a few percent of inaudible data is discarded. For a truly identical (lossless) copy, use wav-to-flac instead.
Does encoding at 320 upload my master?
No. The encode runs in your browser via FFmpeg WebAssembly. Your master WAV never leaves your machine — important when the file is unreleased work.
Does 320 change my sample rate?
No. Bitrate (kbps of compressed data) and sample rate (samples per second) are independent. The converter preserves the source sample rate; only the bitrate is set to 320. Use sample-rate-converter to change sample rate.
Should I use 320 CBR or VBR for a music release?
This tool only does CBR, and 320 CBR is the most universally compatible high-quality MP3 — a safe default for any release or hardware player. If your distributor specifically requires VBR you'd need a different encoder, but for self-hosting and most stores, 320 CBR is fine.
Are tags and album art kept at 320?
Yes — bitrate doesn't affect metadata. Tags and embedded cover art copy into ID3v2.3 regardless of bitrate. Edit them afterward with id3-editor.
How big will a 320 MP3 be?
About 2.4 MB per stereo minute, so roughly 14-15 MB for a 6-minute track and ~108 MB for a 45-minute album. That's the cost of the highest quality; step down to 256 kbps to shave roughly 20%.
Can I batch a whole album to 320 at once?
The WAV-to-MP3 page is single-file. Convert each track one at a time. Pro tiers support batch limits across audio tools, but this page processes one WAV per run. To stitch tracks into one file use audio-merger.
My 320 file clips on loud parts — why?
Likely a 32-bit float WAV with peaks above 0 dBFS that clip on encode. Run true-peak-limiter with a ceiling around -1 dBTP first, then encode at 320. The limiter prevents the inter-sample overs that MP3 encoding can expose.
Is 320 overkill for spoken word?
Yes — for voice, 128 or even 64 kbps is plenty and far smaller. 320 is for music and dense material. If your WAV is a podcast or audiobook, the convert-wav-to-mp3-for-podcast-hosting guide covers the right rates.
What's the largest WAV I can encode at 320?
Limited by tier, not bitrate: Free 50 MB / 30 min, Pro 200 MB / 120 min, Pro-media and Developer 100 GB / unlimited. The 320 setting doesn't change the input limit — it changes the output size.
Can I tell the bitrate is genuinely 320?
Yes — open the MP3's file info in any player or media inspector; the bitrate field should read 320 kbps and the mode CBR. The engine runs -b:a 320k, a constant-bitrate request, so every frame targets 320 kbps.
Privacy first
Every JAD Audio tool runs entirely in your browser via FFmpeg (WebAssembly) and RNNoise. Your audio files never leave your device — verified by zero outbound network requests during processing.