Reset to defaults
Need help?How to Re-encode a GIF Online
- Upload Your GIF Files: Drag and drop, or click "+ Add Files" to select one or more animated GIFs. Batch processing is supported — each file uses the settings you pick below.
- Set Image Quality (%): Switch File Compression to Custom and lower the quality slider to apply lossy re-encoding (Gifsicle-style). 100 keeps the source quality; 75 is a balanced default; 50 noticeably shrinks the file but introduces dithering noise.
- Reduce Colors and Frame Rate (Optional): In the same Custom group, drop the Colors dropdown from Original to 128, 64, 32, 16, 8, 4, or 2 — fewer entries shrink the palette index. Lower Framerate from the source (often 20-30 FPS) to 10 or 15 FPS to halve stored frames. Use Image Resolution to scale by percentage, set a preset (1080P, 720P, 480P, 360P, 240P, 144P), or enter custom width/height.
- Re-encode and Download: Click Convert. processing runs on our servers — no sign-up, no watermark, no upload to a third party.
Why Re-encode GIF to GIF?
The GIF container has been around since CompuServe's 87a release in 1987 (animation was added in the 89a revision in 1989) and is locked to 256 indexed colors per frame using LZW lossless compression. That makes the format inefficient compared with WebP or MP4, but also widely interoperable — every browser, every email client, every chat app accepts a .gif. A GIF-to-GIF re-export is the right move when you need to keep the file extension but shrink the payload, drop frames, or change dimensions:
- Discord free-tier uploads — Discord raised the free attachment cap from 10 MB to 20 MB in August 2026. Nitro Basic stays at 50 MB and full Nitro at 1 GB, but most users are on the free tier and a re-encoded GIF needs to clear the 20 MB ceiling.
- X (formerly Twitter) — accepts GIFs up to 15 MB on web, but mobile uploads commonly fail above 5 MB, and X transcodes everything to silent MP4 anyway. Trimming the palette to 64 colors and the framerate to 15 FPS usually lands the file under both caps.
- Slack message threads — Slack's 1 GB per-file ceiling rarely matters, but custom emoji are capped at 128 KB and 50 frames at 128x128 pixels; a re-encode is the only way to fit an existing animation into that envelope.
- Email signatures and newsletters — Outlook, Gmail, and Yahoo Mail clip attachments at 20-25 MB and many corporate gateways reject anything over 10 MB. A 4-color, 240p re-export keeps logo animations under 100 KB.
- Page-load and Core Web Vitals — large autoplay GIFs hurt Largest Contentful Paint scores. Cutting a hero animation from 8 MB to 800 KB is often the single biggest LCP win on a marketing page.
- Legacy device compatibility — older e-readers, kiosk displays, and digital photo frames support GIF but choke on dimensions above 720p or palettes above 128 colors; a re-encode rescales without changing the format the device expects.
If you can switch formats entirely, Convert GIF to MP4 or Convert GIF to WebP will produce a much smaller file at the same visual quality. Use Compress GIF for one-click size reduction, or Convert MP4 to GIF if you're going the other direction.
GIF Format — Why Re-encoding Helps
| Property | GIF (1989 89a) | Modern alternative |
|---|---|---|
| Color depth per frame | 256 indexed (8-bit palette) | WebP/AVIF: 24-bit truecolor |
| Compression | LZW lossless on indexed pixels | WebP: VP8 lossy or lossless; AVIF: AV1 |
| Animation | Frame-by-frame with delays | Same plus inter-frame prediction |
| Typical 5-second 480p clip | 3-8 MB | WebP 0.5-1.5 MB; MP4 0.2-0.8 MB |
| Browser support | Universal since 1995 | WebP: all modern browsers; AVIF: Chrome 85+, Firefox 113+, Safari 16.4+ |
| Best for | Reaction shots, simple icons, broad compatibility | Long animations, color-rich video clips |
Re-encoding Settings — Effect on File Size
| Setting change | Typical size reduction | Quality impact |
|---|---|---|
| Colors 256 to 128 | ~25-35% | Mild banding in gradients |
| Colors 256 to 64 | ~45-55% | Visible banding; OK for cartoons/text |
| Colors 256 to 16 | ~70-80% | Heavy posterization |
| Image Quality 100 to 75 | ~20-40% | Slight dithering noise |
| Image Quality 100 to 50 | ~50-65% | Noticeable noise on flat areas |
| Framerate 30 FPS to 15 FPS | ~50% | Choppier motion in fast clips |
| Framerate 30 FPS to 10 FPS | ~65% | Stuttery; acceptable for slideshows |
| Resolution 100% to 50% | ~70-75% | 4x fewer pixels |
Stacking changes is multiplicative — dropping to 64 colors, 15 FPS, and 75% resolution typically lands an 8 MB GIF under 1 MB. ezgif.com reports its Gifsicle-based lossy encoder achieves 30-50% reduction on the quality slider alone.
Frequently Asked Questions
Why would I re-export a GIF as a GIF instead of converting to MP4 or WebP?
Format compatibility. Discord, Slack, Outlook, Gmail, GitHub READMEs, and most CMS attachments accept .gif natively but will not autoplay .mp4 or sometimes reject .webp. If the destination requires a GIF extension, re-encoding is the only way to shrink the file. If the destination accepts MP4, switching formats is almost always smaller — a typical 5-second 480p clip drops from 3-8 MB to under 1 MB.
What does the Image Quality slider actually do on a GIF?
GIF itself is a lossless format on indexed pixels, so "quality" is implemented as lossy re-quantization before LZW compression (the same approach Gifsicle uses with --lossy). Lower values let the encoder approximate similar adjacent pixels with the same palette index, which compresses better but adds visible dithering noise. ezgif documents 30-50% file size reduction at the cost of "some dithering."
Will reducing colors to 16 or 32 break my GIF?
It will not break it — every GIF frame is already limited to 256 colors and many GIFs were exported at far fewer. The visible effect is posterization (smooth gradients become stepped bands). Cartoons, line art, screen recordings of text, and pixel-art animations tolerate 16-32 colors well. Photographic content or anything with skin tones, sunsets, or gradients should stay at 128 or 256.
What framerate should I pick?
Most source GIFs are recorded at 20-30 FPS. Dropping to 15 FPS halves the stored frames with almost no perceived change for talking-head or UI-demo content. 10 FPS works for slideshow-style animations. Below 10 FPS, fast motion becomes visibly choppy. The dropdown offers presets from 1 FPS up to 50 FPS.
Why is my re-encoded GIF still huge even at 64 colors?
Three likely causes. First, the source resolution is too large — a 1080p GIF starts at four times the pixel count of a 540p one. Use the resolution percentage slider or set a 480P or 360P preset. Second, the clip is long — GIF stores every frame independently (no inter-frame prediction), so 10 seconds at 30 FPS is 300 stored frames. Trim or drop framerate. Third, the content has high temporal change (rapid scene cuts, particle effects) — LZW cannot compress noisy difference across frames the way modern codecs do; switching to MP4 or WebP becomes worthwhile.
Does the tool preserve transparency?
Yes. The encoder keeps the source's transparency index intact. Note that GIF transparency is binary (a pixel is either fully transparent or fully opaque) — there is no alpha channel. If your source uses semi-transparent pixels (for example a PNG converted to GIF), they will be flattened to opaque against the background color.
How many files can I batch at once?
There is no fixed cap from this tool — upload a folder and each file is re-encoded with the same settings. For very large batches of 1080p multi-megabyte GIFs, upload and processing time is the practical limit. For 100+ files, run them in two or three smaller batches.
Will the re-encoded GIF play on older devices and email clients?
Yes. The output is a standard GIF89a file with LZW compression and one of the same palette sizes that have shipped since 1989. Every browser since Netscape, every email client, and every chat app that ever supported animated GIFs will play the re-encoded file. The only caveats are dimension limits on legacy hardware (older e-readers and kiosk displays sometimes cap at 800x600 or 1024x768).
Is the optimization done in the browser or on a server?
The optimization runs on our servers, not in your browser. Your files are uploaded over an encrypted connection, processed, and deleted automatically after a few hours. The tool runs without ads, sign-up, or watermarks, and there is no fixed file-count cap.