Guides · updated October 22, 2026

Audacity WAV to MP3

Audacity gives you LAME options and batch macros. The browser gives you no install and no upload. Here is which one fits which job.

Tested: 22 October 2026 · Audacity 3.x MP3 export settings · Chrome 156 browser route

Short answer

Audacity can export WAV to MP3 with LAME, including constant, average and variable bitrate modes. It is the better tool when you need editing, normalization, noise removal or a batch macro. The browser converter is better for one file, no install and no project setup. Neither one uploads the audio.

Audacity’s MP3 export dialog

When you choose File → Export → Export as MP3, Audacity opens a dialog with:

Bit Rate Mode: Constant, Average or Variable.
Quality: the LAME quality/bitrate control, depending on the mode.
Channel Mode: Joint Stereo, Stereo, Mono, or a forced mix.
Metadata: ID3 tags.

Constant is predictable and matches the browser converter’s CBR output. Variable lets LAME spend more bits on complex passages and fewer on quiet ones; it can match CBR quality at a smaller average size. Average targets a bitrate while varying within the file.

If you just need a standard 192 or 320 kbps MP3, the defaults are fine. If you need a specific size or a VBR profile, Audacity exposes it.

Batch with a Macro

For a folder of WAVs:

Tools → Macros → New, name it WAV to MP3.
Insert → Export as MP3, set the bitrate and channel mode.
Save the macro.
Apply to Files, select the WAVs, choose an output folder.

This is the workflow the browser does not try to replace. The browser queue is sequential and visual; a Macro is unattended and repeatable.

When the browser is the better route

You have one file and do not want to open a project.
You are on a machine where you cannot install Audacity.
You want to see the source codec, duration and channels before converting.
You want to keep the audio in the tab and avoid a temporary project file.

The browser converter is single-file by design. It does not edit, normalize or apply effects. That is the trade: less power, less setup.

The source matters. A 24-bit/96 kHz WAV and a 16-bit/44.1 kHz WAV can both become 320 kbps MP3; the output is still lossy.
The bitrate ceiling is 320 kbps. No tool can write a 512 kbps MP3.
The WAV is the master. Keep it if you might edit again.
No upload is required. Audacity is local; the browser converter is local.

A practical recommendation

Use Audacity when the job includes editing, effects, loudness normalization, or a folder that must be processed the same way every week. Use the browser when the job is “make this one WAV an MP3 and move on”. Both are honest tools; neither is a quality upgrade over the other’s encoder.

FAQ

Does Audacity use LAME for MP3 export?

Yes. Audacity uses the LAME encoder for MP3. On modern builds the library is bundled; older builds may ask you to locate libmp3lame. The export dialog exposes bitrate mode, quality and channel mode.

Can Audacity batch convert WAV to MP3?

Yes, with a Macro. Tools → Macros → New, add the Export as MP3 command with the desired settings, save the macro, then Apply to Files and choose the WAVs. It is the right route for a large folder or a repeatable pipeline.

Is Audacity faster than the browser?

Native LAME in Audacity is usually faster than the browser's WebAssembly encoder, especially for long files. The browser avoids an install and gives you a visual check before converting.

Does Audacity upload my files?

No. Audacity is a desktop application; it reads and writes local files. Some optional online features exist, but a normal WAV-to-MP3 export is local.

Which is better for a podcast?

If you need noise removal, compression, normalization or a repeatable loudness chain, Audacity. If the file is already edited and you just need MP3, the browser is faster to open and has no project overhead.