updated
Aug 16, 2026
1MB
file size
47.8K
downloads
LAME for Mac is the free, open-source MP3 encoder used by Audacity, XLD and most Mac audio tools, and version 4.0 ships as a universal binary that runs natively on Apple Silicon, Intel and even PowerPC Macs.
LAME 4.0 landed on 11 July 2026, the first major release of the MP3 encoder since 3.100 in 2017.
The Mac package is a universal binary, so one download covers Apple Silicon, Intel and PowerPC machines and picks the right code path on its own.
Encoding quality is unchanged from 3.100, so this is a maintenance update rather than a reason to re-encode anything you already have.
What You Get in the Mac Download
The LAME project publishes source code only, so every ready-to-run Mac build comes from someone else compiling it. The one listed here is the SIMD-optimized build, which uses the vector instructions in your processor to encode faster than a plain compile.
On Apple Silicon that means the NEON instructions in the M-series chips, on Intel Macs it means SSE, and the PowerPC binary in the same archive uses AltiVec for G4 and G5 machines. The archive picks whichever binary suits the Mac it is running on.
What it contains is the command-line encoder itself, not a library or a plug-in. There is no installer, no icon and no window: you get a single executable that takes a file in and writes an MP3 out.
Who Actually Needs This Download
Most Mac users do not, and it is worth saying so plainly before you spend time on it.
Audacity for Mac has included MP3 export internally since version 3.2, so exporting an MP3 there needs nothing extra.
X Lossless Decoder also bundles its own LAME for CD ripping, and VLC for Mac converts to MP3 with its own built-in encoder.
Where this download earns its place is scripting and batch work: a shell script that walks a folder of WAV files, a cron job, a Make step in a podcast pipeline, or an older Audacity build that still asks you to supply the encoder yourself.
Running It the First Time on macOS
The binary is not notarized by Apple, so Gatekeeper will stop it on first launch. That is expected for a community-compiled command-line tool and there is a supported way through it.
-
Unzip the archive and move the
lamebinary somewhere permanent, such as a Tools folder in your home directory. -
Open Terminal, type
cdfollowed by a space, then drag the folder onto the window and press Return. -
Run
./lame --version. macOS will block it the first time. -
Open System Settings, then Privacy & Security, scroll to the security message about
lameand click Open Anyway. - Run the command again and confirm it prints the version. It will not ask again.
From there a normal encode looks like ./lame -V 2 song.wav song.mp3. To convert a whole folder, a one-line loop such as for f in *.wav; do ./lame -V 2 "$f" "${f%.wav}.mp3"; done does the job.
The Settings That Actually Matter
Bitrate is how much data per second the encoder spends on your audio, and higher usually means better sound and a bigger file. LAME can hold that number steady or let it rise and fall with the music.
For music, variable bitrate is almost always the right answer. -V 2 averages around 190 kbps and is the long-standing sweet spot, while -V 0 pushes to roughly 245 kbps for headroom you probably cannot hear.
For spoken word, -V 6 lands near 115 kbps and still sounds clean. Where a predictable file size matters, such as broadcast delivery, -b 192 is a sensible fixed-bitrate floor for music.
One quirk worth remembering.
With fixed and average bitrate modes, asking for the slowest quality settings -q0 through -q3 can make the result worse rather than better, thanks to an old tuning left over from a psychoacoustic model no longer in use. Use -q4 there instead. Variable bitrate is unaffected, and the issue is still open in 4.0.
The best LAME settings guide and the WAV to MP3 quality guide work through the presets case by case.
What Changed in 4.0
The jump from 3.101 to 4.0 is mostly about version numbering. Every MP3 LAME creates carries a small tag naming the encoder, with a fixed nine-byte slot for the version string, and once minor versions hit three digits that slot ran out of room for the letter marking an alpha, beta or final build. Going to 4.0 makes it fit again.
Two security fixes came with it. The more serious one closes a stack buffer overflow in the Blade-compatible encoder library, which is a Windows component and does not affect the Mac build, and the second removes an integer underflow in the AIFF header reader that could send the encoder into an endless loop on a malformed file.
The rest is housekeeping: it compiles cleanly with current Clang versions, a bug that wrote the wrong genre when combining UTF-8 ID3 tags with the genre option is fixed, and the shared library now exposes its UTF-8 tagging functions to other applications. The guide on why LAME is still relevant covers why an encoder this old still gets recommended.
Building a Mac Audio Workflow Around It
For CD collections, X Lossless Decoder is the macOS equivalent of the accurate Windows rippers, checking each rip against a shared database of verified extractions before encoding. It comes from the same developer as the optimized LAME build on this page.
If you would rather not touch Terminal for a single file, the site's online audio converter handles one-off conversions in the browser.
For tagging afterwards, Mp3tag has a macOS release on the App Store alongside its Windows version. If Audacity needs to handle formats beyond MP3, the FFmpeg for Audacity guide covers that side.
When Another Format Suits You Better
MP3 is still the format that plays everywhere: car stereos, old iPods, cheap Bluetooth speakers, rental-car head units. That universality is the whole reason to choose it in 2026.
When the file is staying inside your own ecosystem, Opus sounds clearly better at low bitrates and suits voice and podcasts, while FLAC keeps every bit of the original for archiving.
Apple Lossless is the natural choice if your library lives in Music and syncs to Apple devices. More macOS software sits in the Mac section, including IINA if you want a native player for the results.
Windows and Other Platforms
Windows users want the LAME MP3 Encoder for Windows page instead, which covers the 64-bit and 32-bit builds and the lame_enc.dll library that older Windows applications ask for.
If you want a graphical front-end on that side, LameXP and the foobar2000 Free Encoder Pack both wrap LAME in a normal window.
The rest of the current encoder builds are in the Audio Encoders section.
Quick questions
Do I need this if I use Audacity on my Mac?
No. Audacity 3.2 and newer includes MP3 export already. Only older versions ask you to supply the encoder separately.
Does it run natively on Apple Silicon?
Yes. The archive holds a universal binary with a native ARM64 build, so M-series Macs run it without Rosetta.
Is there a version with a window and buttons?
Not in this package, which is command-line only. On macOS the usual graphical route is X Lossless Decoder or Audacity, both of which include their own copy of LAME.
Why does macOS say the file cannot be opened?
The binary is not notarized by Apple, which is normal for community-compiled command-line tools. Approving it once under System Settings, Privacy & Security clears it for good.
Will 4.0 make my MP3s sound better than 3.100 did?
No. Encoded output is unchanged, so there is nothing to gain from re-encoding files you made with an earlier version.
Does it still work on a PowerPC Mac?
Yes. The same archive carries a build for G4 and G5 machines, which is unusual for anything released in 2026.
More encoders, decoders and format tools sit in the Audio Codecs section.
Download LAME 4.0 for Mac and see how it handles your files, or tell us how you got on if you have used it before.
