Includes cVBR and cVBRb Windows packages for creating MP3 files from WAV and other audio sources. lamemp3.co.uk is a focused branch project from Media Player Codec Pack, with practical build notes and command-line examples.
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.
This site is structured so each release can sit under its own version group, starting with the current LAME 3.101 beta 3 cVBR/cVBRb package set.
Browse packages by LAME version without mixing release numbers into every build title. This keeps Visual Studio, MinGW, cVBR and cVBRb variants easier to compare as more package sets are published.
Choose Visual Studio builds for SIMD/OpenMP and statically linked mpg123 decode support. Choose MinGW builds for portable Windows packages with runtime DLLs included. Use the version filter above as the catalogue grows.
Performance-focused 64-bit build with constrained VBR, bitrate boost, q4 patching, runtime SIMD paths, OpenMP acceleration and statically linked mpg123 decoding support.
32-bit Visual Studio cVBRb build for testing bitrate boost and constrained VBR on older or 32-bit Windows targets.
64-bit Visual Studio build focused on constrained VBR without bitrate boost, with q4 patching, OpenMP, runtime SIMD paths and static mpg123 decode support.
32-bit Visual Studio cVBR build with strict minimum VBR support, q4 patching, OpenMP acceleration and statically linked mpg123 decoding support.
Portable 64-bit MinGW cVBR build. It does not use OpenMP or AVX runtime paths and ships dynamic mpg123/iconv runtime DLLs.
Portable 32-bit MinGW cVBR build with dynamic mpg123 decode support and required libiconv/libmpg123 DLLs included in the package.
These notes are summarised from the README.txt files packaged inside the downloads.
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.
All featured packages include the q4-related patch from this fork. It is a bug fix for the affected VBR path, not a separate quality preset.
Standard LAME options remain supported. These examples highlight the additional options included in this fork.
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.wavVisual Studio packages link mpg123 statically; MinGW packages require the included matching DLLs.
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.
Unzip one package, place a WAV file in the same folder, open PowerShell in that folder and run a command like this:
.\lame_cVBR_x64.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, keep any included DLL files beside the EXE, and run the encoder directly when you need it.
Open PowerShell or Command Prompt in the folder containing the EXE and run a command such as lame_cVBR_x64.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. 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.
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 an x64 build. Use an x86 build only for older 32-bit systems. Visual Studio builds are aimed at performance features, while MinGW builds are portable packages that include required runtime DLLs.
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.
Keep the included DLL files in the same folder as the EXE. They are runtime support files used by that package, especially for decode support. Moving only the EXE may stop some features from working.
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. Keep the MinGW DLLs beside the executable for decode support.
Use this when you want the most capable 64-bit Visual Studio package and want to test bitrate boost behaviour.
lame_3.101b3_cVBRb_20260508_AVX_OpenMP_x64.zip18fd783da099c38e2ae39803641714622e7155628b747e812725a8c1a5cbbf62Use this for 32-bit compatibility while still testing the cVBRb bitrate boost branch.
lame_3.101b3_cVBRb_20260508_AVX_OpenMP.zip603f1250fba9285e69d9ec02c657ef053c194212a006318d45114f442905673aUse this when you want the main cVBR branch on modern 64-bit Windows without bitrate boost experiments.
lame_3.101b3_cVBR_20260508_AVX_OpenMP_x64.zip6859eab1dae66f643fec25c05c90bea460f89371baf0b5de7872ee3f977b3383Use this as the 32-bit counterpart to the main Visual Studio cVBR branch.
lame_3.101b3_cVBR_20260508_AVX_OpenMP.zip0afba213a5b391098aab9a3adbfcd5466df83a67a7696f7ac2d02c87161a9e36Use this for a portable 64-bit Windows build where maximum SIMD acceleration is less important than compatibility.
lame_3.101b3_cVBR_20260509_MinGW_x64.zip2a25b911d77b9225890d14d9ee81398d8ad9181ee3a1e5087dcdce302f52d641Use this for older 32-bit Windows compatibility and portable deployment.
lame_3.101b3_cVBR_20260509_MinGW.zip4acc434a1c759733b12e24ac8bf3ffcd41fcd9ffeaec287e1384386428f592c4