AVI (Audio Video Interleave) is Microsoft's container from 1992, and the .avi files that survive today are usually decades old: home videos from early digital camcorders, DivX or XviD movie rips from the file-sharing era, screen captures from a long-defunct Camtasia version, or scientific recordings from lab cameras with proprietary codecs. AVI predates streaming; it was designed for spinning hard disks and CDs, and its structure makes random-access into long files awkward. None of that matters for converting to MP3 — we read the audio track sequentially and re-encode it.
Because AVI is well outside the WebCodecs sweet spot, this conversion runs on the FFmpeg-wasm fallback engine. That means a one-time ~30 MB download the first time you convert (cached after that), then conversion proceeds. The file is processed in memory, which the browser caps around 2 GB — so a single multi-gigabyte AVI rip may need to be cut on the desktop first. Most surviving AVIs are well under that limit.
Common scenarios
When to convert AVI to MP3
Old camcorder footage
Mini DV and early digital camcorders often dumped to AVI with MP3 or PCM audio. Extract the audio for memorial montages or family archives.
DivX / XviD movie rips
If you legally ripped DVDs in the 2000s to AVI, the audio is usually MP3 or AC-3. Pulling an MP3 out for car listening is straightforward.
Lab and scientific recordings
Microscope cameras and instrumentation software often save AVI with PCM or uncompressed audio. Convert to MP3 for easier review and sharing.
Archive digitization
Older tutorial CDs and educational discs used AVI extensively. Pulling MP3 audio for long-form listening is a common digitization step.
Under the hood
How the conversion works
Why AVI needs the compatibility engine
AVI's container quirks (chunk-based, no global index in many older files) and the long tail of obscure audio codecs (DivX Audio, GoToMeeting G2M, Xperts variants) mean the WebCodecs fast path doesn't handle it. FFmpeg-wasm carries decoders for essentially everything AVI has ever wrapped, which is why we route AVI through it.
The 2 GB ceiling
FFmpeg-wasm allocates linear WebAssembly memory inside a single browser tab, capped at roughly 2 GB by the 32-bit memory model that current FFmpeg builds use. Most archival AVIs are well under that. For genuine multi-gigabyte AVIs, use a desktop tool to split the file first (or convert directly with command-line FFmpeg).
How to
Step by step
- 1
Drop your .avi
Drag the file in. The first time, the FFmpeg engine loads (~30 MB, cached after).
- 2
Confirm MP3 + bitrate
For old camcorder audio, 192 kbps is usually plenty — these sources weren't high-fidelity to start with.
- 3
Wait and download
Conversion is slower than WebCodecs-based formats but still typically minutes, not hours.
FAQ
Frequently asked questions
Why is the first AVI conversion slower than the same MP4?
AVI uses the FFmpeg-wasm fallback, which has to load ~30 MB of WebAssembly the first time. After that the engine is cached and subsequent conversions start instantly. MP4/MOV/MKV/WebM use a lighter native-WebCodecs engine that's already shipped.
Can I convert a 3 GB AVI rip?
The browser's WebAssembly memory ceiling is around 2 GB. For files over that, split the AVI on the desktop (with VirtualDub or command-line FFmpeg) and convert pieces. We're investigating Memory64 for a future build that would lift this limit.
My AVI has DivX or XviD audio — wait, audio? Those are video codecs.
Correct — DivX and XviD are video codecs, paired inside AVI with separate audio codecs, usually MP3 or AC-3. Don't worry about the video; we discard it and process only the audio track.
Does the AVI need to be on the same drive as the browser?
Yes — for the drag-and-drop step. The browser reads the file from disk into a memory buffer; that file needs to be reachable from the file picker.
What if the audio in the AVI is some obscure codec I've never heard of?
FFmpeg-wasm includes decoders for essentially every audio codec ever shipped in an AVI. If you hit a file that genuinely won't decode, please open a GitHub issue with the codec name from a tool like MediaInfo — we can usually expand support.
See also
Related converters