PicaJet
Search Build shortlist

Reference Formats

AVI

AVI is Microsoft's RIFF-based multimedia container that interleaves audio and video chunks in a single file for synchronized playback on Windows.

Extension

.avi

Full name

Audio Video Interleave

Introduced

November 10, 1992 (with Video for Windows)

Vendor

Microsoft

What is inside the container

AVI is built on the generic RIFF chunk structure and can wrap many different video codecs (from uncompressed and DV to MJPEG, Xvid/DivX, and even some H.264 variants) alongside PCM or compressed audio — the container itself defines only how chunks interleave, not how the video is compressed. Its 1992-era design lacks native support for some modern features like variable frame rate and certain subtitle/metadata schemes that newer containers handle more gracefully.

How to open it

Windows Windows Media Player and Windows Movie/Photos apps play most codec variants of AVI
Cross-platform VLC Media Player plays virtually any AVI regardless of internal codec, including older DivX/Xvid encodes
macOS VLC or IINA are needed since QuickTime Player does not support AVI natively
Editing Adobe Premiere Pro and DaVinci Resolve import AVI, though codec support depends on installed system codecs

For archives

AVI is largely a legacy format in a modern DAM — retain existing AVI archives as-is rather than converting them speculatively, but plan to transcode to a modern container (MP4 or MKV) with a well-documented codec when the asset needs active reuse, since AVI's codec ecosystem (older DivX/Xvid builds especially) is increasingly hard to guarantee playback for. Always record the specific video codec (FourCC) inside the AVI, since that determines actual playability far more than the .avi extension does.

Microsoft introduced AVI on November 10, 1992, as the video format underpinning Video for Windows, its answer to Apple’s QuickTime and a first attempt to make digital video playback a standard Windows capability. Built as a specific application of the RIFF chunk architecture, AVI interleaves blocks of audio and video data so a single-threaded 1990s PC could read both in sync without a separate demultiplexing step.

AVI’s container-agnostic-to-codec design let it absorb three decades of shifting compression technology — early Cinepak and Indeo, then MJPEG for capture cards, then the DivX and Xvid MPEG-4 variants that made AVI the dominant format for downloaded video in the 2000s. That same flexibility is now a liability: an AVI file’s actual playability depends entirely on which of dozens of possible codecs it wraps, and some of the more obscure ones have effectively no modern decoder support.

For a DAM ingesting older archives — corporate video libraries, digitized tape transfers, legacy marketing assets — AVI shows up often enough that codec identification at ingest matters more than for newer formats. A DAM should probe and log the specific FourCC codec inside each AVI, flag files using obsolete or proprietary codecs for proactive transcoding, and never assume an .avi extension alone guarantees the file will open in current software.

Frequently asked

What determines whether an AVI file will actually play in modern software?

The specific video codec (FourCC) wrapped inside the AVI's RIFF chunk structure determines playability far more than the .avi extension itself, since AVI can carry anything from uncompressed and DV to MJPEG, Xvid/DivX, or even some H.264 variants.

Should a DAM convert existing AVI archives automatically?

No — retain existing AVI archives as-is rather than converting them speculatively, but plan to transcode to a modern container like MP4 or MKV with a well-documented codec once the asset needs active reuse.

Why is AVI considered a playback risk for long-term storage?

AVI's codec ecosystem — older DivX/Xvid builds especially — is increasingly hard to guarantee playback for, since some wrapped codecs have little to no modern decoder support, making codec identification at ingest important for legacy archives.

What metadata should a DAM capture for each AVI file at ingest?

The specific FourCC codec inside the AVI should be probed and logged, and files using obsolete or proprietary codecs should be flagged for proactive transcoding rather than left until a playback failure occurs.

Does AVI support modern video features like variable frame rate?

No — AVI's 1992-era design lacks native support for some modern features such as variable frame rate and certain subtitle or metadata schemes that newer containers handle more gracefully.

What tools reliably open AVI files across platforms?

VLC Media Player plays virtually any AVI regardless of internal codec, including older DivX/Xvid encodes, on Windows, macOS, and Linux; Windows Media Player also handles most codec variants natively on Windows, while macOS needs VLC or IINA since QuickTime Player doesn't support AVI natively.

Why does a DAM commonly still encounter AVI files today?

AVI shows up in older archives such as corporate video libraries, digitized tape transfers, and legacy marketing assets, since it was the dominant format for downloaded video during the 2000s via DivX/Xvid encodes.

What was AVI originally designed to solve?

Microsoft introduced AVI in 1992 as the format underpinning Video for Windows, built on the RIFF chunk architecture to interleave audio and video data so a single-threaded 1990s PC could read both in sync without a separate demultiplexing step.

Sources