Download current and archived LAME MP3 encoder builds for Windows, including lame.exe and libmp3lame.dll. Current MinGW packages also include a standard Blade-compatible lame_enc.dll. The current LAME 4.0 package set below includes this site’s separate cVBR and cVBRb development builds. Independently compiled builds from the official LAME 4.0 branch are available on the official-branch LAME 4.0 page.
Use the Windows builds below for command-line encoding, Exact Audio Copy integration, batch work and current cVBRb features.
Use the Online MP3 Encoder for a simple audio-focused browser workflow. Use the Video & Audio to MP3 Converter when you want to extract audio from video, work with a wider range of media files, or convert long files with memory-managed processing. Use the EAC Guide if you are ripping CDs. Use Command Examples if you want copy-and-paste LAME commands, read FFmpeg MP3 encoding with LAME if you use libmp3lame, use the FFmpeg LAME Shim when a host expects ffmpeg.exe but you want native LAME encoding, and use the Best LAME Settings guide if you want a direct recommendation, or the MP3 V0 vs 320 kbps Bitrate Guide if you are comparing VBR, CBR, V0, V2, 192 kbps or 320 kbps.
For the technical behaviour behind strict minimum VBR and bitrate boost, see cVBR explained: VBR vs cVBR vs cVBRb.
Have a supported NVIDIA GPU? The final card under Downloads by build type is a specialist CUDA x64 release, with full compatibility and usage notes on the LAME CUDA page.
Browse packages by LAME version without mixing release numbers into every build title. This keeps Visual Studio SIMD and MinGW Solid State variants easier to compare as more package sets are published.
Choose the current Visual Studio SIMD builds for the main performance line: optimized CPU runtime paths, cVBRb controls, optional lame.ini defaults and direct FLAC input through libFLAC.dll. OpenMP-assisted VBR work is capped at four threads. Choose MinGW Solid State builds for the compatibility-focused package with runtime DLLs and a standard Blade-compatible lame_enc.dll included.
For the simplest EAC installation, use the setup utility. It detects the system and installs the appropriate LAME build. Supported systems receive the Visual Studio performance build, including direct FLAC input support; compatibility builds remain available for older targets. The installer can also open the personalized EAC setup guide when finished.
Stable 64-bit Visual Studio SIMD performance build with cVBRb, optional lame.ini defaults and automatic FLAC input when libFLAC.dll is present.
Enhancements: SIMD · OpenMP (max 4 threads) · FLAC input · lame.ini
Stable 32-bit Visual Studio SIMD performance build with cVBRb, optional lame.ini defaults and automatic FLAC input when the x86 libFLAC.dll is present.
Enhancements: SIMD · OpenMP (max 4 threads) · FLAC input · lame.ini
High-compatibility 64-bit MinGW Solid State package. It includes lame.exe and libmp3lame.dll with the cVBRb feature set, plus a standard Blade-compatible lame_enc.dll for older applications.
High-compatibility 32-bit MinGW Solid State package. It includes lame.exe and libmp3lame.dll with the cVBRb feature set, plus a standard Blade-compatible lame_enc.dll for older applications.
A specialist Visual Studio build that accelerates selected psychoacoustic and bitrate-decision work on supported NVIDIA GPUs while retaining cVBRb controls and final LAME MP3 generation.
Recommended for: selected GeForce GTX 10/16 and RTX 20/30/40/50 series cards, plus compatible NVIDIA professional GPUs.
Most users should choose a standard CPU build. A compatible NVIDIA driver is required for CUDA encoding.
The current Visual Studio packages are the stable SIMD cVBRb performance builds. They add optional lame.ini defaults and direct FLAC input through libFLAC.dll while retaining the stricter bitrate-control and bitrate-boost features.
Shared VS build features include ABR boost support at level 1, SSE2 baseline with an AVX2 runtime CPU path where supported, and OpenMP-assisted VBR quantizer work capped at four threads.
The optional lame.ini file can supply persistent defaults for host applications that expose only a limited LAME command line; explicit command-line options still win. FLAC input is automatic when the bundled architecture-matched libFLAC.dll is beside lame.exe. MinGW packages remain separate as the Solid State compatibility line.
These notes describe branch behaviour and user-facing options. The shared Visual Studio enhancements are grouped above so the individual package listings can focus on what differs between the Visual Studio SIMD builds and the MinGW Solid State compatibility builds.
The --vbr-min-strict option turns the bitrate supplied with -b into a hard floor. Unlike LAME -F, frames should not be encoded below the configured minimum.
The --vbr-max <bitrate> option can set a maximum allowed bitrate for cVBR mode, useful for streaming, device compatibility and controlled distribution targets.
The cVBRb branch adds --bitrate-boost[=n] for demanding audio changes. Levels 1, 2 and 3 map to light, medium and aggressive boost behaviour.
Standard LAME options remain supported. These examples highlight the additional options included in this fork. If you only need a quick browser-based conversion, use the Online MP3 Encoder. If you rip CDs with Exact Audio Copy, see the EAC LAME guide. For more examples, see the command-line examples.
lame -V0 -b 192 --vbr-min-strict --vbr-max 320 input.wav output.mp3Constrains VBR output between 192 kbps and 320 kbps.
lame -V0 -b 192 --vbr-min-strict --bitrate-boost=2 input.wav output.mp3Enables medium bitrate boost in the cVBRb branch.
lame --abr 192 --bitrate-boost input.wav output.mp3Bitrate boost also works in ABR mode, limited to level 1.
lame --decode input.mp3 output.wavThe encoder EXE is the primary command-line tool and can be used directly for normal encoding. The MinGW bundles include separate DLL interfaces: libmp3lame.dll for compatible applications and lame_enc.dll for older Blade-compatible hosts. The latter uses standard LAME and does not include the cVBRb presets or SIMD assembly optimisations.
New users often expect an installer or a desktop app. These packages are command line encoder builds, so the EXE is normally run with input and output filenames rather than opened by double-clicking. Prefer not to use the command line? Open the Online MP3 Encoder.
Unzip one package, place a WAV file in the same folder, open PowerShell in that folder and run a command like this:
.\lame.exe input.wav output.mp3Use the actual EXE name from your download. If the command succeeds, the new MP3 file appears in the same folder.
A command line encoder is a tool rather than a full music app. It is designed to be called with options, used in scripts, or used by other software that needs MP3 encoding.
lame.exe is a Windows command line encoder. It is a program you run from Command Prompt, PowerShell, a batch file or another audio application to convert supported audio input into an MP3 file.
These packages are portable encoder builds. There is no setup wizard. You unzip the package and run the encoder EXE directly from Command Prompt or PowerShell. The EXE is the main tool. The MinGW bundles also include libmp3lame.dll, decode-support DLLs and a standard Blade-compatible lame_enc.dll for older host applications.
Open PowerShell or Command Prompt in the folder containing the EXE and run a command such as lame.exe input.wav output.mp3. Replace the EXE name with the build you downloaded and replace the filenames with your own audio file names.
A WAV file is the easiest starting point. The current Visual Studio builds can also read FLAC files directly when libFLAC.dll is beside lame.exe. MP3 output will be written to the filename you choose.
Usually no. If you double-click a command line encoder, a console window may appear and close quickly because no input or output file was supplied. Run it from PowerShell or Command Prompt so you can provide filenames and options.
Most users on modern Windows should start with the x64 Visual Studio SIMD build. Use x86 for 32-bit systems. The Visual Studio packages are the current performance builds and include libFLAC.dll for direct FLAC input; MinGW Solid State builds remain the high-compatibility line.
The Visual Studio builds can read an optional lame.ini beside lame.exe. It supplies default LAME options for applications that do not expose every encoder setting. Explicit command-line options still take precedence, and normal behaviour is unchanged when the file is absent.
Yes, in the current Visual Studio builds. If the bundled libFLAC.dll is beside lame.exe, a FLAC file can be used directly as input. The MinGW Solid State packages do not include this FLAC input extension.
cVBR is a constrained VBR branch that can keep variable bitrate encoding within a stricter range. cVBRb adds bitrate boost behaviour for more demanding audio changes. Standard LAME options still remain available.
For normal command-line encoding, use lame.exe directly. In the MinGW bundles, libmp3lame.dll supports compatible applications and the included lame_enc.dll provides the older standard Blade-compatible interface. Keep libmpg123-0.dll and libiconv-2.dll with the bundle where required.
No. The MinGW bundle includes a standard Blade-compatible lame_enc.dll for older applications, but that DLL uses the standard LAME encoder without the additional cVBR/cVBRb presets or SIMD assembly optimisations. Use lame.exe or libmp3lame.dll from the same bundle for this site's additional bitrate-control features.
The VirusTotal link lets you view an external scan report for the ZIP file SHA-256. It is provided as a verification aid, not a guarantee. Always compare the SHA-256 on this page with the file you downloaded, and remember that new command-line tools or DLLs can sometimes produce false positives.
No. Checksums are provided as an advanced detail for users who want to manually verify a downloaded ZIP file. Most users can simply download the package that matches their Windows system and follow the usage example.
Use this section to compare included files, branch features and technical package information. All current cards now identify the cVBRb branch. Visual Studio packages list SIMD, four-thread OpenMP, lame.ini and FLAC-input enhancements, while MinGW Solid State packages identify the included standard lame_enc.dll. cVBRb and SIMD features apply to lame.exe and libmp3lame.dll, not to lame_enc.dll.
Recommended for modern 64-bit Windows systems. This is the main performance build and includes direct FLAC input support.
lame-4.0-cVBRb-20260926-bundle-VS-x64.zip8e68cb6e12cb0d6ad230fb4bff8b8ca52c7397180c2f013432f1ee91e1615cc5VirusTotal is an external verification aid. Compare the SHA-256 above with your downloaded ZIP. A clean report does not guarantee safety, and a detection can be a false positive.
Use this for 32-bit Windows compatibility while retaining the current Visual Studio feature set and direct FLAC input support.
lame-4.0-cVBRb-20260926-bundle-VS-x86.zip0e2d03933e3711bd20c565cbfcfb4bd0cdbec4c15ed22800bd6bfce2e4a004fbVirusTotal is an external verification aid. Compare the SHA-256 above with your downloaded ZIP. A clean report does not guarantee safety, and a detection can be a false positive.
Use this when compatibility and a simple predictable encoder path matter more than peak SIMD performance.
lame-4.0-cVBRb-20260801-bundle-x64.zipc735a59ced118737cbc968183ef39d3647e88f8bd24e3fdeccae5a55a414a26bVirusTotal is an external verification aid. Compare the SHA-256 above with your downloaded ZIP. A clean report does not guarantee safety, and a detection can be a false positive.
Use this for older 32-bit Windows compatibility and the simplest supported MinGW release path.
lame-4.0-cVBRb-20260801-bundle-x86.zip11d8676561ab71f9a369fcec74fbed6b25156ef21183e68c6bc838d90c454016VirusTotal is an external verification aid. Compare the SHA-256 above with your downloaded ZIP. A clean report does not guarantee safety, and a detection can be a false positive.
The original LAME project built its reputation through encoder quality, speed, psychoacoustic tuning, VBR improvements and open collaboration. This site presents an independent build branch with its own release notes and Windows packages.
LAME began around mid-1998 as work around an earlier MP3 encoder, then grew through open-source collaboration into a respected encoder project.
The project moved beyond patch work and replaced the remaining reference source, becoming a complete LGPL MP3 encoder.
Development focused on psychoacoustics, noise shaping, VBR behaviour, presets, speed and practical listening quality.
The current Visual Studio packages add optional lame.ini defaults and direct FLAC input through libFLAC.dll while retaining the cVBRb performance work.
See practical tables for CBR, ABR, VBR, cVBR and cVBRb showing the average bitrate, approximate file size per minute and high-frequency reach produced by the current encoder.
Most visitors are looking for the Windows encoder download or the browser encoder.