Initializing... drag & drop files here
Supports: MPG, MPEG
The .mpg / .mpeg container holds either MPEG-1 (finalized November 1992, the codec behind Video CD and the MP3 audio layer) or MPEG-2 (the DVD-Video standard, also used for ATSC/DVB broadcast). Both are video codecs with audio — GIF strips the audio and emits a soundless looping animation that plays inline in every browser, chat client, email, forum post, and CMS without a player or autoplay permission.
| Property | MPG (MPEG-1 / MPEG-2) | GIF (GIF89a) |
|---|---|---|
| Type | Video container + codec | Indexed-color animated image |
| Standardized | MPEG-1: 1992 (ISO/IEC 11172). MPEG-2: 1995 (ISO/IEC 13818) | 1987 (87a static), 1989 (89a animation), CompuServe |
| Color depth | Full 24-bit YCbCr, 4:2:0 chroma | 256 colors per frame, drawn from 24-bit RGB |
| Compression | Lossy inter-frame (I/P/B frames) | Lossless LZW on the indexed palette |
| Typical bitrate | ~1.5 Mbit/s (MPEG-1 VCD), 3–15 Mbit/s (MPEG-2 DVD) | No fixed bitrate; size scales with frames × dimensions × palette |
| Audio | Yes (MP1/MP2/AAC) | None |
| Browser autoplay | Requires <video> and user gesture in many cases |
Plays inline in every browser, email, and chat client since the 1990s |
| Frame rate | Up to 60 fps (4:2:0); MPEG-2 supports interlace | Frame delay in 1/100 s; most browsers clamp delays ≤ 10 ms to 100 ms (~10 fps), and ≤ 20 ms is the effective floor for ~50 fps |
| Best for | Long-form playback, archival video | Short looping animations, reactions, UI demos |
| Setting | Effect on size | When to use |
|---|---|---|
| 5 FPS | Smallest; very choppy | Slideshow-style loops, ASCII-art animations, ≤200 KB targets |
| 10 FPS (default) | ~50% smaller than 20 FPS | Chat reactions, UI tutorials, the safe browser-cap default |
| 15 FPS | Smooth enough for most action | Sports highlights, gesture demos |
| 20 FPS | Cinematic feel, near the browser limit | Premium quality where size doesn't matter |
| 256 colors | Full GIF palette | Photographic content, gradients, skin tones |
| 128 colors | Roughly 25–30% smaller | Most live-action with mild dithering |
| 32–64 colors | 40–60% smaller | Stylized animation, line art, screen recordings |
| 8–16 colors | 60–80% smaller | Pixel art, monochrome loops, retro aesthetic |
| 320–480 px wide | 60–75% smaller than 720p | Slack, Discord, forum embeds |
| Duration ≤ 3 s | Linear with frame count | Reaction GIFs, meme loops |
If the result still feels too heavy, compress GIF re-optimizes the palette and frame delays, or convert to a modern container with GIF to WebP (often 60–90% smaller at the same visual quality) or GIF to MP4 for video platforms. Need to keep the audio or want a smaller universal-playback file from the same source? Use MPG to MP4 instead.
GIF stores every frame independently with LZW-compressed indexed color and no inter-frame prediction, while MPEG-1/2 only encodes the differences between frames (I, P, and B frames). A 5-second 480p MPEG-1 clip at 1.5 Mbit/s is roughly 950 KB; the same 5 seconds at 480p, 10 fps, 256 colors as GIF can land at 3–8 MB. To get back to MPEG-class size, cut to 2–3 seconds, drop to 320–480 px wide, lower the palette to 64 or 32 colors, and use 8–10 FPS.
For the GIF output, no — both decode to a sequence of frames before re-encoding to indexed color. It matters for what you can extract: MPEG-2 sources are usually 720×480 (NTSC DVD) or 720×576 (PAL DVD) interlaced at 29.97 or 25 fps, so the converter deinterlaces before frame extraction. MPEG-1 VCD sources are 352×240 / 352×288 progressive at ~1.15 Mbit/s, which is already close to GIF-friendly dimensions and converts faster.
Both Chromium and Firefox enforce a minimum frame delay: any frame requesting ≤ 10 ms (i.e., > 100 fps) is bumped to 100 ms (10 fps) for legacy compatibility with how 1990s GIFs were authored. The effective hard floor across modern browsers is about 20 ms (50 fps). If you encode at 30 or 60 fps the file size grows but actual playback may still cap at 50 fps. Stick to 10–20 FPS for predictable cross-browser playback.
Use the frame-selection controls in Advanced Options: "Specific Frame" grabs a single image at a timestamp (useful for a still poster), and "Multiple Frames" lets you set a range so a 90-minute MPEG-2 movie can output a 4-second loop. For finer trimming with timeline scrubbing, Video Trimmer cuts the MPG first and then you convert the trimmed clip.
No. GIF has no audio track — it predates audio-capable web image formats. If audio matters, convert to MP4 (which preserves the original AC3/MP2 stream) or to WebM. For silent visual content like UI captures, screen recordings, and reaction shots, GIF is fine.
MPEG-1 and MPEG-2 use 4:2:0 chroma subsampling, so color detail is already lower than the luma. Reducing to 128 or 64 colors usually shows much less visible banding than on a 4:4:4 source (uncompressed PNG sequence, ProRes, etc.). Live-action DVD content typically survives a 64-color palette with dithering; animated content (cartoons, motion graphics) often holds up at 16–32 colors.
DVD MPEG-2 uses non-square pixels — 720×480 stored, displayed as 640×480 (4:3) or 854×480 (16:9). The converter applies the aspect-ratio flag during decode so the GIF comes out at the correct display ratio. If your output looks horizontally squished or stretched, your source file is missing the aspect-ratio metadata; set Width × Height explicitly in Advanced Options.
Conversion runs in your browser session, so practical limits depend on your device's memory rather than a fixed cap. Older MPEG-1 VCDs at 352×240 convert in seconds. Full-length MPEG-2 DVD rips (often 4–8 GB) are slow to load and not recommended — trim to the segment you actually want first with Video Trimmer, then convert. No watermark and no sign-up regardless of size.
LICEcap and Gifski capture from your screen in real time, so they're limited to whatever's currently playing. This converter reads the MPG file directly, so quality is bounded only by the source codec (not screen DPI, refresh rate, or window size), and you can batch many files headlessly. For best-quality reaction GIFs, source-file conversion almost always beats screen capture.