Troubleshooting
Unsupported audio codec: how to identify the real problem
A familiar extension can contain a codec that the browser FFmpeg build does not include.
Reviewed against current browser behavior and AudioFetcher test fixtures on July 28, 2026.
Check these first
- 1
Use the metadata viewer to identify codec and container.
- 2
Compare against common supported inputs: MP3, AAC, FLAC, Vorbis, Opus, and PCM.
- 3
Check whether the file is encrypted or protected.
- 4
Test a known-good file with the same extension.
Reliable fixes
- Decode the source with software that legally supports its codec.
- Save to PCM WAV, then use the local tools.
- Do not rename the extension as a substitute for conversion.
Change one variable at a time and test with a short known-good file. That separates a damaged source from a browser, codec, or memory limitation.
Questions about Unsupported audio codec
What is the short answer to "Unsupported audio codec: how to identify the real problem"?
A familiar extension can contain a codec that the browser FFmpeg build does not include.
Does the linked AudioFetcher tool upload my media?
The local tools linked from this article process selected media in the browser. Read each tool's limits before using a large or uncommon file.
What is the most important practical point?
Decode the source with software that legally supports its codec.