If you have an AVI file in 2026, it almost certainly came from one of three places: a digital camcorder you forgot about in a drawer, a screen recorder from the early 2000s that you've reinstalled by muscle memory, or a download from a corner of the internet that hasn't been updated since file sharing was a noun. The file plays in VLC, refuses to play in Quicktime, embarrasses you when you try to attach it to an email, and gets rejected by every social platform's upload form.

This isn't AVI being broken. AVI is doing what it was designed to do in 1992, which is wrap a video stream and an audio stream into a single file using a fixed-header container. The problem is that the codecs people used inside AVI containers — DivX, Xvid, MS-MPEG-4 v2, MP3 audio — are retired in the modern playback world. Browsers don't ship decoders for them. iOS and Android don't either. Windows 11's built-in player technically can, with the right codec pack, but the pack isn't installed by default. So you end up with a file that VLC plays because VLC ships its own decoders for everything, and nothing else plays because everything else relies on the OS for codec support.

TL;DR

  • Use Clipy's AVI to MP4 converter. Drop the file in, click convert, download the MP4. The conversion runs in your browser — no upload, no account.
  • The output is H.264 video plus AAC audio in an MP4 container — the universal modern target. Plays everywhere: browsers, phones, social platforms, embed surfaces, video editors.
  • Older AVI files containing DivX, Xvid, or MPEG-4 ASP video are fully decodable by the converter. You don't need a codec pack.
  • For other dead format containers (MKV, FLV, WMV) use MKV to MP4 or WebM to MP4; for legacy AVI specifically, this is the tool.
  • FFmpeg one-liner if you want command line: ffmpeg -i input.avi -c:v libx264 -pix_fmt yuv420p -crf 23 -c:a aac -b:a 192k -movflags +faststart output.mp4

Why AVI is dead and isn't coming back

AVI — Audio Video Interleave — is a Microsoft container format introduced in 1992 as part of Video for Windows. It was the dominant consumer video container through the early 2000s. Its design assumptions were correct for 1992: fixed-size index at the end of the file, no support for streaming, no support for B-frames in the way modern codecs use them, no support for variable frame rate, no provision for modern subtitle tracks, no per-stream metadata.

Every one of those design choices conflicts with what video does in 2026. Streaming requires the metadata at the front of the file so the player knows what's inside before downloading the whole thing — MP4 has this with faststart, AVI cannot. Variable frame rate is standard in screen recordings and webcam captures — AVI can't represent it cleanly. Modern codecs like H.264 and H.265 rely on B-frames (bidirectionally-predicted frames) and complex temporal references — these technically fit in AVI but break many AVI parsers.

The other half of AVI's irrelevance is the codecs people put inside it. DivX, Xvid, MS-MPEG-4 v2, and 3ivX were the dominant video codecs in AVI files. None of them are shipped by any modern platform's built-in decoder. iOS doesn't decode DivX. Android doesn't. Chrome, Firefox, and Safari don't. Even Windows 11 doesn't include the decoders by default — you'd need a codec pack from somewhere, and codec packs are a known source of malware.

The replacement, since about 2010, has been MP4 containers with H.264 video and AAC audio. This combination is decoded natively by every browser, every phone, every social platform's upload validator, every video editor. It is the actual universal standard. Converting your AVI files to it is the difference between "this file is a museum piece" and "this file plays everywhere."

What the conversion actually does

Converting AVI to MP4 is two operations done in sequence. First, the decoder pulls the video stream out of the AVI container and decompresses it from whatever codec it was in (DivX, Xvid, MPEG-4 ASP, or in rare modern AVIs, H.264) back to raw pixel data. The audio stream gets the same treatment — decompressed from MP3 or PCM back to raw audio samples.

Then the encoder takes those raw frames and audio samples and compresses them into the modern target: H.264 video and AAC audio. The output gets packed into an MP4 container with the metadata at the front (faststart) so streaming clients can begin playback before downloading the whole file.

This is a full transcode, not a remux. You can't just rewrap AVI contents into MP4 because most of the old codecs aren't MP4-compatible. Even if the source video was H.264 inside the AVI (rare but possible — late-era AVI files sometimes did this), the audio is almost certainly MP3, and MP4 prefers AAC for maximum compatibility. The encoder does both.

A transcode means the conversion takes time proportional to the length of the video. A 10-minute AVI takes longer to convert than a 30-second one. The Clipy converter shows progress as it works. Conversion speed scales with your CPU because everything happens locally — there's no server queue to wait in, but there's also no server CPU to lean on. Modern laptops handle 10-minute conversions in 1–3 minutes depending on resolution.

"VLC plays it, why bother converting?"

The pragmatic answer: because you can't share it. VLC plays AVI files because VLC ships its own decoders for hundreds of codecs. That doesn't help when you email the file to someone whose default player is Windows Media Player, QuickTime, or the iOS Photos app. None of those have the codec. The file appears broken to them even though it's not.

It also doesn't help when you try to upload the file anywhere. Social platforms validate the container format and reject AVI outright. Embed surfaces require MP4 or WebM. Video editors prefer MP4 for ingest and many won't import AVI without a transcode step anyway.

And if you want to preserve the video — actually archive it for the long term — MP4 is the safer bet. AVI's tooling support is shrinking every year. The decoders that exist are unmaintained. In ten years, MP4 will still play everywhere. AVI will play in VLC and historical software.

The quirks of old AVI files and how the converter handles them

Real-world AVI files have accumulated decades of quirks. The Clipy converter handles the common ones, but knowing what they are explains why some files take a moment longer to convert.

Index at the end. AVI puts its frame index at the end of the file. For a damaged AVI where the end is missing or corrupted, the index is unreadable and most players choke. FFmpeg's AVI demuxer can rebuild the index by scanning the file, which is slower but works. The Clipy converter does this automatically when needed.

Variable frame rate. Strictly, AVI is a fixed-frame-rate container. In practice, many AVI files from screen recording tools have variable frame rates encoded via repeated frames or weird timestamps. The converter normalizes this to a constant frame rate (usually 30fps) in the output, which is what MP4 prefers.

Audio sync drift. Long AVI files sometimes have small drifts between audio and video timing accumulated over the recording. Modern containers handle this better. The converter resamples the audio against the video timeline to keep them aligned.

Non-square pixels. Some old AVI files use non-square pixel aspect ratios (PAR != 1:1) which were common in DV camcorder footage. The converter scales the output to square pixels so the video looks correct in modern players without needing a PAR-aware decoder.

None of these require user intervention. They're handled automatically when the converter detects them. The output is a clean MP4 that plays correctly everywhere.

What happens to file size

This depends on what codec was inside the AVI. The two most common cases:

AVI with DivX or Xvid video. These codecs are roughly comparable to H.264 in compression efficiency for their era but lag the modern encoder by a noticeable margin. Converting to H.264 with a sensible CRF usually produces an MP4 about the same size as the input or slightly smaller. Quality stays the same.

AVI with uncompressed or DV video. Rare in the wild but they exist — usually camcorder output. These files are huge (hundreds of MB per minute). Converting to H.264 shrinks them by 10–50x with no visible quality loss. This is the case where conversion is the biggest win.

If the output is still bigger than you want, run it through Clipy's video compressor with a higher CRF or a target file size.

The MKV and WebM cousins

AVI's lineage didn't quite die — it spawned successors. MKV (Matroska) is a more modern flexible container that became popular for high-bitrate downloads and Blu-ray rips. WebM is a stripped-down MKV with mandatory VP8/VP9/AV1 video and Vorbis/Opus audio, designed for the web. Both have similar "works in VLC, fails in social uploads" problems for similar reasons: the codecs inside are often not the universally-supported H.264.

The fix is the same shape: convert to MP4 with H.264 + AAC. MKV to MP4 handles MKV files; WebM to MP4 handles WebM. Both run in the browser using the same WebAssembly FFmpeg pipeline, no upload, no signup.

If you have a MOV file (Apple's container, similar issue with Windows playback), MOV to MP4 handles that path.

Command line version, for the FFmpeg-curious

ffmpeg -i input.avi \
  -c:v libx264 -crf 23 -pix_fmt yuv420p \
  -c:a aac -b:a 192k \
  -movflags +faststart \
  output.mp4

Notes on the flags. -crf 23 is the standard quality target for H.264; visually identical to the source for most content. Lower is higher quality and bigger file; 18 is visually lossless to most viewers. -pix_fmt yuv420p is the chroma subsampling required for universal playback. -c:a aac -b:a 192k encodes the audio at a reasonable bitrate. -movflags +faststart moves the metadata to the front of the file so streaming clients can start playback immediately.

If the source AVI uses Xvid or DivX, FFmpeg's libavcodec will decode it automatically — you don't need a separate codec pack. If you get errors about an unknown codec, the AVI is probably wrapping a truly obscure codec (Cinepak, Indeo, RealVideo) and you may need a system-wide codec install. The browser converter has the same coverage as command-line FFmpeg for these.

The fastest path, summary

Open Clipy's AVI to MP4 converter. Drop the file in. Wait for the conversion (proportional to file length, not size). Download the MP4. The output is H.264 + AAC in an MP4 container with faststart enabled — universal compatibility.

No upload, no account, no watermark, no file size cap. The file stays on your machine; the conversion happens in your browser tab. If the output is bigger than you want for sharing, video compressor shrinks it. For MKV and WebM siblings, the corresponding tools (MKV to MP4, WebM to MP4) handle those paths.