Cut and trim AVI video files online. Extract scenes with optional compression and resolution control — supports all AVI codecs.
Process files in seconds with our optimized servers
Set exact start and end points with frame accuracy
Maintain original quality with smart re-encoding
AVI (Audio Video Interleave) is Microsoft's container format, introduced on November 10, 1992 as part of Video for Windows. Three decades on, AVI is still common for DivX/Xvid movie archives, dashcam and CCTV footage, screen-capture output from older versions of Bandicam and Camtasia, and DV camcorder transfers. These sources tend to produce long, continuous recordings — exactly the files that need a clean trim before they go anywhere else.
| Property | AVI | MP4 | MKV |
|---|---|---|---|
| Released | Nov 10, 1992 (Microsoft) | 2001 (ISO/IEC 14496-14) | 2002 (open standard) |
| Typical codecs | DivX, Xvid, MJPEG, MPEG-4 | H.264, H.265, AV1, AAC | H.264, H.265, AV1, FLAC |
| B-frame support | Unreliable (RIFF chunk timing) | Yes | Yes |
| Subtitles in container | No (external .srt only) | Yes (mov_text, tx3g) | Yes (SRT, ASS, PGS) |
| Multiple audio tracks | Limited / nonstandard | Yes | Yes (unlimited) |
| Chapters / metadata | Minimal | Yes | Yes (rich) |
| Streaming / web playback | No (not browser-native) | Yes (HTML5 native) | Limited |
| Best for | Legacy archives, DV capture | Sharing, web, mobile | Multi-track storage |
| Mode | What it does | When to use |
|---|---|---|
| Quality Preset (Highest–Lowest) | One-click visual quality target | Quickest path; "Very High" matches most source DivX/Xvid quality |
| Target file size (%) | Output is N% of input size | "Cut and shrink to 50%" for email/Discord shares |
| Specific file size | Pin exact MB output | Hitting a hard cap (e.g., 25 MB Gmail) |
| Constant Bitrate (CBR) | Steady kbps throughout | Streaming targets where rate must stay flat |
| Variable Bitrate (VBR) | Bits flex with scene complexity | Best size-vs-quality on mixed motion content |
| Constant Quality (CRF) | Same perceived quality everywhere | Most efficient default; CRF 18 archive, 23 balanced, 28 small |
| Constraint Quality | Quality with a max-bitrate ceiling | Quality-first, but safe for bitrate-limited devices |
XConvert re-encodes when you change resolution, codec, or bitrate. For pure stream-copy trimming (no quality loss, instant cuts), use Quality Preset "Highest" with the original resolution — that produces the closest-to-source output a browser-side trim can deliver. True frame-accurate stream-copy editing requires desktop tools like LosslessCut, VirtualDub, or Avidemux, which align cuts to keyframes.
AVI with B-frame codecs (Xvid, DivX, MPEG-4 ASP) only allows clean cuts on keyframes (I-frames). If you cut between keyframes, the decoder needs the previous I-frame plus B/P-frame chain to reconstruct the first second. XConvert re-encodes around the cut to give frame-accurate output, which avoids this artifact entirely — the tradeoff is a re-encode pass.
The trimmer reads AVI containers carrying DivX, Xvid (MPEG-4 ASP), MJPEG, MPEG-4 Part 2, uncompressed RGB / BMP, DV (DV-AVI from MiniDV / HDV camcorders), and the rare H.264-in-AVI streams. Audio inside AVI is typically MP3, AC-3, or PCM.
Original 1992 AVI had a 2 GB practical limit; the OpenDML extension (Matrox, February 1996, sometimes labeled "AVI 2.0") raised this to terabytes. Most modern AVI files use OpenDML and trim fine. If you have a true legacy pre-1996 AVI hitting the 2 GB ceiling, the file is usually already truncated.
For sharing or web embedding, MP4 wins — every browser, phone, and TV plays H.264 MP4 natively. Trim and convert in one pass with AVI to MP4. Keep AVI if you need to drop the file back into legacy Windows software, an existing DivX/Xvid library, or a video-editing project that expects the original container.
Yes — that's the main reason to use a re-encoding trimmer over a stream-copy one. Combine "Time Range" with "Target file size (%)" at 50% to roughly halve the output, or set CRF 23 in Constant Quality mode for a clean balance. For larger files, the dedicated Compress AVI tool gives more bitrate-tuning headroom on the full file.
AVI does not store subtitles inside the container — they live in a separate .srt file alongside the video. The trim only affects the AVI itself, so you'll need to retime or re-cut the .srt manually (or convert the package to MKV with AVI to MKV, which embeds subtitles natively).
Multiple audio tracks in AVI are technically possible via the RIFF spec but poorly supported across players — most decoders only read the first track. If your source has commentary or multi-language tracks, trimming through MKV preserves all of them; AVI may drop the extras. For multi-track sources, AVI to MKV is the safer path.
The free trimmer handles AVIs typical of dashcam, screen-recording, and DV-camcorder workflows in a single browser session. For DV-AVI captures (~13 GB/hour) or long surveillance pulls, trim in shorter passes — your browser tab's memory is the practical ceiling, not a hard server limit.
Yes — XConvert offers the same trim controls for MP4 and MOV sources. The compression and resolution options carry over identically; only the output container changes.