Why GIFs are so big, and when a muted video is the better choice
A ten-second GIF of a video clip can be five times the size of the video, look worse, and stutter. That isn't a bug in your converter; it's the format, which was designed in 1987 for 256-colour images on dial-up and was never meant to hold video. This guide explains what's in a GIF, why it costs so much, and how the video-to-GIF tool and the GIF maker are set up to keep results sendable.
What a GIF actually is
The Graphics Interchange Format (CompuServe, 1987; the animated version in 1989) stores an image as an index into a palette of at most 256 colours, compressed losslessly with LZW — the same algorithm as early zip. Animation was a bolt-on: a GIF may hold many frames, each with a delay and an optional local palette, played in sequence, and since Netscape's extension, looped. Every frame is a full (or partial) image; there is no notion of motion, prediction or keyframes. It is, at heart, a flipbook of indexed bitmaps.
Why the file is so large
Video codecs store each frame as the difference from the previous one, a few percent of a full frame (How video compression works: bitrate, keyframes and codecs). GIF stores every frame whole, and LZW only helps where runs of identical pixels are long — flat cartoons compress well, photographs barely. So a 480-pixel, 15-frames-per-second, 10-second GIF holds 150 full frames of 480×270 pixels, and even at a few bits per pixel that's 5–15 MB, where the same clip as H.264 is under 1 MB. The 256-colour limit adds posterising and dithering on top. Frame count times frame size, with weak compression: that's the whole story.
Making a GIF small enough to send
- Short. Two to four seconds is the classic reaction length. Every second is 10–15 frames.
- Small. 320 px wide suits chats; 480 is the ceiling for anything sendable. Pixels are cost.
- Fewer frames. 10 fps looks fine for most content; 15 for fast action; never 30.
- Flat content compresses better. Screen recordings and cartoons stay small; grainy video balloons — noise is incompressible.
- Crop to the part that matters with the cropper first for still frames, or the trimmer for video.
Those are the defaults in the tools here for a reason: 3 seconds, 320 px, 10 fps produces the size messaging apps expect.
When a video beats a GIF
For anything over a few seconds, with sound, or with photographic detail, a muted looping MP4 or WebM is smaller by an order of magnitude and looks better — which is why Twitter, Imgur and Giphy all convert uploaded GIFs to video and merely call them GIFs. Use a real GIF when the destination only accepts GIFs (some chat apps, email, older forums, README files on code hosts), when transparency matters, or when the loop is a few frames of flat graphics. Otherwise trim and compress the video, or convert to MP4 with the MP4 converter, and send that.
What platforms do with your GIF
Most re-encode. WhatsApp and Telegram convert GIFs to MP4 on send; Slack and Discord cap file sizes (8–10 MB by default) and may downscale; email clients play GIFs but size limits apply; iMessage keeps the file. So the GIF you make is a source, and its main job is to be small enough to get through the first gate. GIF to PNG pulls a single frame out; the image compressor handles stills.
Sources and further reading
The claims in this guide rest on these references, which were checked when the guide was last updated. Spotted an error? The contact page says how to report it.