LAME ACM MP3 Codec is a free Audio Compression Manager driver that puts the LAME MP3 encoder into the audio compression list of VirtualDub and other 32-bit Windows software, frozen at version 3.99.5 since 2012.
MP3 is missing from the audio compression list in VirtualDub, and every other option in that dropdown produces files far larger than they need to be.
Windows has never shipped an MP3 encoder for that list, only a decoder, which is why the option was never there in the first place.
LAME ACM MP3 Codec is the driver that adds it.
What This Actually Does
ACM stands for Audio Compression Manager, the part of Windows that supplies the list of audio formats you see when a program asks how to compress a soundtrack. Windows populates that list from a small set of registered drivers, and until you add one for MP3, MP3 is simply not an option.
This package registers one, under the name msacm.lameacm, wrapping the same LAME MP3 Encoder that most Windows audio software already uses internally.
Once it is installed, MP3 appears wherever ACM formats are offered. In VirtualDub that is Audio, then Full processing mode, then Compression, and the entry reads Lame ACM MP3 Codec. Older capture tools, screen recorders and DivX-era AVI workflows read the same list.
What it is not. This is an encoder, not a decoder. If MP3 files will not play, the missing piece is the MPEG Layer-3 decoder instead.
Installing It Without the INF Headache
The download here is an installer that copies the driver into place, registers it and adds a normal entry to Add or Remove Programs. It is built and maintained by X Codec Pack, and it takes a couple of clicks.
That is worth explaining, because the old method is the reason this codec has a reputation for not working.
For years the only way to install it was to unzip the package, right-click LameACM.inf and choose Install. On 32-bit Windows that worked. On 64-bit Windows it appears to work, reports success, and leaves you with a compression list that still has no MP3 in it.
The reason is that ACM is a 32-bit interface and the driver is a 32-bit file. Right-clicking the INF hands it to the 64-bit half of Windows, which files the registration where no 32-bit program looks for it. Nothing warns you.
If you already tried the right-click method and nothing happened, you did not do it wrong. That route has been broken on 64-bit Windows for as long as 64-bit Windows has existed. Run the installer instead and it will land in the right place.
If you would rather do it by hand, open a Command Prompt as administrator, change to the SysWOW64 folder inside your Windows directory, and run setupapi's install section against the INF from there. Doing it from that folder is the whole trick, and it is what the text file inside the original archive has always described.
The WAV Header Catch
This one surprises people, so it is worth knowing before you encode anything important.
When an ACM codec writes audio into a video container such as AVI, the result is exactly right and every player handles it. When a program uses ACM to save a standalone audio file, it writes an MP3 stream wrapped in a WAV header, and a fair number of players and phones refuse to recognise the result even though the audio inside is perfectly good.
So use this for soundtracks inside video files, which is what it is for. For standalone MP3s, a normal encoder gives you a clean file with no wrapper.
The easy fix. If you only want MP3 files rather than MP3 audio inside a video, skip ACM entirely and use X Audio Converter for something quick, or LameXP for batches. Neither produces the wrapper problem.
Why It Is Still 3.99.5 When LAME Is on 4.0
The build here dates from February 2012 and wraps LAME 3.99.5, while the encoder itself reached 4.0 in July 2026. That gap is real and there is no newer ACM build anywhere, from anyone.
It matters less than it looks, for two reasons.
The first is that MP3 encoding quality has not moved. LAME 4.0 was a security and housekeeping release, and its own release notes are clear that encoded output is unchanged from 3.100. Files this codec produces sound the same as files a current build produces.
The second is that 4.0's two security fixes land in parts of LAME this codec does not contain. One is in the old Blade-compatible library that legacy applications load, and the other is in the command-line tool's AIFF file reader. The ACM driver links the encoding library directly and includes neither.
That is not a clean bill of health, because nobody has audited a 2012 binary. It does mean the specific problems 4.0 fixed are not problems here.
Who Should Look Elsewhere
Three tells, each of which you can check right now without installing anything.
- Your video editor is 64-bit. ACM is a 32-bit interface with no 64-bit equivalent, so a 64-bit application will never list this codec no matter how it is installed - use the 32-bit build of your editor, or encode the audio separately.
- You wanted MP3 files, not MP3 inside a video. That is the WAV header problem above, and a normal encoder avoids it entirely.
- Your program asks for a DirectShow filter or for lame_enc.dll. Different interfaces - the LAME DirectShow Filter covers the first, and the step-by-step LAME install guide for Windows covers the second.
If none of that applies and you simply want MP3 files with a window rather than a command prompt, winLAME and RazorLame are the classic front-ends.
Audacity bundles its own MP3 encoder and needs nothing from this page at all, and for a single file with nothing to install there is the site's online audio converter.
The Settings Worth Changing
Whatever host you use, the compression dialog has a Configure button next to the codec, and the defaults are conservative. Out of the box it runs average bitrate between 88 and 160 kbps in joint stereo, which is fine for speech and thin for music.
For a music soundtrack, raise the range so the average lands nearer 190 kbps. For voice, the defaults are already about right and there is little to gain.
The best LAME settings guide goes through the presets case by case, and the WAV to MP3 quality guide covers the same ground for standalone files.
Where This Sits Next to the Rest
MP3 earns its place in an AVI through sheer compatibility, and that is still the reason to reach for it. Where compatibility is not the constraint, Opus sounds better at low bitrates and FLAC keeps everything for archiving.
For a tool that handles every format at once rather than hooking into Windows, the FFmpeg Audio Encoder covers the lot. Once the files exist, Mp3tag sorts out the artist and album fields.
Other machines want other builds. Windows on ARM devices run better on LAME for Windows ARM64, and Mac users want LAME for Mac OS.
For AC3 and DTS soundtracks rather than MP3, AC3 Filter is the equivalent piece. The rest of the current builds sit in the Audio Encoders section.
Quick questions
Is LAME ACM MP3 Codec free?
Yes, and for commercial work too. LAME is open source under the LGPL and MP3 patent licensing ended in 2017, so there is no fee for encoding either way.
Why does MP3 still not appear after installing it?
Two usual causes. The program was already open when you installed, and Windows only reads the codec list when a program starts, so close it and reopen it. Or the program is 64-bit, in which case it will never list an ACM codec at all.
Does it work on Windows 10 and 11?
Yes. ACM is old but it has never been removed, and the driver registers and runs normally on current Windows. The catch has always been the installation route rather than compatibility.
Is there a 64-bit version?
No, and there will not be. ACM is a 32-bit interface with no 64-bit counterpart, so the codec only ever appears in 32-bit applications. Use the 32-bit build of your editor, or encode the audio separately with a normal encoder.
Why do the MP3s it makes not play on my phone?
Because a standalone file saved through ACM carries a WAV header that some players reject. Audio inside a video file is unaffected. For standalone MP3s, use a normal encoder instead.
Should I wait for a version based on LAME 4.0?
There is nothing to wait for. No 4.0-based ACM build exists, and 4.0 changed security and build tooling rather than sound quality, so this codec encodes identically to a current one.
More encoders, decoders and format tools sit in the Audio Codecs section.
Download LAME ACM MP3 Codec 3.99.5 and see how it handles your files, or tell us how you got on if you have used it before.
using this for bitRipper
