AVI: Microsoft's Legacy Video Format

AVI was the format that brought video to Windows. Released in 1992 as part of Video for Windows (VFW), it predates MP4 by a decade, MKV by over a decade, and the entire concept of web video by several years. For most of the 1990s and early 2000s, AVI was synonymous with "video file on a computer."

The format is technically still functional — you can put H.264 video in an AVI container and it'll play. But doing so is like putting a modern engine in a Model T chassis: the container adds nothing and takes away features (no streaming, no chapters, limited subtitle support, no modern metadata) that every other format provides.

If you have AVI files, the right move is almost always to convert them to MP4. Here's why, and the few edge cases where AVI still makes sense.

How AVI Works

AVI uses Microsoft's RIFF (Resource Interchange File Format) structure — the same binary container used by WAV audio files. A RIFF file is a tree of "chunks," each with a four-character ID and a size field.

The key AVI chunks:

• hdrl — Header list containing stream definitions (video dimensions, frame rate, audio sample rate, codec identifiers)
• movi — The actual interleaved video and audio data
• idx1 — Index of frame offsets for seeking

The interleaving pattern: AVI alternates video and audio chunks in the movi section: a chunk of video frames, then a chunk of audio samples, then more video, then more audio. This was a practical solution for 1992-era hard drives that couldn't seek fast enough to read video and audio from separate regions of the file.

Structural Limitations

No native streaming: AVI requires the index (idx1) to be at the end of the file. You can't start playback until the entire file is downloaded, because seeking requires the index. There's no equivalent to MP4's faststart or fragmented MP4.

2GB file size limit (original spec): The RIFF format uses 32-bit size fields, capping files at 4GB. In practice, many AVI parsers choke at 2GB. OpenDML (AVI 2.0) extended this with a AVIX continuation mechanism, but support is inconsistent.

No B-frame timing: AVI's timestamp model assumes frames are displayed in the order they're stored. H.264's B-frames (bidirectionally predicted) are stored out of display order, which AVI handles poorly. Players may display stuttery or out-of-order frames when H.264 with B-frames is stuffed into AVI.

No subtitle tracks: AVI has no native subtitle support. Subtitles for AVI files are always external (.srt or .sub files alongside the .avi file).

Single audio track: AVI technically supports multiple streams, but virtually all software and players expect exactly one video stream and one audio stream. Multiple audio tracks (different languages) aren't practical in AVI — use MKV for that.

Codecs You'll Find in AVI Files

AVI doesn't restrict which codecs can be used — it stores a FourCC (four-character code) identifying the codec, and the player is responsible for having the right decoder installed. In the VFW/DirectShow era, this meant installing "codec packs" to play files. Common codecs in AVI files:

If you encounter an AVI file today, the most common codecs inside are DivX/Xvid (2000s-era downloads), Motion JPEG (security cameras, industrial cameras), or uncompressed (video capture cards).

Where AVI Still Exists in 2026

AVI refuses to die completely because it's embedded in hardware and industrial systems:

• Security cameras and DVRs: Many CCTV systems still output AVI with Motion JPEG or MPEG-4 ASP. The format is simple for embedded processors with limited firmware.
• Industrial and scientific equipment: Lab cameras, microscope capture systems, and machine vision systems often output AVI. Some of this equipment runs Windows XP-era software that was never updated.
• Legacy archives: Millions of AVI files from the DivX/Xvid era sit on hard drives and NAS boxes. Family videos from 2003 camcorders, screen recordings from early 2000s software, pirated movies from the LimeWire era.
• Stop-motion and animation: Some stop-motion software still uses AVI with uncompressed or Motion JPEG frames because each frame is independently accessible without full decode. Though modern tools have moved to image sequences or MOV/ProRes.

Migrating AVI Files to Modern Formats

AVI to MP4 is the most common migration. The conversion requires re-encoding because AVI files usually contain DivX/Xvid codecs that MP4 doesn't natively support. Re-encoding to H.264+AAC produces a universally playable file that's often smaller than the original (H.264 compresses better than DivX/Xvid). Convert AVI to MP4.

AVI to MKV is faster if you just want a modern container without re-encoding. MKV accepts any codec, so the DivX/Xvid/MJPEG streams can be remuxed (moved without re-encoding). The result plays in VLC and media servers but not in browsers. Convert AVI to MKV.

AVI to WebM requires full re-encoding to VP9+Opus. Convert AVI to WebM.

Audio extraction: AVI to MP3 extracts and converts the audio track.

Recommended approach for legacy archive migration:

1. Batch convert to MP4 with H.264 CRF 18 (visually lossless) and AAC 192kbps
2. Verify the output plays correctly and quality is acceptable
3. Keep the original AVI files as backup until you've confirmed the MP4s are good
4. Delete the AVI originals to reclaim disk space (AVI files are almost always larger)

AVI vs Modern Containers

AVI loses in every category except simplicity. Its only remaining value is compatibility with legacy systems that expect it.

AVI had a good run. It was the right format for 1992 — simple, compatible with the hardware of the time, and functional enough to bring video to personal computers. But it was never updated to keep pace with modern requirements, and every one of its contemporaries (QuickTime, RealMedia) has either evolved or died.

If you have AVI files, convert them to MP4. If you encounter equipment that outputs AVI, build a pipeline that converts to MP4 automatically. The format deserves its place in computing history, but not on your hard drive in 2026.