Why an audio conversion fails in the browserMost local failures come from an unsupported internal codec, a damaged file, insufficient memory, or a suspended browser tab.Audio conversion stopped because browser memory ran outBrowser FFmpeg holds source, decoded data, and output in memory, so peak use can be several times the compressed file size.Unsupported audio codec: how to identify the real problemA familiar extension can contain a codec that the browser FFmpeg build does not include.How to tell whether an audio file is corruptTruncated headers, missing frames, impossible duration, or playback stopping at the same point indicate file damage.Why an MP3 bitrate looks different than expectedThe file may be VBR, the player may show an average, or the source may have been up-encoded without gaining quality.MP3 metadata saved but not showing in the playerThe player may cache its library, prefer a different tag field, or lack support for the written ID3 version.MP3 cover art is embedded but not displayedCached artwork, an unsupported image type, or an incorrect picture role can prevent display.WAV file is unexpectedly largeUncompressed PCM size grows directly with duration, sample rate, bit depth, and channel count.M4A file will not play: container and codec checksThe M4A may contain an unsupported codec, be incomplete, use protected content, or have a damaged MP4 container.WebM conversion produced no audioSome WebM files contain only video, multiple unusual streams, or a codec unavailable in the local build.MOV to MP3 failed or produced no audioMOV is a flexible container; camera and editing applications can store codecs that a browser build cannot decode.Audio sounds distorted after increasing volumeThe gain pushed peaks beyond the available range or exposed distortion already present in the source.Why normalized audio can sound quieterA loudness target may reduce a heavily limited source so its integrated level and true peaks fit the target.Silence remover cuts quiet wordsThe threshold is above quiet speech or the minimum-silence duration is too short.Online voice recorder cannot access the microphoneBrowser permission, operating-system privacy settings, an occupied input, or an insecure context can block microphone access.Local audio download disappeared after refreshingBrowser-local results use temporary object URLs and in-memory bytes; refreshing or closing the page intentionally clears them.Local audio tool is stuck loadingThe FFmpeg WebAssembly asset may be blocked, the browser may be compiling slowly, or an extension/security setting may prevent workers.Converted audio duration is wrongA damaged timestamp table, truncated source, variable frame timing, or an incorrect trim value can produce an unexpected duration.Why audio conversion fails on a phone but works on desktopMobile browsers have tighter memory, background execution, thermal, and file-access constraints.Generated audio file will not openThe download may be incomplete, mislabeled, empty, or encoded with a codec the target player does not support.
AudioFetcherAudio tools