Resize GIF — Exact Pixels or Percent, Ratio Locked

Type the width you want in pixels and, with the aspect ratio locked, the height fills in automatically so the GIF scales proportionally to your target resolution. If you'd rather not do the math, switch to percentage and scale the whole frame by a single number — say 50% to halve every dimension.

The resizer reads the original width and height the moment you load the GIF, so you always size against a known starting point. Lock the ratio for clean proportional scaling, or unlock it to stretch the frame to an exact width and height that don't match the original shape. Because the work runs through WebAssembly in your browser, every frame is scaled locally, and the output renders at the new dimensions when you export. If you want the file lighter after resizing, optimize the GIF's palette on the smaller canvas — fewer pixels per frame means less for it to encode.

Resizing scales the entire frame to a new width and height, so every pixel of the picture stays in shot — just smaller or larger — while cropping cuts pixels away from the edges to change what's actually in the frame. Resize keeps the whole composition; crop reframes it.

Reach for resize when the GIF is simply the wrong size for where it's going and you want to keep all of it. Use crop the GIF instead when you need to cut away borders or reframe an off-center subject. The two pair well: crop to the region you want, then resize that region to its final dimensions. Both, along with the palette and file-size tools, live in the same in-browser edit-and-optimize toolkit, so the GIF stays on your device the whole way through.

Scale with a quality-preserving resampler and keep the aspect ratio locked so the GIF never stretches — distortion, not size change, is what usually reads as lost quality. The Lanczos-quality resampler samples surrounding pixels as it redraws each frame, keeping edges sharp whether you downscale or upscale.

Downscaling is the friendlier direction: you're throwing pixels away, and a good resampler averages them cleanly, so a smaller GIF generally looks crisp. Upscaling has to invent detail that was never captured, so push it modestly and the resampler will smooth the new pixels rather than leave them blocky. One thing scaling can't fix is file weight — a GIF's 256-color palette still bloats it. If the resized GIF is still heavy, send it to the GIF compressor to hit a target size after the dimensions are set.

Yes — the resampler scales every frame in the sequence, not just one, so the frame count, timing, and loop flag all carry through and the animation plays back exactly as before, only at the new resolution. Nothing about the motion changes; only the pixel dimensions of each frame do.

That's the difference between resizing a still image and resizing a GIF: a GIF is a stack of frames, and a proper resize redraws the whole stack at the new width and height in one pass. Because the scaling runs locally through WebAssembly, the loop you started with is the loop you download — same animation, smaller or larger frame.