LAME MP3 Encoder for Windows

LAME MP3 Encoder builds for Windows

Download LAME 4.0 and Windows lame.exe binaries

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.

Where to start

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 quick browser-based conversion without installing anything. Use the EAC Guide if you are ripping CDs. Use Command Examples if you want copy-and-paste LAME commands, and the MP3 Bitrate Guide if you are choosing between VBR, CBR, V0, V2, 192 kbps or 320 kbps.

For the technical behaviour behind strict minimum VBR and bitrate boost, see cVBR explanation and measured comparison.

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.

Version groups

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.

Downloads by build type

Choose Visual Studio SIMD builds when you want optimized CPU runtime paths, multi-threaded encoder work and bitrate-boost options. The compact cards mark these as SSE2/AVX/Multi-thread. Choose MinGW Solid State builds for the compatibility-focused package with runtime DLLs and a standard Blade-compatible lame_enc.dll included. Use the version filter above as the catalogue grows.

Visual Studio SIMD x64

Featured
LAME 4.0

Performance-focused 64-bit Visual Studio SIMD build with cVBRb features, runtime SIMD path selection and OpenMP-assisted encoder work.

Enhancements: SSE2/AVX/Multi-thread

Version
LAME 4.0
Branch
cVBRb
Platform
Windows x64 / 64-bit
Compiler
Microsoft Visual Studio
Package
759.7 KB

Visual Studio SIMD x86

Featured
LAME 4.0

32-bit Visual Studio SIMD build for users who want the same SIMD mode structure as the x64 performance build on 32-bit Windows targets.

Enhancements: SSE2/AVX/Multi-thread

Version
LAME 4.0
Branch
cVBRb
Platform
Windows x86 / 32-bit
Compiler
Microsoft Visual Studio
Package
672.43 KB

MinGW Solid State x64

Compatible
LAME 4.0

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.

Version
LAME 4.0
Branch
cVBRb
Platform
Windows x64 / 64-bit
Compiler
MinGW
Package
1.77 MB

MinGW Solid State x86

Compatible
LAME 4.0

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.

Version
LAME 4.0
Branch
cVBRb
Platform
Windows x86 / 32-bit
Compiler
MinGW
Package
1.79 MB

LAME 4.0 cVBRb CUDA x64

Specialist release
NVIDIA CUDA · Windows x64

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.

Version
LAME 4.0 cVBRb
Branch
cVBRb CUDA
Platform
Windows x64 / 64-bit
Compiler
Visual Studio + CUDA 12.9
Package
lame.exe + cuFFT + mpg123

Most users should choose a standard CPU build. A compatible NVIDIA driver is required for CUDA encoding.

Visual Studio optimized builds

The Visual Studio packages are optimized SIMD cVBRb Windows builds with newer performance paths, stricter bitrate-control options and bitrate-boost support.

Shared VS build features include ABR boost support at level 1, SSE2 baseline with an AVX2 runtime CPU path where supported, and OpenMP-assisted multi-threading for selected quantization/Huffman work.

In plain terms, OpenMP is used to let some heavier encoding work use more than one CPU thread. Individual packages may still differ by architecture, branch feature set, executable name and command-line options. MinGW packages remain separate because they now serve as the Solid State compatibility line while Visual Studio carries the SIMD performance line.

Build notes and branch comparison

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.

Constrained VBR

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.

Optional VBR ceiling

The --vbr-max <bitrate> option can set a maximum allowed bitrate for cVBR mode, useful for streaming, device compatibility and controlled distribution targets.

cVBRb bitrate boost

The cVBRb branch adds --bitrate-boost[=n] for demanding audio changes. Levels 1, 2 and 3 map to light, medium and aggressive boost behaviour.

Usage examples

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.

Strict cVBR range

lame -V0 -b 192 --vbr-min-strict --vbr-max 320 input.wav output.mp3

Constrains VBR output between 192 kbps and 320 kbps.

cVBRb bitrate boost

lame -V0 -b 192 --vbr-min-strict --bitrate-boost=2 input.wav output.mp3

Enables medium bitrate boost in the cVBRb branch.

ABR boost level 1

lame --abr 192 --bitrate-boost input.wav output.mp3

Bitrate boost also works in ABR mode, limited to level 1.

Decode MP3 to WAV

lame --decode input.mp3 output.wav

The 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.

FAQ: using encoder EXE files

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.

A simple first encode

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.mp3

Use the actual EXE name from your download. If the command succeeds, the new MP3 file appears in the same folder.

Why it feels different

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.

What is lame.exe?

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.

Why does the download contain an EXE instead of a normal installer?

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.

How do I use the encoder if I am new to command line tools?

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.

What kind of input file should I start with?

A WAV file is the easiest starting point. Put the WAV file in the same folder as the encoder, then use it as the input file in the command. MP3 output will be written to the filename you choose.

Do I need to double-click the EXE?

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.

Which Windows build should I choose?

Most users on modern Windows should start with an x64 build. Use an x86 build only for older 32-bit systems. Visual Studio SIMD builds are the optimized performance packages, while MinGW Solid State builds are the high-compatibility packages that include the required runtime DLLs.

What are cVBR and cVBRb?

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.

What should I do with the DLL files in the MinGW Solid State packages?

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.

Does the included lame_enc.dll support cVBR and cVBRb?

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.

What does the VirusTotal link mean?

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.

Do I need to understand checksums to use the download?

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.

Advanced package details

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 their SIMD and multi-threaded enhancements, while MinGW Solid State packages also identify the included standard lame_enc.dll. cVBRb and SIMD features apply to lame.exe and libmp3lame.dll, not to lame_enc.dll.

Visual Studio SIMD x64

Use this when you want the fastest 64-bit build and your CPU supports the newer SIMD paths.

Download

Included files

  • lame.exe
  • libmp3lame.dll
  • README.txt

Main features

  • cVBR strict bitrate floor
  • Optional --vbr-max ceiling
  • --bitrate-boost levels 1–3
  • mpg123 decode support integrated into lame.exe
  • ABR boost support at level 1
  • SSE2 baseline with an AVX2 runtime CPU path
  • OpenMP-assisted multi-threading for selected quantization/Huffman work
Version
LAME 4.0
Executable
lame.exe
ZIP filename
lame-4.0-cVBRb-20260715-bundle-VS-x64.zip
Checksums and VirusTotal details
SHA-256
d233004acef059b0ba72f600fbb3d33a4a2fd2899c2342c725e55ca99ef8d930
VirusTotal
VirusTotal: 0 detections
Checked 2026-08-05T22:49:38+00:00

VirusTotal 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.

Visual Studio SIMD x86

Use this for 32-bit compatibility while keeping the same SIMD-capable feature line as the x64 Visual Studio build.

Download

Included files

  • lame.exe
  • libmp3lame.dll
  • README.txt

Main features

  • cVBR strict bitrate floor
  • Optional --vbr-max ceiling
  • --bitrate-boost levels 1–3
  • mpg123 decode support integrated into lame.exe
  • ABR boost support at level 1
  • SSE2 baseline with an AVX2 runtime CPU path
  • OpenMP-assisted multi-threading for selected quantization/Huffman work
Version
LAME 4.0
Executable
lame.exe
ZIP filename
lame-4.0-cVBRb-20260715-bundle-VS-x86.zip
Checksums and VirusTotal details
SHA-256
69f40eec02348fa731419eed3386ff2bf7a12414b3b0f2f65ebed8f3ae9efe1d
VirusTotal
VirusTotal: 0 detections
Checked 2026-08-05T23:38:13+00:00

VirusTotal 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.

MinGW Solid State x64

Use this when compatibility and a simple predictable encoder path matter more than peak SIMD performance.

Download

Included files

  • lame.exe
  • lame_enc.dll
  • libmp3lame.dll
  • libmpg123-0.dll
  • libiconv-2.dll
  • README.txt

Main features

  • cVBR strict bitrate floor in lame.exe/libmp3lame.dll
  • Optional --vbr-max ceiling
  • --bitrate-boost levels 1–3
  • ABR boost support at level 1
  • Standard Blade-compatible lame_enc.dll
  • lame_enc.dll uses standard LAME without cVBRb or SIMD assembly
  • Portable Windows MinGW package
  • Dynamic mpg123 decode support
Version
LAME 4.0
Executable
lame.exe
ZIP filename
lame-4.0-cVBRb-20260801-bundle-x64.zip
Checksums and VirusTotal details
SHA-256
c735a59ced118737cbc968183ef39d3647e88f8bd24e3fdeccae5a55a414a26b

VirusTotal 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.

MinGW Solid State x86

Use this for older 32-bit Windows compatibility and the simplest supported MinGW release path.

Download

Included files

  • lame.exe
  • lame_enc.dll
  • libmp3lame.dll
  • libmpg123-0.dll
  • libiconv-2.dll
  • README.txt

Main features

  • cVBR strict bitrate floor in lame.exe/libmp3lame.dll
  • Optional --vbr-max ceiling
  • --bitrate-boost levels 1–3
  • ABR boost support at level 1
  • Standard Blade-compatible lame_enc.dll
  • lame_enc.dll uses standard LAME without cVBRb or SIMD assembly
  • Portable Windows MinGW package
  • Dynamic mpg123 decode support
Version
LAME 4.0
Executable
lame.exe
ZIP filename
lame-4.0-cVBRb-20260801-bundle-x86.zip
Checksums and VirusTotal details
SHA-256
11d8676561ab71f9a369fcec74fbed6b25156ef21183e68c6bc838d90c454016

VirusTotal 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.

Origins of this development branch

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.

1998

The LAME story begins

LAME began around mid-1998 as work around an earlier MP3 encoder, then grew through open-source collaboration into a respected encoder project.

2000

A complete encoder

The project moved beyond patch work and replaced the remaining reference source, becoming a complete LGPL MP3 encoder.

3.x era

Quality and tuning

Development focused on psychoacoustics, noise shaping, VBR behaviour, presets, speed and practical listening quality.

May 2026

LAME 4.0 development builds

Current packages are based on LAME 4.0 cVBR and cVBRb development.