Resize GIF
Scale an animated GIF up or down, frame by frame — free, entirely on your device.
Drop a GIF here
Set new dimensions, then rebuild every frame
{{ errorMsg }}
How resizing an animated GIF works
Unlike a still image, a GIF is a sequence of frames. This tool decodes every frame of your GIF, redraws each one at the new width and height you choose, and re-encodes them back into a single animated file with the same timing. Lock proportions to scale without stretching, or uncheck it to set an exact width and height.
Shrinking a GIF is also one of the most effective ways to cut its file size, since fewer pixels means less data per frame — useful when a GIF is too large to attach to an email or message.
Choosing the right dimensions
Where a GIF is going to live should drive the size you pick. A reaction GIF dropped into a chat thread rarely needs to be wider than 300-400px, since messaging apps display it small anyway. A GIF embedded in a blog post or documentation page usually looks best between 480-720px wide, matching typical content column widths. Anything wider than 800px is rarely worth keeping as a GIF at all — video formats compress far more efficiently at that size, so consider the MP4 or WebM to GIF tools in reverse if you're starting from a large source.
Keep proportions locked unless you specifically want to stretch the animation — unlocking it and setting mismatched width and height will distort every frame, which is rarely the effect you're after. If your GIF has text baked into it, resizing down too aggressively can make that text unreadable, so preview the result before committing to the smallest option.
How this differs from resizing a still image
A regular photo resizer only ever touches one canvas, but a GIF resizer has to repeat that exact operation on every single frame — sometimes dozens of them — and then re-encode the whole sequence back into one file while preserving each frame's original timing. That's why this runs a dedicated GIF decoder and encoder rather than the simpler image tools used elsewhere on this site, and why very long GIFs with many frames take a moment longer to process than a single photo would.
All of that decoding, resizing and re-encoding happens locally using WebAssembly-accelerated libraries running in your browser tab — nothing about your GIF is ever sent anywhere else in the process.
Frequently asked questions
{{ item.a }}