GIF Compressor
Shrink animated or static GIFs to fit Slack, Discord, email, or CMS limits without uploading them to a third-party server.
Drop files or a folder here
or click to browse · paste from clipboard
Accepts .GIF · Up to 1,000 files
Browser-based GIF Compressor. Nothing Uploads
How it works
Drop your files
Drag and drop, click to browse, or paste from clipboard. Up to 1,000 files at once.
Choose settings
Choose compression level, or a target size. If you need more control, use the advanced settings for more control.
Click Compress
Everything runs in your browser via WebAssembly. GIF Compressor happens locally — nothing is uploaded.
Download
Download files individually or grab all at once as a ZIP.
Compress large GIF files down to a size that you can send. Open or drop your files, choose the correct setting, and download. Everything is processed in the browser, and nothing is uploaded.
What is a GIF and what does this tool do?
To help you better understand what this tool does, let me first explain how a GIF works. Imagine a flipbook: a bunch of hand-drawn or graphic pages stacked on top of each other. As you flip through these pages rapidly, it creates an illusion of movement. That basically is a GIF image, but in a digital format.
One issue with GIF files is that their file size gets bloated the more image stills you add. The more complex the movement, the larger it gets, making it difficult to send, whether on Discord or email. If you’re using these GIFs on a website, the large footprint will affect your website loading speed negatively. One solution would be to use the WebP format (Convertyard has a GIF-to-WebP converter) to convert the GIF to a more efficient file format, or, if the CMS you’re using doesn’t support WebP, you’ll need to compress the GIF.
What to expect?
- Animated GIFs will be compressed between 30 and 80%, based on tests. But take note that at 80% compression, there will be noticeable quality loss.
- Non-animated (or still) GIFs will be compressed between 30 and 60%. Again, these are based on my tests, and the aggressive option will have noticeable quality degradation.
- Animation will play at the same speed (no frames are removed).
- Users will see a side-by-side preview before the compression, so they can adjust the settings and preview the result.
- If you need more compression, I suggest using the WebP file format, which offers better compression. Check the GIF-to-WebP converter.
The compression options (explainer)
There are four presets. Select one and go. There’s no need to touch anything else.
| Preset | What it does | When to use it |
|---|---|---|
| Light | Barely touches the GIF. You won’t see any change. | When quality matters more than size. |
| Balanced (default) | Big size drop, still looks great. | Almost every situation. Start here. |
| Strong | Smaller file, uses fewer colors. Slight banding on smooth gradients. | When Balanced isn’t small enough. |
| Extreme | Drops every other frame so the file is much smaller. Motion looks a little choppier. | When you really need it tiny and choppy motion is okay. |
Another option is selecting a target size if you need to compress a GIF to a specific number. Select a preset between 256 KB and 8 MB, or type a custom size.
Disclaimer: This doesn’t guarantee that the tool will compress the file to that exact size, but it tries to get close to it. That’s how this compressor was programmed to maintain GIF quality.
This is handy if you need to use platforms like Slack (8 MB free plan limit) or Discord (10 MB per file limit), or send the GIF file as an email attachment (10 to 25 MB depending on provider and server settings).
Manual controls (for users who love to tweak)
Turn on the “manual settings” if you want full control of the compression. Here’s what each slider does in plain English.
- Lossy level (0–200): Think of this setting as a compressor dial. A higher number equates to a smaller file size. However, anything past 140, you’ll see blocky patches in smooth areas like gradients. The sweet spot for compression and quality is 80.
- Palette size (32–256 colors): GIF files can use a maximum of 256 colors. Fewer colors mean a smaller file, but the smooth transitions can turn into pixelated stripes. Select 256 if you want to maintain image quality. Lowering it to 32 will make it look like an old poster.
- Frame drop: As I said in the intro, GIFs function like flipbooks. Removing every other image in this flipbook reduces the file size by half. The animation plays at roughly the same speed, but the movement isn’t as smooth — it skips.
- Dither: Using fewer colors can create ugly spots, usually on the hands, skin, sky, or shadows. Dither sprinkles tiny dots into these areas to hide those ugly spots. File size will be bigger, but the gradients will look smoother.
How does GIF compression actually work?
To understand GIF compression, let’s first look at the components of a GIF.
- Frames (or pictures)
- Color palette (or colors it’s allowed to use)
- Frame rate (how long each photo stays on screen)
To compress an animated GIF, we need to squeeze one or more of these:
- Reuse pixels across all frames: In most animations, there are portions of an image that don’t change (like the background). So we tell the file to “keep whatever is there before” instead of storing the pixels again. This is called “lossy interframe compression,” and it’s where the most file savings come from.
- Use fewer colors: GIF selects from a color palette. Reducing 256 to 128 colors cuts the file size in half. Choosing a lower setting offers more savings, but the image starts to look clunky.
- Drop some frames: For example, the animated GIF has 30 frames; retaining only 15 of them cuts the file size in half. The animation will run at the same speed, but has fewer pages on the “flipbook.”
Under the hood, this tool uses a WebAssembly version of “gifsicle.” It’s the same code most professional GIF optimizers use. The only difference is that this one runs in the browser instead of on a server.
Why does “in your browser” matter?
Most free GIF compressors I see online upload your files to the server, compress them there, then you download the compressed version, and this means:
- Your animation is stored on a stranger’s computer.
- You have to wait for the file to upload, then download.
- Large files hit a file size cap.
- Your files are exposed in case of a data breach.
ConvertYard compresses GIF animations inside the browser. So nothing is uploaded to a server. It’s faster and works on larger files as long as your computer’s video processor memory can handle (usually a few hundred megabytes).
Frequently asked questions
Lossy compression removes visually similar pixel data across frames — the workhorse setting, and the one that produces the biggest savings with the least visible loss. Palette size reduces the total colors used across the whole GIF; lower counts make files smaller but cause banding on gradients. Frame drop removes evenly-spaced frames, which halves or thirds the file size at the cost of choppier motion. The Balanced preset uses lossy=80 with the full 256-color palette and no frame drop — the sweet spot for most GIFs.
Yes. Compression preserves all animation timing, loop count, and disposal methods. The output plays back at exactly the same speed as the original. The only preset that changes motion is Extreme, which drops every other frame to shave file size — that trade-off is called out in the interface before you compress.
For animated GIFs at the Balanced preset, expect 40–70% file-size reduction with no visible quality difference. Static GIFs (single-frame) usually reduce 15–35%. Strong and Extreme presets can hit 80–90% but the loss becomes visible on gradients and skin tones. If you need more than 90% savings on an animated GIF, convert it to MP4 or WebP — those formats are 10–20× more efficient than the GIF container itself.
Up to 1,000 files per batch. Individual file size is limited only by your browser’s memory — in practice, GIFs above 200 MB may run slowly or fail on lower-end laptops. Files are processed in parallel up to your device’s CPU count (capped at 4 concurrent) to keep memory usage predictable.
If you’re embedding on a website or in an app that plays video, yes — MP4 is roughly 10× smaller than an optimized GIF at the same visual quality. The only reasons to keep the .gif extension are platform requirements (some chat apps, older CMSes, or email clients that don’t autoplay video). If either works, use the GIF to MP4 tool instead of this one — the file will load faster and look better.
Two things cause visible artifacts: high lossy values (over 140) throw away too much inter-frame detail, so gradients get blocky. Small palette sizes (under 128 colors) cause color banding — smooth transitions turn into visible steps. Turning on Dither adds subtle noise that hides banding at the cost of a slightly larger file. Drop to a lower preset or reduce the lossy slider by 20–40 to fix the graininess.
Yes. Static GIFs use the same lossy and palette-reduction settings and typically shrink by 15–35%. Compression is less dramatic than for animated GIFs because there’s no cross-frame redundancy to exploit. If the static GIF has photographic content, converting to WebP or JPG will produce much smaller files than keeping it as a GIF.
No. Compression runs entirely in your browser using a WebAssembly build of gifsicle — the same tool most command-line optimizers use. Files never leave your device; the server delivers the tool’s code and nothing else. ConvertYard has no upload endpoint, no queue, and no way to store what you compress.