Initializing... drag & drop files here
Supports: AVI
2.100 (2 seconds and 100 ms) to capture exactly one still. Switch to Multiple Screenshots to extract a sequence at a chosen capture rate (0.1s, 0.2s, 0.3s, 0.5s, 1s, 2s, 3s, 4s, 5s, 6s, 7s, 8s, 9s, or 10s per frame).AVI is a 1992-vintage Microsoft container that stayed dominant through the DivX/Xvid era of the early 2000s. Most "movie.avi" files in personal archives, old camcorder dumps, dashcam SD cards, and CCTV exports are still AVI. Extracting JPG stills turns that motion footage into shareable, embeddable, archivable images — without re-encoding the whole video.
12.450 seconds for an insurance claim, police report, or HOA submission. JPG keeps file sizes small enough to email.| Property | AVI (Audio Video Interleave) | JPG (JPEG) |
|---|---|---|
| Type | Video container | Single still image |
| Released | 1992 (Microsoft Video for Windows) | 1992 (Joint Photographic Experts Group) |
| Typical codecs | DivX, Xvid, MJPEG, H.264, uncompressed | DCT-based lossy compression |
| Audio | Yes (MP3, AC-3, PCM) | No |
| Plays in browsers | Limited — needs codec support | Universal |
| File size for 1 min 720p | 50-200 MB | 80-300 KB per frame |
| Embeds in docs / slides | Poor | Universal |
| Best for | Storage / playback of full recordings | Thumbnails, evidence, references |
| Goal | Frame selection mode | Capture rate / time |
|---|---|---|
| One thumbnail / poster | Specific Frame | Pick the timestamp (e.g. 00:05.000) |
| Evidence still from CCTV | Specific Frame | Exact incident time, e.g. 12.450 |
| Storyboard contact sheet | Multiple Screenshots | 5 or 10 seconds per frame |
| Editing image sequence | Multiple Screenshots | 0.1s (10 fps) or 0.2s (5 fps) |
| Rough video summary | Multiple Screenshots | 1 second per frame |
| Frame-by-frame sports analysis | Multiple Screenshots | 0.1s (10 fps) |
Use Specific Frame mode and enter the time in seconds with millisecond precision. For example, 2.100 means 2 seconds and 100 milliseconds into the AVI. Use this when you need the exact moment of a sports highlight, the frame just before a crash on a dashcam, or the frame where a person enters a CCTV view.
Depends on the capture rate. At 1 second per frame you'll get 600 JPGs. At 0.1s per frame (10 fps) you'll get 6,000 JPGs — that's fine for editing pipelines but heavy in a browser. At 5 seconds per frame you'll get 120 stills — a manageable contact sheet. Pick the slowest rate that still captures the moments you need.
The extracted JPG matches the AVI's actual frame size, not the playback dimensions. A "720p AVI" from 2005 is often actually 720x404 letterboxed, or even 640x360 upscaled. Use the resolution presets to upscale to a larger output, or set a higher Image Quality preset (Very High / Highest) to keep more detail. Note that upscaling can't add real pixels — it interpolates.
JPG for photographic content (live-action footage, faces, landscapes) and when file size matters. PNG for screenshots, screen recordings, computer-generated content, and when you need pixel-exact text or graphics. PNG is lossless but typically 3-5x larger. See AVI to PNG for lossless extraction.
No — JPG is a still image format with no audio support. The audio track (if any) is discarded during extraction. If you need the audio separately, see AVI to MP3.
Yes. XConvert decodes DivX (DivX 3 / 4 / 5), Xvid, MJPEG, H.264-in-AVI, and uncompressed AVI. Frame extraction reads the decoded pixel data, so codec quirks that prevent playback in some media players don't usually block frame extraction here.
AVI playback in modern browsers is unreliable — most don't natively support the container. The frame extraction still works because we decode the video stream directly, independently of any browser playback. If preview fails but extraction succeeds, that's expected.
Set Multiple Screenshots to 0.1 seconds per frame (10 fps) for the densest extraction available. For true every-frame extraction matching the AVI's native frame rate (often 24, 25, 29.97, or 30 fps), the 0.1s preset is close enough for most editing workflows. Note that a 5-minute AVI at 30 fps native = 9,000 frames — plan storage accordingly.
Files are processed in your browser session via secure WebAssembly decoding. Frames are extracted client-side wherever possible. No watermarks, no sign-up, and you can also see AVI to GIF if you'd rather have an animated output instead of stills.