Initializing... drag & drop files here
Supports: MPEG2
Turn a clip from an old MPEG-2 file — a DVD rip, a .mpg/.vob-era capture, or a broadcast recording — into a looping animated GIF you can drop into a chat, a forum post, or a README. MPEG-2 (ISO/IEC 13818 / ITU-T H.262, standardized 1995) is the DVD and digital-TV codec, so its footage is usually standard definition and frequently interlaced; this converter resamples that into a GIF's 256-color, no-audio loop. Best for pulling a short reaction or preview out of footage that nothing modern wants to autoplay.
.mpeg2 file or click "+ Add Files" to browse. Batch upload works — the same settings apply to every file in the queue.| Property | MPEG-2 source | GIF output |
|---|---|---|
| Standard | ISO/IEC 13818-2 / ITU-T H.262 (1995) | GIF89a (1989), LZW-compressed |
| Typical resolution | SD: 720×480 (NTSC) / 720×576 (PAL) | Whatever you downscale to (480p/360p common) |
| Scan type | Often interlaced (480i / 576i) | Progressive frames only |
| Color | 8-bit 4:2:0, millions of colors | 256 colors per frame, banding likely |
| Audio | Yes (MPEG audio / AC-3 on DVD) | None — GIF is silent |
| Motion compression | Inter-frame (P/B frames) | Per-frame LZW, no motion comp — large files |
| Best at | Full-length video, archival | 2-6 second silent loops for chat and web |
It can, because MPEG-2 from DVD and broadcast is frequently interlaced (480i or 576i) — each frame is two fields captured a moment apart. When that's flattened into a progressive GIF frame, fast motion shows comb-tooth artifacts. Two ways around it: pick a low-motion segment where fields nearly match, or if combing is heavy on the footage, convert to MPEG-2 to MP4 first (where deinterlacing has room to work) and make the GIF from the cleaned video.
GIF has no inter-frame motion compression — every frame is stored as its own LZW-compressed 256-color image, while MPEG-2 only encodes the differences between frames. A few seconds of GIF can dwarf the source clip. In our testing, a 6-second 480p loop at 10 FPS landed in the low single-digit megabytes. The biggest lever is resolution (size scales roughly with pixel count, so 720p→480p more than halves it), then duration, then frame rate and palette. If you have already trimmed and downscaled and it's still heavy, run the result through Compress GIF for a second optimization pass.
GIF caps each frame at 256 colors drawn from a 24-bit space, whereas MPEG-2 carries millions. Gradients, skies, and skin tones posterize after quantization — this is unavoidable in GIF. Enabling color reduction with dithering in the Colors option trades a stippled texture for smoother-looking gradients. If you need full color with the same autoplay-in-chat behavior, MPEG-2 to WebP keeps millions of colors and is usually far smaller.
No. GIF is an image format with no audio track, so the soundtrack is dropped. If sound matters, MPEG-2 to MP4 preserves the audio and plays inline on every modern platform. GIF earns its place precisely where silent autoplay is the point — email bodies, GitHub READMEs, and chat apps that mute or strip video.
10-15 FPS and 2-6 seconds is the sweet spot. GIF89a stores each frame's delay in hundredths of a second, so 25 FPS and 50 FPS are the cleanest high rates and 50 FPS is the practical ceiling — browsers won't render faster. Since most DVD/broadcast MPEG-2 was mastered around 25-30 FPS, dropping to 10-12 FPS for the GIF removes redundant frames you won't miss and meaningfully cuts file size.