I build LoopGIF.
You already have the animated GIF. It looks fine at its original width and height. Now it has to fit a new box: a square reaction slot, a narrow blog column, a template that asks for exact pixel dimensions. The tempting move is to type the new width and height, turn the aspect lock off, and Stretch the picture into the new shape. The file still loops. The mark does not look like itself: a wide wordmark becomes tall and thin. You changed the shape of every frame.
Fitting an already-made GIF to a new size is a geometry problem first and a file-size problem second. The two mistakes that do the most damage are stretching a picture into a different aspect ratio, and scaling a small original up as if extra pixels could invent detail that was never there.
Stretch changes the shape. Crop to fill keeps it.
When the aspect lock is on, you set one side and the other follows, rounded to whole pixels. The picture stays the same shape — the safe default when you are only changing scale.
When you need a different shape — usually a square from a wide or tall source — turn the lock off and set both sides yourself. Then you have two choices, and they are not interchangeable.
Stretch redraws the whole picture into the new box. Every frame is squeezed or pulled until it fits. If the source is wider than it is tall and the target is a square, the letters get taller relative to their width. That is what Stretch does, and it is the right choice only when distortion is what you want.
Crop to fill does the other job. It cuts the picture to the new aspect first, keeping a centred region, then scales that region to the target size. Letterforms stay in proportion. What you lose is whatever sat outside that centred cut — the left and right of a wide frame, or the top and bottom of a tall one.
The tool’s own published examples make the difference visible on the same wide source. A 480 × 270 GIF, run through the 128 × 128 emoji preset with Crop to fill, is cut to the middle 270 × 270 square and then scaled to 128 × 128. The file goes from 34 KB to 15 KB. The letters stay undistorted. The same source, with the lock off and Stretch on, squeezed into 256 × 256, goes from 34 KB to 32 KB — almost no change in bytes — and the letters look tall. The output size in pixels is not what wrecked the mark. The fill mode is.
The 128 × 128 and 256 × 256 emoji presets are built around that lesson. Both switch the aspect lock off and choose Crop to fill, so a wide or tall GIF is cut to a centred square and then scaled, rather than squeezed. After you download, open the result and check that the part you care about is still in the middle. If the mark sits off to one side in the original, a centred crop can clip it, and you will need to choose the square yourself before you scale.
Those two presets are usual starting points for a small square, not a promise that every app will accept the file. Apps set their own rules for dimensions, file size, and whether animation is allowed, and those rules change. Check the current guidelines of the app you upload to before you commit to a size. I am not going to quote a platform limit here, because any number I write will go stale.
Downscaling shrinks pixels and bytes. Upscaling does not add detail.
With the aspect lock on, making a GIF smaller is the reliable path. Half the width and half the height is a quarter of the pixels, so the file usually drops by more than half, and edges often look sharper at the new size because the picture has been reduced, not invented.
The page’s published examples:
- Scale by 50% with the lock on: 320 × 320 down to 160 × 160, 320 KB to 129 KB, 60% smaller, still 16 frames.
- Scale by 25% with the lock on: 480 × 270 down to 120 × 68, 130 KB to 17 KB, 87% smaller, 12 frames — a thumbnail-sized loop from a 480 px source.
If a GIF is simply too wide for a page, the 480 px wide and 640 px wide presets do the same kind of work. They bring a large loop down so it fits a blog column or an email, without changing its shape.
Upscaling goes the other way. The tool will do it, up to 1,024 pixels on the longer side, but it can only stretch the pixels it already has. The picture gets larger and a little soft, and the file grows. Nothing that was not in the original appears. Pixel art and hard-edged lettering suffer most.
One published example: a 360 × 240 GIF scaled up, aspect locked, to 480 × 320 with the 480 px wide preset. The file goes from 44 KB to 90 KB, 103% larger, and no new detail appears. If you need a bigger GIF, start from the largest original you have. You cannot recover sharpness that a small export already discarded.
Typing a number above 1,024 is not a way around the cap. The longer side is brought back to 1,024, and with the lock on, the other side follows. The output also cannot go below 8 pixels on a side.
The animation speed does not change. The palette might.
Resizing a GIF means redrawing every frame at the new size and writing those frames out as a new GIF. Each frame keeps its own delay, so the animation plays at the same speed with the same number of frames. You are not re-timing the loop. You are changing how large each picture is.
The result is a fresh encode, not a byte copy of the original. Colours are re-quantised to one shared palette of up to 255 colours plus transparency, with no dithering. Transparent GIFs stay transparent. Because it is a new encode, the file can come out smaller or larger than the source.
That is why the Smaller file tick is easy to misunderstand. It uses 127 colours and ignores tiny colour changes between frames. It is a palette and similarity trade, and it can make a lighter file. It is not a substitute for picking the right dimensions. If the GIF is too wide for the slot, shrink the pixels. If you stretched a wide source into a square, reducing the colour count will not unsquash the letters. If you need a particular size in kilobytes rather than a particular size in pixels, that is a compression problem, and a smaller palette will not always get you to a specific budget.
How to set the size without wrecking the mark
LoopGIF’s GIF resizer does this in the browser. It is free, requires no sign-up, and nothing is uploaded. There is no watermark. It accepts a GIF only, up to 25 MB and 300 frames, and it shows the current width, height, frame count and file size when you drop a file in.
From there the controls are straightforward:
- Type a width or a height, with the aspect lock on if you want the other side to follow.
- Or tap a scale chip: 25%, 50%, 75%, 150%, or 200%.
- Or use a preset: 128 × 128 emoji, 256 × 256 emoji, 480 px wide, or 640 px wide.
- If you turn the lock off, choose Stretch or Crop to fill before you run it.
- Tick Smaller file only if you want the 127-colour, ignore-tiny-changes encode.
Press Resize GIF. The new file appears next to the original, with its dimensions and the file size before and after, ready to download.
A practical order of decisions:
- Start from the largest original you have. Do not upscale a small export if a larger source still exists.
- If you only need a smaller version of the same shape, leave the aspect lock on and type a side, or use 25%, 50%, 75%, or a 480 / 640 px wide preset.
- If a template asks for an exact width and height that does not match the original aspect, turn the lock off and use Crop to fill so nothing is stretched. Then check that the part you care about is still in the middle.
- Use Stretch only when you actually want the picture to change shape.
- Treat Smaller file as a palette trade after the dimensions are right, not as the way to choose the size.
The work stays on your device: the GIF is opened, resized and encoded in the browser. Files with very large dimensions can be refused if they would not fit in memory. Current Chrome, Edge, Firefox and Safari are supported. Browsers that cannot decode GIFs natively use a built-in decoder, and the tool tells you which one it used.
You do not need a new GIF. You need the one you already have, at the size the layout actually uses, with the mark still the same shape it was when you made it.
I build LoopGIF.

