Audacity's FFmpeg support is an optional library that Audacity is not allowed to ship with the program, which is why a fresh install can tell you it is missing even though nothing is broken. The manual gives the reason in one sentence, and it is a legal one rather than a technical one.
That single fact changes how you should approach this: you are not repairing a damaged installation, you are deciding whether you actually need an add-on.
What this actually means
Audacity's FAQ page on installing the library states it plainly:
"The optional FFmpeg library allows Audacity to import and export a much larger range of audio formats including M4A (AAC), AC3 and WMA and also to import audio from most video files.Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own websites."
Two things follow from that. First, the library is optional — Audacity ships with a working set of formats on its own. Second, the reason it is absent is software patents, so no amount of reinstalling Audacity will ever produce it. You get it separately or you work around it.
What Audacity handles without FFmpeg, per the Importing Audio page:
- Uncompressed: "most WAV and AIFF files including all PCM variants can be imported into Audacity"
- Compressed: "MP3, Ogg Vorbis, FLAC and MP2 can be imported into Audacity."
Worth knowing if you are comparing pages: the manual's FAQ: Opening and Saving Files lists the shipped compressed formats as "Ogg Vorbis, FLAC and MP2" — MP3 is not on that list, while the Importing Audio page includes it. Two official pages, two different lists, which is part of why the advice you find online contradicts itself.
The fastest fix: check whether you need FFmpeg at all
Three common reasons for landing here do not require the library.
1. You are trying to export MP3. You do not need FFmpeg for that, and on Windows and Mac you no longer need LAME either. The manual:
"The software patent on LAME encoding library has expired, so now the LAME library for MP3 export is built-in with Audacity for Windows and Mac. Linux users will still need to download and install the free and recommended LAME third-party encoder to export MP3 files from Audacity."
Keep that qualifier: Windows and Mac built-in, Linux still installs LAME. Most "first install LAME" tutorials you will find are describing an older state of affairs.
2. You are on a Mac importing M4A, MP4 or MOV. The FAQ adds an exception the Importing Audio page does not mention: "(on Mac only, Audacity can import unprotected M4A, MP4 and MOV files without FFmpeg)." Both conditions matter — Mac only, and unprotected.
3. You only want the audio out of a video file. That is the single most common reason people go hunting for the library, and it does not need Audacity at all if you are not editing:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs in your browser tab — the file is decoded locally and handed back, never uploaded. If you already have an M4A and just want a more portable file, M4A to MP3 does that same conversion directly. If Audacity is not the tool you are attached to, extracting audio in VLC is another route to the same result.
If you do want the library
Audacity's FAQ hands installation off to a separate site: "Please see Installing FFmpeg on the Audacity Support site for FFmpeg installation details."
That means version numbers, download links and click-by-click steps are not in the manual pages this article is built from, so this page will not invent them — check the official documentation for those. The version numbers floating around forum posts are exactly the kind of detail that goes stale silently, and installing a mismatched build is how people end up with a library Audacity acknowledges but cannot use.
Other causes, in order of likelihood
It installed, but your format still is not offered. The Custom FFmpeg Export page explains why: "The actual formats and codecs available in the lists depend entirely on the options with which your copy of FFmpeg has been compiled." Two people with "FFmpeg installed" can genuinely have different format lists.
The export produces a broken file rather than an error. The export formats page warns: "not all formats and codecs are compatible, and some exports might result in zero-byte or invalid files if FFmpeg does not support the combination chosen." A zero-byte output is a codec and container mismatch, not a missing library.
You expect export parity with import. Audacity states the ceiling directly: "FFmpeg can only export about two-thirds of the formats that it can import." The same page gives the diagnostic: "One way to test if there is a problem in the Audacity implementation of FFmpeg is to use a command-line version of FFmpeg separately to perform the same task. If it fails in FFmpeg, then Audacity has the same limitation."
Audacity keeps reaching for its own importer instead of FFmpeg. Which one goes first is a setting rather than a fixed rule: "The FFmpeg importer will always be tried first if "Attempt to use filter in OpenFile dialog first" in Extended Import Preferences is checked, otherwise the native importer will be tried first." And that setting does not apply everywhere — "If using File > Recent Files or dragging in audio files, "Attempt to use filter in OpenFile dialog first" has no effect; Audacity will always try first the default importer for the file type, unless a rule is set that asks for another importer to be tried first." That is why the same file can import fine through the menu and fail when you drag it in.
You are using (external program) instead of the library. That is a different mechanism with its own requirements. Typing just ffmpeg "only works on Windows and Linux, assuming LAME or FFmpeg are installed on the system in the standard location", and on Windows "this requires that you used the LAME or FFmpeg EXE installer and did not change the installation directory." For a copy you placed yourself, "the full path to the command-line program must be given. The path must be enclosed inside quotes if there are any spaces in the path." On Mac, the manual is blunt: "the shipped commands for "lame" and "ffmpeg" do not work, trying them will simply generate an error message."
The file is DRM-protected. FFmpeg covers formats "if the files are not DRM-protected to work only in particular software". For those, Audacity suggests burning to an audio CD in the licensed application and ripping back to WAV or AIFF.
How to tell it worked
You do not have to guess — Audacity exposes the library in places that simply are not there otherwise:
- The import filter. In the file type dropdown, "FFmpeg compatible files - this option is only available if you have installed the optional FFmpeg extension."
- The custom exporter. "The custom FFmpeg exporter is available if you have installed the optional FFmpeg library."
- AAC export. The AAC page notes "FFmpeg is required for AAC export but it is not shipped with Audacity", and the format entry is listed as "M4A(AAC) Files FFmpeg" in the Format dropdown.
If those appear, the library is wired in. One saving throw worth remembering: presets are stored in ffmpeg_presets.xml in the Audacity data directory, which on Windows is Users\<username>\AppData\Roaming\Audacity.
FAQ
Why can't Audacity just include FFmpeg? Because of patents. The manual says "Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own websites." It is a distribution restriction, not a bug in your install.
Do I need FFmpeg to export MP3 from Audacity? No. LAME "is built-in with Audacity for Windows and Mac". Linux users still install LAME separately. FFmpeg is for the other formats — M4A (AAC), AC3, WMA and audio from video files.
Which FFmpeg version should I install? Audacity's FAQ points that question at the Audacity Support site rather than answering it in the manual, so check the official documentation for the current requirement instead of copying a version number from a forum thread.
Can Audacity open a video file once FFmpeg is installed? It can take the audio. The wording is specific: FFmpeg "will also import audio from most video files or DVDs that are not DRM-protected." That is an audio import, not video editing.
My MP3 won't import — will FFmpeg help? Sometimes, and Audacity says so: for a malformed MP3, "The answer is: Import it with FFmpeg instead of importing with libmad." There is a documented cost, though — with FFmpeg handling MP3s, the "Artist" and "Year" tags are not imported.
More error walkthroughs are in the fix guides, and every browser-based converter is listed under Clapr tools. Facts on this page are quoted from Audacity's official manual at manual.audacityteam.org, checked 16 September 2026.
