Why your GIF is 40 MB and what actually shrinks it

Video codecs store one full picture and then, for the following frames, only what changed. GIF does nothing of the sort. Every frame is a complete image compressed on its own, like a flipbook where every page is fully drawn. Ten seconds at 15 frames per second is 150 complete pictures in one file. That is the entire mystery of the 40 MB GIF.

The three multipliers

• Frames: length times frame rate. Halving either halves the file. This is always the first lever.
• Pixels: width times height. Halving both dimensions cuts pixel count to a quarter, and the file shrinks almost as much.
• Colors: each frame carries a palette of up to 256 colors. Fewer palette entries mean better compression per frame, with 128 colors being invisible on most content.

What barely helps

Cropping a thin border, removing a handful of frames from the middle, or converting to GIF again at the same settings. People try these first because they feel safe, and they save single digit percentages. The big three above are where the mass lives.

A worked example

A screen recording GIF: 12 seconds, 30 fps, 1280 by 720, full palette, 48 MB. Trim to 6 seconds: 24 MB. Drop to 12 fps: about 10 MB. Scale to 640 wide: about 3 MB. Reduce to 128 colors: about 2 MB. Same content, 96 percent smaller, and each step took one slider.

Or stop fighting the format

If the destination plays video, convert the GIF to MP4 and get a file five to ten times smaller than even a well compressed GIF, with full color. Discord, Slack, Telegram, WhatsApp, X and every modern website handle MP4 loops natively.