Back to blog

Article

Convert GIF to MP4 and Cut the File by 90% (Why GIFs Are So Huge)

A five-second GIF can be 10MB; MP4 is often under 1MB. Why GIF is so inefficient, when converting helps, and how to keep the original per-frame timing intact.

Convert GIF to MP4 and Cut the File by 90% (Why GIFs Are So Huge)

A five-second animated GIF routinely runs to 8–15 MB. The identical animation encoded as MP4 is usually under 1 MB.

That is not a rounding difference — it is roughly a factor of ten, and it is the reason X, Instagram and most modern websites quietly convert your GIF to video the moment you upload it.

This guide explains where that gap comes from, when converting is the right call, and the one detail most converters get wrong.

1. Why GIF files are so large

GIF’s compression was finalised in 1989. It has not changed since.

Two consequences follow, and together they explain the entire size problem:

GIF has no motion compression. Modern video codecs store the differences between frames — if 90% of the picture is identical to the previous frame, that 90% costs almost nothing. GIF has no such concept at the level that matters. Every frame is essentially stored as its own image.

GIF is limited to 256 colours per frame. To make a photographic scene look acceptable within 256 colours, encoders use dithering — scattering pixels of available colours to fake the missing ones. Dithering creates fine-grained noise, and noise is the hardest thing in the world to compress. The workaround for one limitation actively worsens the other.

H.264 has neither problem. It compresses across frames and handles millions of colours natively.

2. When to convert, and when not to

Convert to MP4 when:

  • The file is going on a website — a 10 MB GIF above the fold is a Core Web Vitals disaster
  • You are posting to X, Instagram or Reddit, which re-encode to video anyway
  • The animation is longer than about three seconds or contains photographic content
  • The file is being rejected for size

Keep the GIF when:

  • It is going in an email — most clients still will not play video, but they will animate a GIF
  • You need it to autoplay and loop with zero setup in a context you do not control
  • It is a tiny UI animation where the size difference is a few hundred kilobytes and not worth the trouble
  • The destination is a chat sticker slot that specifically expects GIF

The honest summary: GIF survives because of autoplay, looping and universal support — not because of quality or size.

3. The detail most converters get wrong: frame timing

Here is the part worth understanding, because it separates a good conversion from a mangled one.

GIF stores a separate delay for every single frame. A GIF is not required to have a constant frame rate, and in practice many do not — a hand-made GIF might hold the first frame for 2 seconds, run 12 frames at 40ms each, then hold the last for 1.5 seconds.

A naive converter reads only the frame count, assumes a constant rate, and re-times everything evenly. The result plays at the wrong speed, and any deliberate pause is destroyed.

A correct conversion reads each frame’s delay, builds the real timeline, and resamples that timeline at the output frame rate. The motion keeps its original rhythm.

Our GIF to MP4 converter does this — each frame’s delay is read individually and the timeline is rebuilt before encoding.

4. Converting a GIF, step by step

  1. Drop your GIF in. Frame count, per-frame delays and total duration are read locally.
  2. Pick a frame rate. 24fps is a good default. Going higher than the GIF’s own effective rate adds file size without adding information.
  3. Set the output size. 100% keeps the original dimensions. Scaling up is available but will not add detail.
  4. Choose a background colour. MP4 has no alpha channel, so if your GIF has transparent areas they get filled — black or white depending on where the video will sit.
  5. Set the repeat count if needed. Some platforms reject clips under three seconds. Repeating a short GIF two or three times is the simplest way past that.
  6. Convert and download.

5. Common questions

Will the MP4 still loop? Looping is a player setting, not something stored in the file. On a website, add the loop attribute to your <video> tag. On social platforms, short videos loop automatically. This is the main practical thing you give up by converting.

How much smaller will it actually be? For a typical animated GIF, expect 80–90%. In our own testing a 40-frame, 320×320 GIF went from 820 KB to 87 KB — an 89% reduction with no visible quality loss. Photographic GIFs save the most; flat-colour animations save less because GIF handles those relatively well.

Does converting lose quality? Usually it improves perceived quality. The GIF was already quantised to 256 colours and dithered; MP4 does not reintroduce the lost colours, but it does not add another 256-colour pass either, and the dither noise compresses away.

Can I convert MP4 back to GIF? Yes, though you will pay the size penalty again. Our video to GIF converter handles that direction with control over frame rate, width and dithering.

Why is my output WebM instead of MP4? H.264 encoding depends on the browser. Firefox and some Linux builds do not provide it, so the converter falls back to WebM with VP9, which plays everywhere except older Safari.