gif compressor

Local in-browser processing is the right call for files up to 50MB - skipping the upload round-trip makes this much faster than server-side compressors. Does the before/after preview help pick between Default and Smallest Size modes?

Having both a Default and a Smallest Size mode with a before/after size comparison is handy, especially for squeezing reaction GIFs under Discord's upload cap. Does Smallest Size work by reducing the color palette, dropping frames, or both? A target-size option like "fit under 8 MB" would make it even more practical for chat uploads.

This is a great tool for anyone who needs to shrink GIF files without losing too much quality. I love that it works right in the browser, keeps animations intact, and doesn’t require uploading files or creating an account. Perfect for sharing GIFs online and optimizing images for websites!

Since the GIF is processed locally in the browser, is there a practical size limit before it gets slow, given the 50 MB cap? Also curious how much quality the "Smallest Size" mode trades off versus Default.

I love that it works right in the browser

For product pages, keeping an animation small is only useful if details such as text and product colours remain clear. A side-by-side preview is a helpful feature here. Does compression preserve transparent backgrounds and the original animation timing? I would want to check both before adding a compressed GIF to a storefront.

Keeping it all in the browser with no upload is the right call for this kind of tool. The one option I looked for and couldn't find was resizing: when a GIF has to fit a chat or email limit, dropping from 800px to 480px wide usually saves more than any compression setting. A width option next to the two modes, plus a "download all" when you've done five files, would cover most of what I'd come back for.

Processing everything in the browser without uploading is a big plus. That's the first thing I check with file tools. The before/after size comparison is a nice touch. Would love to see a target-size option (e.g. "under 2 MB" for Discord or email) and batch compression for multiple GIFs; those are the two things I end up needing most.

Keeping the output as a real GIF instead of converting to video is the right call for chat and forum embeds that only accept .gif. Does the 50 MB limit apply to the input file or the compressed output, and does it stay responsive on GIFs with very high frame counts?

Processing locally in the browser and keeping the output a real animated GIF is a practical combo, and the before/after size readout makes the trade-off visible. Does Smallest Size mode reduce the palette, drop frames, or both? I'd find an optional max-width setting useful too, since resizing often saves more than extra compression.

Local-only processing is the part I trust most here. I build a desktop image compressor that never uploads anything, and once you've worked that way, sending a 40MB GIF to a server just to shrink it feels wrong. Two things I'd check if I were using this daily: whether Smallest Size drops frames or only quantizes the palette, and what happens on a GIF with a very high frame count — the 50MB cap says nothing about the frame ceiling. A max-width input would also save more than any compression setting on chat uploads.