Guide · Formats
GIF or MP4?
The same three seconds of video is routinely ten times larger as a GIF than as an MP4 — and usually looks worse. Here is why, and the short list of places where the GIF is still the right call.
Updated 20 November 2026 · 6 min read
The gap, in one comparison
A three-second loop at 480 pixels wide comes out of this site at roughly 2–5 MB as a GIF. The same frames encoded as H.264 MP4 land nearer 200–500 KB. That is not an encoder trick: it is a difference in what the two formats are allowed to do. The GIF is a slideshow; the MP4 is a prediction engine.
Why GIF is so large
GIF was designed in 1987 to send small images over slow links, and it shows. Four limits do the damage:
- 256 colours per frame. A photograph has millions. The encoder has to approximate, and the approximation is visible as banding in skies and skin.
- Dithering makes it worse. To hide the banding, encoders scatter pixels of neighbouring colours — and that noise is close to random, which is exactly what a lossless compressor cannot squeeze.
- No motion prediction. MP4 stores “this block moved two pixels left”; GIF stores a complete picture for every frame, whatever changed.
- No real inter-frame coding. GIF can flag unchanged pixels as transparent, which helps a static shot, but it is a crude trick compared with the motion vectors in H.264 or VP9.
Do the arithmetic: a ten-second clip at 12 frames per second is 120 full frames. At 150 KB each — a normal figure for dithered 480 px video — that is 18 MB before any overhead. An MP4 of the same clip is typically under 2 MB.
Where a GIF still wins
The GIF’s advantage is not technical, it is social: it is an image. It renders inside an email client, a markdown file, a forum post, a support ticket and a chat app that would refuse or strip a video attachment. There are no controls to click, no codec to support and no autoplay policy to satisfy — it simply appears and moves.
It also loops by definition. The loop flag lives in the file, so the behaviour travels with it. An MP4 loops only when the app showing it decides to, which is fine on Discord and unpredictable in an email signature. And GIF supports transparency, albeit one-bit: a pixel is fully transparent or fully opaque, with hard edges that look right for logos and terrible for hair.
Where MP4 and WebM win
Everywhere the file is going to a modern app or a web page. A silent, looping MP4 is smaller, sharper, smoother and full-colour. WebM with VP9 goes further: another 20–40% smaller than H.264 at the same quality, for pages you host yourself. If there is sound, the argument is over — GIF has no audio track at all.
The one thing to check is mute. A looping MP4 should be silent anyway, and some platforms will not autoplay a file with an audio track. Muting it first costs seconds because the video stream is copied rather than re-encoded.
Which one for which destination
| Destination | Use | Why |
|---|---|---|
| Email signature, README, docs | GIF | Renders as an image. Many mail clients and markdown hosts strip or refuse video files. |
| Discord, Slack, iMessage | MP4 | These apps play MP4 inline, often with autoplay and looping, at a fraction of the GIF size. |
| X, Reddit, most social feeds | MP4 | X converts uploaded GIFs to MP4 for playback anyway; Reddit plays MP4 inline too. |
| A site you host | MP4 or WebM | Page weight is the whole argument. Ten times smaller means a faster page and less bandwidth. |
| A CMS that only accepts images | GIF | An animated GIF passes an image-upload filter; an MP4 does not get that far. |
| A short loop with real transparency | GIF or APNG | MP4 has no alpha. GIF gives one-bit transparency; APNG gives full alpha at a larger size. |
How to keep a GIF small
If a GIF is the only option, size is decided before encoding, not after. Five rules, in order of effect:
- Cut it short. Three seconds is a lot; six is usually too much. Time is linear in file size.
- Cut it narrow. 480 pixels wide is the usual compromise. Halving the width roughly quarters the pixels.
- Drop the frame rate. 12 fps reads as motion; 24 doubles the file for very little gain.
- Build the palette from the clip. A generic web palette is what makes cheap converters look washed out and banded.
- Crop to the subject. Empty background is paying rent in every frame.
The video-to-GIF tool does 12 fps, 480 px and a two-pass palette from your own clip, which handles the last two automatically. Trim first with thetrim tool if the source is longer than a few seconds.
Converting either way
Both directions run in the tab: video to GIF for the looping-image case, andGIF to MP4 when a 6 MB GIF should have been a 600 KB video. The MP4 is encoded with faststart so it begins immediately, and the colour banding disappears because the full palette is back.
Questions
Why is my GIF 20 MB?
GIF stores no motion prediction — every frame is a full picture with a 256-colour palette. A ten-second clip at 480 pixels wide is 120 frames, and even at 150 KB each that is 18 MB. Trimming to three seconds is the only reliable fix.
Is MP4 really smaller than GIF?
Routinely five to ten times smaller for the same animation. An MP4 stores the difference between frames, uses the full colour range and does not dither, so it is both smaller and smoother.
Do GIFs support transparency?
Yes, but one-bit: a pixel is either fully transparent or fully opaque, with hard edges. MP4 has no alpha channel at all. WebM can carry alpha, though player support is patchy.
Does converting a GIF to MP4 lose quality?
It usually looks better. MP4 keeps full colour, so the dithering and banding in the GIF are replaced by smooth gradients. The catch is that looping depends on the app showing it.
Will my MP4 loop automatically?
Only where the player does it. Browsers loop a muted MP4 if the page says so, and most chat apps loop short silent clips. A GIF carries its own loop flag, which is the one thing it does better.
More: all guides · which format to use ·every tool