AVI MIME Type
video/x-msvideo identifies, how AVI stores audio and video, which applications open it, and how Poly supports AVI files. MIME type details for video/x-msvideo
In active use| MIME type | video/x-msvideo |
|---|---|
| Extensions | .avi |
| Magic number | 52 49 46 46 ?? ?? ?? ?? 41 56 49 20 |
| First standardized | 1992 |
| Created by | Microsoft |
| Browser support | |
| Example applications | VLC media player, Windows Media Player |
| Poly support | Yes. Poly recognizes `.avi` files and processes decodable audio and video streams for preview, search, and metadata. |
| Indexed by Poly | Yes. Poly indexes the filename, available technical metadata, spoken transcript, and sampled visual content. A transcript requires a usable audio track. |
| Preview in Poly | Yes. Poly provides a thumbnail, timeline previews, and in-app playback when the AVI's codecs can be decoded. |
| Poly agent | Yes. The Poly agent can use the video's visual content, transcript, and supported metadata. Results depend on decodable streams and audible speech. |
What does video/x-msvideo mean?
The video/x-msvideo media type identifies AVI, Microsoft's Audio Video Interleave container. AVI stores one or more timed streams, usually video and audio, in a RIFF structure. The media type and the .avi extension identify the container, not the compression method inside it.12
That distinction explains why two .avi files can behave very differently. One might contain uncompressed frames and PCM audio, while another uses older compressed codecs that are no longer installed. A player has to understand the AVI container and every codec needed by its streams.
video/x-msvideo is the common web media type for .avi files, and MDN lists that pairing in its common-types reference.1 RFC 2361 also defines video/vnd.avi;codec=... for naming a specific codec from the historic AVI registry.3 These labels describe the same container family, but they are not interchangeable with a codec name.How to identify an AVI file
AVI is based on RIFF. A conventional file begins with the ASCII bytes RIFF, followed by a four-byte size field, then the form type AVI , including the trailing space. In hexadecimal, that pattern is:
52 49 46 46 ?? ?? ?? ?? 41 56 49 20
Checking only 52 49 46 46 is not enough. WAV, WebP, and other formats also use RIFF. A detector should confirm the AVI form type at bytes 8 through 11 and validate the following chunk structure.24
Microsoft's AVI reference describes three important areas:2
- An
hdrllist containing the main header and a description of each stream. - A
movilist containing the interleaved video frames and audio samples. - An optional
idx1index that helps a player seek to media data.
FOURCC values identify chunks, stream types, and many video codecs. The main header can record details such as stream count, width, and height. Each stream then has its own header and format information.2
Why an AVI file may not play
AVI is a container rather than a single codec. Recognizing the container does not guarantee that a device can decode its streams. Microsoft notes that Windows Media Player can play AVI content only when the corresponding codecs are available, and lists examples ranging from DV and MJPEG to DivX, Cinepak, Indeo, and uncompressed video.5
This also makes browser support unreliable. Current web guidance recommends MP4 or WebM for general-purpose delivery and does not list AVI among broadly supported HTML video containers.6 An AVI that opens in a desktop player may still fail in a browser, or it may play video without audio when only one codec is supported.
.mp4 changes only the filename. It does not move the streams into an MP4 container or convert their codecs.VLC is a useful first choice for local playback because its published feature list includes AVI among its supported input containers.7 Windows also has native AVI container support through Media Foundation, but actual playback still depends on the codecs carried by the file.58
AVI support in Poly
Poly recognizes .avi files as video/x-msvideo. When the contained streams can be decoded, Poly gives AVI the same practical video experience as other supported videos:
- A representative thumbnail and timeline previews for quick navigation.
- In-app playback that can jump to a matching moment.
- Technical metadata such as duration, dimensions, frame rate, codecs, color information, and audio-track details when available.
- Search by filename, spoken transcript, and sampled visual content.
- Access to supported visual content, transcript, and metadata through the Poly agent.
Speech search and transcript-based agent answers require an audio track with audible speech. Silent AVI files can still benefit from visual search. Damaged files or files containing unsupported legacy codecs may have limited preview, indexing, or agent access.
See Supported File Types for the compact feature comparison.
Converting AVI to MP4 or WebM
For web publishing, MP4 is usually the most compatible destination, while WebM is an open, web-focused alternative.6 Choose conversion settings based on what is inside the source:
| Goal | Recommended approach | Why |
|---|---|---|
| Broad playback | Encode video as H.264 and audio as AAC in MP4 | This combination is widely supported by browsers and devices.6 |
| Open web delivery | Encode to VP9 or AV1 video with Opus audio in WebM | WebM is designed for modern web use.6 |
| Preserve quality for editing | Use a suitable lossless or editing codec in a compatible container | Re-encoding to a delivery codec can discard detail. |
| Preserve an already compatible stream | Remux without re-encoding | This is fast and lossless, but only works when the destination container accepts the existing streams. |
Keep the original until you verify duration, audio synchronization, frame rate, orientation, and every required audio or subtitle stream. Old AVI files sometimes depend on uncommon codecs, so a conversion that silently drops a stream is not a successful preservation copy.
AVI, OpenDML AVI, and modern containers
The original AVI design dates to 1992. OpenDML extensions later expanded the format and addressed limitations of the original layout; the Library of Congress notes that these extensions are often informally called AVI 2.0.4 OpenDML AVI files still normally use .avi and the same container-level media type, so the filename alone does not reveal which indexing layout is present.
AVI remains useful for legacy collections, capture systems, and workflows built around particular codecs. For new delivery files, MP4 and WebM have a clearer web compatibility story. The important choice is not just “AVI versus MP4.” It is the combination of container, video codec, audio codec, metadata, and the software expected to read them.
Footnotes
- MDN Web Docs. Common Media Types. ↩ ↩2
- Microsoft. AVI RIFF File Reference. ↩ ↩2 ↩3 ↩4
- RFC Editor. RFC 2361: WAVE and AVI Codec Registries. This informational RFC defines codec-qualified names in the IANA vendor tree. ↩
- Library of Congress. AVI (Audio Video Interleaved) File Format. ↩ ↩2
- Microsoft Support. File Types Supported by Windows Media Player. ↩ ↩2
- MDN Web Docs. Media Container Formats. ↩ ↩2 ↩3 ↩4
- VideoLAN. VLC Features. ↩
- Microsoft. Supported Media Formats in Media Foundation. ↩