GIF compressor for smaller animated files.

A GIF compressor reduces the bytes needed to store an animation. In this tool, reducing file size may require fewer colors, fewer frames or smaller dimensions. Pixel-identical lossless optimization is not guaranteed. Those changes affect the result differently: a smaller palette can introduce banding, skipping frames can make movement less smooth, and resizing reduces detail. Start with a modest change, compare the preview, then adjust the setting that matters least for your particular animation.

Check the file limit shown by your chat app, publishing tool or email platform before processing. Choose a target below that limit so you have room for differences in how services count file sizes. A target is a constraint, not a promise that every GIF can reach it at acceptable quality. If the current settings cannot produce a file within the target, reduce the dimensions or frame rate and try again. Only a result within the selected target should be treated as a successful target-size compression. In an engine test, our own 640 × 360 motion graphic (946,746 bytes, 120 frames, six seconds) became a 415,104-byte GIF with the 512 KB target, retaining its dimensions, frame count and duration. With a 256 KB target, it became 242,482 bytes at 582 × 327 px and 60 frames, still six seconds long. Results vary with the source and settings. For example, Discord custom emoji must be under 256KB, while X lists 5MB for GIF posts from mobile and 15MB from the web. These are destination requirements, not measured compression results; the sourced limits table below distinguishes each use.

Screen recordings with small text often benefit from keeping their original dimensions and reducing colors first. A looping reaction with fast movement may benefit more from keeping the frame rate and reducing its width. Inspect text, gradients, edges and the first-to-last frame transition before downloading. The smallest output is not automatically the best one: use the lightest settings that fit your destination and still communicate the original action.

Your selected file is processed in the browser rather than sent to a processing server. The first run may need to download the processing engine. Files up to 100 MB are accepted, but decoded frames can use much more memory than the original file. A large animation may fail on a phone even when it is below the input limit. Try a shorter or smaller source on a low-memory device. Local processing does not publish your file to a public gallery.