Initializing... drag & drop files here
Supports: MP4, M4V
MP4 is the modern default for video, but AVI — Microsoft's Audio Video Interleave container, released November 10, 1992 as part of Video for Windows — is still the only format some workflows accept. AVI is a RIFF-based wrapper that can hold MPEG-4 ASP (DivX/Xvid), MJPEG, uncompressed YUV, and other codecs. Modern apps prefer MP4 because AVI cannot reliably store B-frames, lacks native subtitle/chapter support, and adds roughly 5 MB of index overhead per hour of SD video. Convert to AVI when the target system can't open MP4:
If your goal is the reverse — getting an old AVI into modern playback — use AVI to MP4 instead. To shrink an oversized source before conversion, run it through Compress MP4 first.
| Property | MP4 | AVI |
|---|---|---|
| Released | 2001 (ISO/IEC 14496-14) | November 1992 (Microsoft) |
| Underlying structure | ISO Base Media File Format | RIFF chunks (hdrl / movi / idx1) |
| Typical video codecs | H.264, H.265/HEVC, AV1, MPEG-4 ASP | MPEG-4 ASP (DivX/Xvid), MJPEG, uncompressed |
| Typical audio codecs | AAC, AC-3, Opus | MP3 (CBR), PCM, AC-3 |
| B-frames | Full support | Not reliably supported |
| Streaming / fast-start | Yes (moov atom) | Not designed for streaming |
| Subtitles & chapters | Native | Limited / third-party only |
| Variable bitrate MP3 | Yes | Broken below 32 kHz |
| Per-hour overhead (SD) | ~1-2 MB | ~5 MB |
| Browser playback | All major browsers | None |
| Codec | Best for | File size | Trade-offs |
|---|---|---|---|
| Xvid (MPEG-4 ASP) | DivX-certified DVD players, generic legacy compat | Medium | Open-source; broadest legacy player support |
| DivX (MPEG-4 ASP) | DivX-branded hardware, older PC media players | Medium | Same family as Xvid; sometimes branded differently in player menus |
| MJPEG | Frame-accurate editing, machine vision, microscopy | Large (3-5x) | Intra-frame; instant seeking; very high quality per frame |
| Uncompressed (YUV) | Pristine intermediates for finishing | Very large (10-20x) | No generation loss; impractical above short clips |
| H.264 in AVI | Niche editors that accept it | Smaller | Many AVI-only tools cannot decode this; verify first |
MP4 to AVI almost always grows the file. A 100 MB H.264 MP4 typically becomes 200-400 MB as Xvid AVI and 500 MB+ as MJPEG AVI, because Xvid/MJPEG cannot match H.264's compression and AVI itself adds index overhead. This is the cost of legacy compatibility — accept it, or pick a more efficient container like MKV via MP4 to MKV if your target supports it.
Some container conversions can be done losslessly by copying the elementary streams (remuxing) without re-encoding. MP4 to AVI usually cannot, because the codecs differ: MP4 commonly carries H.264/HEVC + AAC, while AVI players expect Xvid/DivX/MJPEG + MP3/PCM. Re-encoding the video stream is required, which introduces one generation of loss. To minimize it, pick the highest Quality Preset (Very High) or a low CRF/qscale and accept the larger file.
Xvid is the most broadly compatible choice. DivX-certified players list "DivX" and "Xvid" interchangeably on the bezel because both implement MPEG-4 ASP. Avoid H.264-in-AVI and MJPEG for these players — most can't decode either. If the player ships a sticker with a specific profile (DivX Home Theater, DivX HD), match that profile's resolution and bitrate ceiling in our Bitrate / Resolution controls.
AVI's typical codecs (Xvid, DivX, MJPEG) use older compression than H.264. Modern smartphones record H.264 or H.265, both of which use B-frames and CABAC entropy coding that AVI codecs lack. Add roughly 5 MB per hour of RIFF index overhead and you land at 2-5x file growth. There is no setting that fixes this — it is the trade-off for legacy compatibility.
Only if the MP4 already contains a codec AVI supports — almost no consumer MP4 does. Phone, GoPro, drone, and screen-recorder MP4s are H.264 or H.265, both of which need to be transcoded to Xvid/DivX/MJPEG for legacy player support. Pick the highest Quality Preset to minimize the one generation of loss.
The classic XP/Vista/7-era Movie Maker accepts .avi, .wmv, .mpg, .mpeg, .m1v, .mp2, .mp2v, .asf, and .wm — but not .mp4 from H.264 sources. Converting to Xvid AVI lets it import the clip. Note that Microsoft discontinued Windows Movie Maker in January 2017; on Windows 10/11, the built-in Photos / Clipchamp apps already accept MP4 directly and no conversion is needed.
Free-tier users can convert files up to several GB per upload. Files are processed on our servers and tied to your browser session; close the tab and they're cleared. For very large source MP4s, compressing first with Compress MP4 shortens upload and conversion time.
Technically yes, but it's not practical. AVI lacks the metadata fields modern HDR pipelines expect (color primaries, transfer characteristics, mastering display luminance), and Xvid/DivX MPEG-4 ASP is 8-bit 4:2:0 by design. For 4K HDR, stay on MP4 or move to MKV — converting to AVI will discard HDR metadata and clip the 10-bit signal to 8-bit.
No. AVI has only fragile, third-party support for subtitles and chapters, and most legacy players will ignore extra tracks. Embedded soft subtitles from an MP4 are dropped during conversion. If you need to keep subtitles, burn them in before converting, or stay on a container that supports them natively (MP4 or MKV).
Yes. Files are uploaded over TLS, processed in your session, and removed automatically after a short retention window. No account is required, no watermark is added, and we do not resell uploads. If you need stricter handling — air-gapped editorial systems, classified material — run the conversion on your own machine with FFmpeg locally.
If the target is anything from 2015 or later, MP4 or MKV is almost certainly a better fit and will save you hours debugging codec packs. Convert to AVI only when a specific named device or piece of software explicitly requires it. The list of "must use AVI" situations is shrinking — modern Windows, macOS, Linux, smart TVs, and current DVD players all accept MP4 natively.