Got a bloated GIF that's too big to post? Re-encode it at lower FPS or width to shrink it — in your browser, with the output size shown before you download.
Loading FFmpeg Core... (This may take a moment)
Files are processed locally and never uploaded.
Drop your oversized GIF into the uploader above — it never leaves your device.
The sliders start at 10 FPS / 480px; lower either one to shrink the file.
Check the new output size next to the download button, then download the smaller GIF.
GIFs bloat for predictable reasons: too many frames (30 FPS source), too many pixels (1080p source), too many seconds (a 20-second "GIF"), or too much visual noise (confetti, film grain, camera shake — the format compresses noise terribly). A GIF with all four problems can weigh 50MB while saying nothing a 3MB version couldn't.
Most bloated GIFs arrive second-hand: downloaded from a converter that defaulted to max quality, exported from a video editor at full resolution, or screen-captured at 60fps. The original video is long gone, so re-encoding the GIF itself is the only practical fix — which is exactly what this page does.
This page treats your GIF as a video source and re-encodes it at the FPS and width you choose. Dropping 30 FPS to 10 cuts roughly two-thirds of the frames; narrowing 1080px to 480px cuts over three-quarters of the pixels. Combined, a 40MB GIF routinely becomes 3–5MB — small enough for Discord, Slack, and forums.
The honest trade: re-encoding is lossy. Motion gets choppier below ~8 FPS, fine detail softens as width drops, and GIF's 256-color palette gets re-quantized, which can add banding to gradients that were smooth in the bloated original. Start at the page defaults (10 FPS / 480px) and only go lower while the GIF still looks like itself.
Before touching quality, ask whether the GIF needs all its seconds. Trimming a 12-second GIF to its best 4 seconds cuts the size by two-thirds with zero visual loss — no other setting comes close. If your GIF tool can't trim, this is the moment to go back to the original video and re-export just the good part.
Which brings up the real advice: whenever you still have the source video, re-convert from that instead of re-encoding the GIF. Every GIF generation loses color information; re-encoding a GIF is a second lossy generation. The page accepts MP4, MOV, and WebM for exactly this reason — the video is always the better starting point.
The FPS slider sets how many frames per second the output keeps; the width slider sets the output pixel width (aspect ratio preserved). The preset starts both at sensible middle values — 10 FPS, 480px — rather than the extremes, so your first conversion is usually close to right.
What the sliders don't do: there's no automatic "make it exactly 2MB" mode, and no magic that keeps full quality at a tenth of the size. The output size shown next to the download button is the real number — iterate on the sliders until it fits your platform's limit, checking the preview each time.
Know your target before you compress: Discord free uploads cap at 8MB, Slack at 1GB (but large GIFs won't animate inline well past ~20MB), most forums cap attachments at 2–8MB, and email providers start rejecting or refusing to animate GIFs past a few megabytes. iMessage handles large GIFs fine; WhatsApp compresses them into videos anyway.
A practical rule: aim for half your platform's limit. A 4MB GIF posts instantly on an 8MB-limit platform; an 7.9MB GIF on the same platform uploads slowly and sometimes fails on flaky connections. The size preview on this page makes targeting easy — convert, read the number, adjust, repeat.
At 10 FPS / 480px, most GIFs look essentially the same at a fraction of the size. Quality visibly drops below ~8 FPS (choppy motion) or under ~320px wide (soft detail). The trick is stopping at the first settings that fit your size limit — don't compress further than you need to.
No — and be suspicious of tools that claim to. This page shows you the exact output size after each conversion so you can iterate the sliders until it fits. Usually one or two tries gets you under Discord's 8MB or any forum limit.
Re-convert from the video whenever you still have it — it's a first-generation encode with full color information. Re-encoding an existing GIF is a second lossy generation. Use this page for GIFs whose source video is gone (downloaded GIFs, old captures).
Usually it's duration: a 20-second GIF at any reasonable quality is still huge. Trim to the essential seconds first. If it's already short, the content may be inherently noisy (confetti, grain, shaky camera) — GIF compresses noise terribly, and the only fix is lower FPS/width or accepting a bigger file.