Initializing... drag & drop files here
Supports: GIF
Animated GIF is a 1987 format that stores each frame as a 256-colour palettised image and re-encodes the palette per frame. Modern video codecs (H.264, H.265, VP9, AV1) use motion-compensated, perceptually-coded compression — for the same animation, the video file is routinely 10-20x smaller while showing millions of colours, smoother gradients, and no dithering. Google's own web.dev guide cites a 3.7 MB GIF shrinking to 551 KB as MP4 (85% reduction) and 341 KB as WebM (91% reduction) on the same source clip.
<video autoplay loop muted playsinline> instead of GIFs. Browser autoplay restrictions don't apply when audio is muted or absent. Generate both WebM and MP4, list WebM first, and the browser picks whichever it supports — WebM globally sits at ~95.7% support per caniuse, MP4 at ~96%+.| Output container | Default codec here | Typical 5s 720p file size | Best for | Watch out for |
|---|---|---|---|---|
| MP4 | H.264 | 300-800 KB | Social media, messaging, email, smart TVs, anything cross-platform | None — this is the safe default |
| WebM | VP9 | 200-600 KB | Self-hosted web video, <video> embeds in HTML5 |
Safari before 16.0 macOS / 17.4 iOS lacks playback |
| MOV | H.264 | 350-900 KB | iMovie, Final Cut Pro, QuickTime, Adobe Premiere on Mac | Slightly larger MP4 with extra Apple metadata |
| AVI | MPEG-4 / MJPEG | 1-5 MB | Legacy Windows tools, VirtualDub, very old hardware | 2-5x larger than MP4 for similar quality |
| MKV | H.264 | 300-800 KB | Open container, multi-track / subtitle workflows | Not natively supported on iOS / Safari |
Recommendation: MP4 for sharing. WebM for web embedding. MOV for Mac editing. Skip AVI unless a specific legacy tool requires it.
| Property | GIF | MP4 (H.264) | WebM (VP9) | MOV (H.264) |
|---|---|---|---|---|
| Year released | 1987 | 2003 | 2010 | 1991 |
| Colours per frame | 256 (palettised) | ~16.7M (8-bit YUV) | ~16.7M (8-bit YUV) | ~16.7M (8-bit YUV) |
| Audio track | Not supported | Supported (AAC) | Supported (Opus / Vorbis) | Supported (AAC) |
| Native loop flag | Yes (Netscape extension) | No — set via <video loop> |
No — set via <video loop> |
No — set via <video loop> |
| Transparency | 1-bit (on / off) | None | Alpha channel (VP9) | None (standard); ProRes 4444 supports alpha |
| Typical 5s 720p clip | 8-20 MB | 300-800 KB | 200-600 KB | 350-900 KB |
| Global browser support | 100% | ~96%+ | ~95.7% (Safari 16+) | Playback via QuickTime / Safari |
| Best for | Sub-2s reactions, tiny pixel art | Cross-platform sharing | HTML5 web embeds | Mac editing workflows |
GIF has three behaviours that don't survive intact into video. Here's what each output does with them.
| Source GIF feature | MP4 / MOV (H.264) | WebM (VP9) | AVI / MKV (H.264) |
|---|---|---|---|
| Loop flag (Netscape extension) | Dropped — set <video loop> in HTML |
Dropped — set <video loop> in HTML |
Dropped — player must loop |
| Audio (GIF has none) | Silent — no track written | Silent — no track written | Silent — no track written |
| 1-bit transparency | Filled with Background Colour (black default) | Preserved as alpha (VP9 with alpha) | Filled with Background Colour |
| Variable frame timing | Resampled to nearest standard fps | Resampled to nearest standard fps | Resampled to nearest standard fps |
If transparency matters, pick WebM. If portability matters, pick MP4 and set Background Colour to match your page.
MP4 with H.264 is the safe default — it plays on every modern device, social platform, and messaging app. Pick WebM (VP9) when you control the embedding HTML and want the smallest file; it saves ~20-30% over H.264 at the same quality but Safari only added support in macOS 16.0 (2022) and iOS 17.4 (2024). Pick MOV when your downstream tool is iMovie, Final Cut Pro, QuickTime, or Adobe Premiere on Mac — the container is essentially the same H.264 payload as MP4 with extra Apple metadata.
Video containers don't carry GIF's loop flag, so looping becomes the player's job. On the web, add the loop attribute: <video autoplay loop muted playsinline>. Twitter / X, Discord, Reddit, and Slack auto-loop short uploaded videos (under ~30 seconds) the same way they treat short GIFs. Standalone players like VLC or QuickTime need loop enabled manually. The xconvert converter doesn't write a loop count into the output because no major video container supports one.
No — animated GIFs cannot store audio, so the output video has no audio track at all (not even a silent one). This is actually useful: browser autoplay rules treat audio-free video the same way they treat GIFs, which is why <video autoplay loop muted playsinline> plays without user interaction. If you need sound, add it afterwards in a video editor.
For typical screen-recording or animation GIFs above ~500 KB, expect a 10-20x reduction (i.e., 85-95% smaller). Google's web.dev cites a 3.7 MB GIF becoming 551 KB as MP4 (85% smaller) and 341 KB as WebM (91% smaller). Tiny GIFs under ~50 KB may actually be larger as video because of container and keyframe overhead — for those, compress GIF directly is the better choice.
Only in WebM. GIF transparency is 1-bit (a pixel is either fully transparent or fully opaque). Standard MP4 / MOV / AVI / MKV with H.264 have no alpha channel, so transparent regions get filled with the Background Colour you pick (black by default — change it in Advanced Options). WebM with VP9 supports an alpha channel, which most modern browsers respect when the video is embedded with the right markup.
xconvert reads the source GIF's frame timing and produces video at the closest standard frame rate — most GIFs are authored at 10, 15, 20, 24, or 25 fps, so the output usually matches the source exactly. GIFs with unusual or variable per-frame delays are resampled to the nearest standard fps to avoid judder. You can override the output rate if you need a specific value, but matching the source is the default for a reason.
For a GIF replacement, stick with H.264. H.265 / HEVC produces ~30-50% smaller files at the same quality, but it has weaker browser support — Safari plays it, Chrome and Firefox on desktop largely don't without hardware decode. H.264 is the right default whenever the video is meant to "play everywhere". H.265 is worth picking only when you control the playback environment (e.g., an iOS app, an Apple TV deployment).
Video containers carry minimum overhead — headers, metadata, keyframes, codec startup. For GIFs under ~50 KB, the MP4 / WebM may be larger or only marginally smaller than the source. The 10-20x savings kick in above ~500 KB of GIF, and dominate above 2 MB. If your input is already tiny, you're past the point where converting helps — keep the GIF or compress it directly.
Yes — drop multiple GIFs into the uploader. Every file uses the same output format, quality preset, and resolution settings, which is what you want for a batch (consistent encoding across a set of clips for a tutorial, marketing deck, or article). Each file downloads individually after conversion completes; pair with video to GIF for the reverse direction.