A GIF Weighs 20× More Than the Same Video. Fix It

You find the perfect GIF, drop it on your page or into a deck, and the file is 8 MB. For ten seconds of motion. That's not bad luck — that's the format.

GIF was never video

GIF shipped in 1987 for icons and simple animations. It caps out at 256 colours per frame and does no compression between frames at all. Every frame is stored almost in full. Video codecs do the opposite: write the first frame, then only what changed.

So the same ten-second clip comes out as 8 MB of GIF or roughly 350 kB of H.264 MP4. And the MP4 has full colour depth, so gradients stop looking like a contour map.

Where it actually hurts

Mobile. A single GIF on a product page can add two seconds to load time, and Google folds that straight into Core Web Vitals. In email most clients freeze it to the first frame anyway. In a deck it bloats the .pptx past the attachment limit.

Social platforms already solved this for themselves — Twitter, Discord and Slack all transcode uploaded GIFs to MP4 behind the scenes. You're just handing them a needlessly heavy source.

Converting without uploading

FileTools turns a GIF into MP4 right in the browser. Drag the file in, pick MP4, download. No account, nothing sent to someone else's server — the conversion runs on your machine.

For the web, add `autoplay muted loop playsinline` to the `<video>` tag and it behaves exactly like a GIF, at a twentieth of the weight.

When to keep the GIF

If you need animation inside an email or a system that can't render `<video>`, GIF is still the only path. There, at least trim the palette and keep it under three seconds.

Making video for several markets? TubeVoice dubs it into dozens of languages — and it obviously expects MP4, not GIF.

Take the three heaviest GIFs on your site and convert them. You'll see it in the metrics the same day.