An unoptimised animated GIF can easily reach 10–20 MB, which means slow page loads, high bandwidth usage, and frustrated users. The good news is that most GIFs contain a surprising amount of redundancy that can be removed without any visible quality loss. Here is exactly how to do it.
Why Are GIFs So Large?
GIF files are large for three main reasons:
1. One full palette per frame. Each frame can use up to 256 colours, and if the encoder isn't smart about reusing palettes, the file stores a separate colour table for every frame.
2. No inter-frame compression. Unlike video formats, standard GIF compression stores each frame mostly independently. There is basic LZW compression, but nothing like the motion-prediction compression used in MP4 or WebP.
3. High frame rates. A GIF at 25fps with 200 frames is storing 200 individual images. Halving the frame rate cuts the frame count in half.
Technique 1: Optimise the Colour Palette
The single most effective compression technique for GIF is palette optimisation. Instead of assigning a generic 256-colour palette to each frame, a smart encoder analyses the actual colours in the animation and builds a palette specific to that content.
For animations with limited colours (text, logos, simple graphics), you may only need 32 or 64 colours. Reducing the palette from 256 to 64 colours can shrink the file by 30–50% with no perceptible quality difference.
Additionally, difference-mode palette generation (stats_mode=diff) only analyses the changed pixels between frames rather than the full frame, producing a more accurate palette for animations with a static background.
Technique 2: Reduce the Frame Rate
Most GIFs look perfectly smooth at 12–15 fps. If you have a GIF that was exported at 25 or 30 fps, dropping it to 15 fps cuts the frame count nearly in half, and most viewers won't notice the difference.
Be careful with very fast motion — a walking animation at 8fps might look choppy, but a slow pan or a looping background effect at 12fps is often indistinguishable from 24fps.
Technique 3: Scale Down the Resolution
Resolution has a quadratic effect on file size — halving the width and height reduces the pixel count (and thus file size) to roughly one quarter. A 1280×720 GIF scaled to 640×360 is dramatically smaller and still looks sharp at typical web sizes.
Most GIFs don't need to be wider than 480–640px for standard web use. If you're embedding a GIF in a blog post or messaging app, 480px is usually more than enough.
Technique 4: Crop Unnecessary Space
If your GIF has empty margins or frames where nothing changes, trim them. Static borders and letterboxing add pixels without adding information.
Technique 5: Use Dithering Carefully
Dithering spreads quantisation error across neighbouring pixels to simulate colours not in the palette, which can improve perceived quality — but it also reduces compressibility, because dithered regions look random to the LZW encoder and compress poorly.
Bayer dithering at a moderate scale (bayer_scale=3) strikes the best balance: it adds just enough dithering to reduce banding without destroying compression. Avoid high-noise dithering algorithms if file size is your priority.
How Much Can You Actually Save?
Results vary by content, but typical savings are:
- Simple animation with static background: 50–70% reduction
- Complex animation with lots of motion: 20–40% reduction
- Photo-based animation: 15–30% reduction (consider converting to WebP instead)
Compress Your GIF Now
Convly's GIF Compressor applies all of the above techniques automatically — palette optimisation with difference-mode generation, bayer dithering at the right scale, and a safety net that returns the original file if re-encoding would make it larger (which can happen with already-optimised GIFs). Everything runs in your browser with no upload required.
If your GIF is still too large after compression, consider converting it to animated WebP — the format typically achieves 50–80% smaller files than GIF with better colour quality. Try the GIF to WebP converter →
Quick Checklist
Before publishing any animated GIF, run through this list:
- [ ] Is the resolution larger than necessary for its display size?
- [ ] Is the frame rate higher than 15fps? Could it be lower?
- [ ] Has a diff-mode colour palette been applied?
- [ ] Is the file size under 1 MB for web use, or under 8 MB for messaging apps?
- [ ] Could this work as a WebP or MP4 instead?
Small GIFs load fast, respect your users' data, and keep your Core Web Vitals scores healthy. It is worth the extra few seconds to optimise before publishing.