Initializing... drag & drop files here
Supports: XVID
Xvid is an open-source MPEG-4 Part 2 (Advanced Simple Profile) codec released in 2001, almost always wrapped in an .avi container. It powered late-1990s and 2000s-era camcorders, peer-to-peer movie distribution, and DivX-compatible DVD players. JPG (the .jpg/.jpeg extension is identical — both refer to the same JPEG format standardized in 1992 as ITU-T T.81) is the universal lossy still-image format: 8 bits per channel, 24-bit color, decoded by every browser, OS, image viewer, and CMS without plug-ins. Pulling JPG stills out of an Xvid AVI is the standard workflow for:
| Property | Xvid (in AVI) | JPG |
|---|---|---|
| Type | Video codec (MPEG-4 ASP) in AVI container | Still image, lossy compression |
| Released / standardized | Codec 2001, AVI container 1992 | JPEG standardized 1992 (ITU-T T.81) |
| Compression | Inter-frame (I/P/B-frames) | Intra-frame (DCT, 4:2:0 chroma typical) |
| Color depth | 8-bit per channel YUV | 8-bit per channel, 24-bit color |
| Audio | Yes — usually MP3 or AC-3 in AVI | None |
| Browser playback | Limited (no native AVI/Xvid in Chrome, Safari, Firefox) | Universal — every browser since 1995 |
| Typical file size | Tens to hundreds of MB per minute | 100 KB – 2 MB per still at 1080p |
| Best for | Archived video footage | Thumbnails, photos, web images |
| Preset | Approx. Image Quality (%) | Typical use |
|---|---|---|
| Lowest | ~30% | Tiny preview thumbnails, fast loading |
| Low | ~50% | Forum avatars, throwaway shares |
| Medium | ~70% | Blog images, social media |
| High | ~85% | Web hero images, default for most uses |
| Very High (Recommended) | ~92% | Web archival, e-commerce product shots |
| Highest | ~98% | Editing source, near-lossless reference |
| Mode | Output | Best for |
|---|---|---|
| Specific Frame | One JPG at the timestamp you set | Poster art, single-scene share, bug reports |
| Multiple Screenshots | A sequence of JPGs at chosen intervals | Contact sheets, storyboards, scrubbable previews |
No major browser (Chrome, Firefox, Safari, Edge) ships with a native AVI demuxer or Xvid/MPEG-4 ASP decoder — AVI playback typically requires VLC, MPV, or a system-level codec pack. JPG, by contrast, has been a built-in browser image format since the mid-1990s. Extracting JPG frames sidesteps the codec problem entirely: the resulting stills work in every browser, OS, and image viewer without any extra software.
JPG when the frame is photographic (camcorder footage, live-action movies) and you want small files — typical Xvid frame at 720p comes out around 100-300 KB as JPG. Xvid to PNG when the frame contains text, sharp graphics, or you need lossless quality for further editing. PNG is roughly 5-10× larger for the same photographic content because it's lossless. For web thumbnails and sharing, JPG is the right default.
Functionally none — both extensions describe the exact same JPEG file format (ITU-T T.81 / ISO/IEC 10918-1). The .jpg extension is a holdover from the DOS / Windows 3.x era when filenames were limited to three-character extensions; .jpeg has been valid on every other OS since the start. XConvert lets you pick either; if you need .jpeg specifically for a CMS that filters by extension, choose that — the bytes inside the file are identical.
Pick "Specific Frame" under Frame Selection, then enter the time in the Time (Seconds) field — for example, 12.5 captures the frame at 12.5 seconds in. The decoder seeks to the nearest decodable frame at that timestamp. Xvid uses I/P/B-frames, so the actual pixel-perfect position depends on where the nearest keyframe (I-frame) falls; for typical Xvid streams keyframes are every 250-300 frames (10 seconds at 25 fps), and the tool decodes forward from the previous keyframe to land on the exact frame you asked for.
Multiple Screenshots is interval-based rather than every-frame. For a one-hour clip at 25 fps that's 90,000 frames — extracting all of them produces gigabytes of JPGs and rarely matches what users actually need. Pick a sensible interval (1 frame per second gives 3,600 stills per hour; 1 frame every 10 seconds gives 360) so the output is browseable. If you genuinely need a frame-perfect image sequence for VFX, an offline tool like FFmpeg (ffmpeg -i input.avi -qscale:v 2 frame_%05d.jpg) is the right choice.
For most uses, leave the default Quality Preset at "Very High (Recommended)" (~92%) — visually indistinguishable from the source frame at typical viewing sizes, with files around 200-500 KB at 1080p. Drop to 85% for thumbnails and social posts where bandwidth matters; 50-70% for tiny forum avatars; 95-98% only when the JPG will be edited further (each re-save of a JPG re-quantizes the DCT coefficients and adds artifacts, so start as high as practical).
Xvid compresses heavily — a 720×480 DVD-rip frame contains a fraction of the detail of a 1080p still from a modern camera, so the JPG of that frame compresses tightly. If you set Resolution Percentage below 100%, the frame is downscaled before encoding which further reduces size. To get a larger JPG, increase Image Quality (%) to 95+, set resolution to original or upscale, and avoid heavy chroma subsampling. You can also extract from a higher-resolution source if available (e.g., the same scene from a Xvid to MP4 re-encode at full resolution).
Yes — drop multiple Xvid AVI files into the uploader and apply the same Frame Selection and quality settings to all of them, or set per-file options. Each clip processes in your browser session and downloads as individual JPGs (Specific Frame mode) or per-file ZIP archives (Multiple Screenshots mode). For an entire AVI library, batch processing is faster than scripting FFmpeg one file at a time.
Often yes, up to the point of corruption. Xvid AVI streams are decodable up to the first damaged keyframe; if the corruption is in the index (idx1) chunk rather than the video stream, the tool can usually still seek and decode. For badly damaged files, try AVI to JPG which uses the same decoder pipeline but with fallback handling, or repair the AVI first with DivFix++ or a similar AVI repair tool before extracting frames.