"Import Failed. This is likely to be caused by a malformed MP3" means Audacity's default MP3 importer found an error inside the file — not that the file is unplayable. The Audacity Manual is unusually direct about this: the same MP3 will very often play correctly in other software.
The fix is documented, and it works. What almost nobody repeats is the price the manual attaches to it, in the same page's own words.
What this error actually means
The Importing Audio page describes the message you are looking at:
"When importing an MP3 audio file you may see the following error message:" "Import FailedThis is likely to be caused by a malformed MP3."
The dedicated page, Opening malformed MP3 files, explains where it comes from:
"This indicates that Audacity's default MP3 importer ("libmad") detected an error in the file."
And it gives the history, which is the part that explains why this feels arbitrary:
"In old versions of Audacity, error checking was disabled in Audacity's MP3 importer. However, it was found that some malformed MP3s could cause serious problems, so error checking was enabled."
"In recent versions of Audacity the error checking has been toned down so that most MP3s will still import even if they contain small errors. Unfortunately a small number of malformed MP3s are sufficiently damaged that they still get caught by the error checking."
So the check is deliberately lenient and your file still tripped it. That does not make the file worthless, and the manual says so plainly:
"There are millions of "faulty" MP3 files downloaded from the Internet every day that will play correctly in other software, but not in Audacity."
Stop treating "it plays in VLC" as evidence that Audacity is broken. Two decoders, two tolerance levels. Audacity's is stricter by design.
The fastest fix: hand the file to a different importer
The manual's answer is one sentence:
"The answer is: Import it with FFmpeg instead of importing with libmad."
The quickest route is Workaround-1, verbatim:
"Workaround-1 - using the file type filter … In the File > Import > Audio dialog, select "FFmpeg compatible files" as the file type choice filter."
Two conditions attach to that. First, the option exists only once the optional library is installed — the Import Filtering and Importer Order page states that "FFmpeg compatible files - this option is only available if you have installed the optional FFmpeg extension." Second, FFmpeg does not ship with Audacity, and the FAQ page explains why: "Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own websites." That page points installation instructions at the Audacity Support site rather than spelling them out, so check the official documentation for the download and setup steps.
One more trap worth knowing before you try: this filter is a property of the dialog. Extended Import Preferences states that "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." Dragging the file back in after setting the filter puts you right back on libmad.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
If you do not have FFmpeg installed and do not want to install it for one file, convert the MP3 to WAV first — the Importing Audio page lists "most WAV and AIFF files including all PCM variants" among the formats Audacity reads as shipped, so a WAV never touches the MP3 importer at all. The converter above runs in your browser tab; the file is read from disk, decoded locally and handed back. The MP3 to WAV tool page is the same thing with more options.
The cost the manual admits — and competitors skip
If the dialog filter is too fiddly to repeat, the manual's Workaround-2 makes the choice permanent:
"Workaround-2 - using Extended Import rules … Type:
*.mp3in the "File Extensions" column. … Drag "FFmpeg compatible files" to the top of the "Importer order" column … De-select (un-check) "Attempt to use filter in OpenFile dialog first""
Here is the paragraph that usually gets left out. The same page, under Limitations:
"All MP3 files will always be imported in future with FFmpeg, so "Artist" and "Year" tags will not be imported."
"FFmpeg does not support Metadata as well as libmad. It misses out the "Artist" and "Year" tags, while libmad supports all of Audacity's metadata fields."
Read the scope carefully, in both directions.
- It is not "you lose your metadata." The manual names two tags: "Artist" and "Year". Audacity's Metadata Editor has seven default tags — the FAQ page lists them as "Artist Name", "Track Title", "Album Title", "Track Number", "Year", "Genre" and "Comments".
- It is not "just this one file." The rule applies to every MP3 you import from then on, which is exactly what "All MP3 files will always be imported in future with FFmpeg" says.
That trade is usually fine for editing work and genuinely annoying for library work — if you are importing an album to top-and-tail tracks and re-export them with their tags intact, Workaround-1 per file keeps libmad for everything else.
There is a related behaviour worth checking while you are in the Metadata Editor: the Importing Audio page notes that "Each time an audio file is imported into the same project window, the metadata tags for that file replace the previously stored metadata for the project. So if the last imported file has no metadata, the project will no longer have any stored metadata."
Other causes of a failed MP3 import
The file is actually corrupt. Audacity has separate wording for that. The Error: Opening or reading file page introduces its messages as "The following two warning messages occur when you try to open or import a corrupted file", and they read "Project file or audio file could not be opened - probably corrupt." and "Audio file or Project file could not be imported - probably corrupt." Different message, different problem — switching importers will not help.
You picked the wrong filter. The Import Filtering and Importer Order page describes the catch-all option: "All files: All files in the list are selectable, even those not supported by Audacity or FFmpeg; The built-in Audacity importers will be tried first, then FFmpeg (if installed)". Built-in first means libmad first, so "All files" will reproduce the same failure.
The order flag is fighting you. The same page: "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." Workaround-2 asks you to un-check that box precisely because the rule should win instead.
How to tell it worked
A track appears, and two documented behaviours tell you the import was normal rather than degraded. The manual states that "Audacity always imports files at their original sample rate, as displayed in the Track Information Area of the Track Control Panel", and that the bit depth follows your preference, not the file: "This setting defaults to 32-bit float. Therefore by default an imported file will show in the Track Control Panel as 32-bit float, even if its original bit depth is lower."
A 32-bit float track is the documented default, not a sign that something re-encoded your audio. Then open Edit > Metadata Editor and look at the Artist and Year rows — empty ones confirm you are now on the FFmpeg path.
FAQ
Why does my MP3 play everywhere else but fail in Audacity? Because Audacity's libmad importer runs error checking that most players do not. The manual says outright that millions of faulty MP3s "will play correctly in other software, but not in Audacity."
Do I have to install FFmpeg to fix this? For the manual's own fix, yes — it is the alternative importer. FFmpeg is not bundled: "Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own websites." If you would rather not install it, convert the file to WAV and import that.
What exactly do I lose by importing MP3s with FFmpeg? The manual names the "Artist" and "Year" tags, and says libmad "supports all of Audacity's metadata fields." Treat anything broader than those two tags as unverified — check the official documentation.
Is the Extended Import rule reversible? It is a rule you added in Extended Import Preferences, described by the manual as an ordering of importers. For the exact behaviour of removing one, check the official Audacity Manual.
Should I just work in MP3 once it imports? No. The MP3 Export Options page is blunt: "you will lose quality twice… So never do production work in MP3, instead work with a lossless format such as WAV, AIFF or FLAC and for final use then export to MP3." If your export sounds wrong afterwards, see Audacity's exported MP3 won't play; for the import side of MP4 files, see Audacity can't import MP4. More browser-based converters are listed under all Clapr tools, and more troubleshooting under the fix guides.
Quotations from the Audacity Manual pages Opening malformed MP3 files, Importing Audio, Import Filtering and Importer Order, Extended Import Preferences, FAQ: Installing the FFmpeg Import/Export Library and Error: Opening or reading file, checked 16 September 2026.
