Crop GIF animations

Drag a crop rectangle on the first frame — it is applied to every frame of the animation. The GIF you download still plays, with its original timing and looping.

Drop a GIF

Crop GIF — Free, Fast & Private

Cropping an animated GIF has a chicken-and-egg problem that cropping a photo does not: you need to draw a rectangle on something, but the something will not hold still. This tool resolves it the way a video editor would. The first frame is drawn as a still on a canvas, you drag and adjust the crop rectangle there — with edge masks, a rule-of-thirds grid, and eight resize handles, the same interaction as our photo cropper — and when you apply, the rectangle is cut from every frame of the animation. What you download is a GIF that still plays: same frame delays, same loop behaviour, transparency intact where the source had it. Nothing is uploaded at any point; parsing, cropping and re-encoding all happen on your device.

What people actually crop out of GIFs

The most common inputs here are screen recordings, and the most common job is removing the parts that were never meant to be in the shot: a browser tab bar, a desktop dock, a chat sidebar, a watermark parked in a corner, the ragged edge where the capture region overshot the window. A tight crop turns a sprawling "here is my whole screen" recording into a focused clip of the one interaction that matters — which is better communication and a smaller file in the same move. The other big category is reframing: cutting a wide meme or reaction GIF down to the face, or squaring off a rectangular animation for a platform that displays square. In every case the fix is geometric, so it costs no quality: pixels inside the rectangle are copied, pixels outside are dropped, and nothing is resampled.

Why the crop surface does not animate

It would be easy to show the moving GIF and let you drag over it — and miserable to use. Dragging a precise rectangle over moving pixels means committing to edges you can only see intermittently. So the crop surface is deliberately the first frame, frozen, with the frame count printed underneath as a reminder that the rest of the animation exists and will get the same treatment. One consequence worth knowing: if something you want to remove appears only in later frames — a popup halfway through a recording, say — it will not be visible while you drag. Position the rectangle from what you know about the clip, apply, and check the animated result; a second pass costs only seconds because there is no upload round-trip.

How a rectangle gets applied to two hundred frames

GIF frames are routinely stored as partial updates — just the changed pixels, plus an instruction for what happens to the previous frame's. Cropping each stored patch directly would produce garbage, because a patch's coordinates only mean anything relative to the full canvas. So the engine plays the GIF properly: each frame is composited onto a running full-size canvas, honouring the format's disposal modes, and the crop rectangle is then cut from that composite and re-encoded into the output. Every output frame gets a fresh colour palette fitted to what actually remains inside the rectangle — cropping away a colourful sidebar can genuinely improve how the remaining content quantizes. Frames stream through one at a time, which is how a 100 MB recording gets cropped inside a browser tab without exhausting its memory.

The file-size dividend

Cropping is usually done for framing, but it pays a size dividend: bytes scale with area, so trimming a quarter of the frame trims roughly a quarter of every frame's pixels, compounded across the whole animation. For screen recordings the effect is often better than proportional, because the discarded chrome — text-heavy sidebars, icon bars — tends to be exactly the high-detail content that quantizes expensively. If the cropped GIF is still too large for its destination, the next lever is width: resize the GIF down while keeping the animation, since crop and resize compose cleanly — crop first to fix the framing, then scale the result to the size the destination wants. A 500+ frame GIF takes a while through either tool, and the per-frame progress bar tells you the truth about how far along it is.

Still GIFs, and when you want a different tool

Not every .gif file animates. The tool reads the real frame count when you drop a file in and says plainly when it is looking at a single-frame GIF. Cropping one here works fine, but the still-image crop tool is the better home for that job — it offers aspect-ratio locks and lets you export to PNG, JPG or WebP instead of being confined to GIF output. Likewise, if what you are after is not trimming edges but shrinking the file wholesale, a static GIF is served by converting it to an efficient format. This page is for one specific, previously awkward job: cutting down an animation without killing it.

How it works

  1. Drop in your GIF: GIF only — the file’s actual bytes are verified, and the frame count, dimensions and duration appear before you commit to anything.
  2. Drag the crop on the first frame: The first frame is shown as a still — dragging over moving pixels is misery. Mask panels, a thirds grid and eight handles help you place the rectangle precisely.
  3. Apply to every frame: The chosen rectangle is cut from all frames, honouring the GIF’s partial-frame structure. A real per-frame progress bar tracks the work; long recordings take longer.
  4. Download the animated result: The output still plays — original frame delays, original loop count, transparency preserved where the source used it — just tighter and smaller.

Frequently asked questions

Does the cropped GIF keep its animation?
Yes. The crop rectangle you draw on the first frame is applied to every frame by a dedicated animated-GIF engine, and the result is re-encoded as a GIF with the original frame delays and loop count. Ordinary crop tools flatten a GIF to one frame because that is all a browser canvas decodes by default.
Why do I only see the first frame while cropping?
Deliberately — dragging a precise rectangle over moving pixels is unworkable. The first frame is frozen as the crop surface, and the readout beneath it confirms how many frames the crop will be applied to. If a later-frame element matters, place the crop from memory, apply, and check the result; retries are fast because nothing uploads.
Does cropping reduce the file size?
Yes, roughly in proportion to the area removed — the discarded pixels are dropped from every frame. Screen recordings often shrink better than proportionally, because trimmed UI chrome tends to be the detail-heavy content that costs the most to encode. For further reduction, resize the cropped GIF down as a second step.
Is any part of my GIF uploaded?
No. The GIF is parsed, composited, cropped and re-encoded entirely in your browser. No server sees the file, which also means no queue, no file-per-day cap, and retry-until-right costs nothing but seconds.
Can I crop and resize in one pass?
Not in one pass — this tool does exactly one thing to keep the interaction honest. Crop first, then feed the result to the GIF resizer. The operations compose cleanly: the crop fixes framing at full resolution, and the resize scales the framed result to your target width.
What happens with transparent GIFs?
If any source frame declares palette transparency, the output is written with a real transparent palette index — the transparent region stays transparent rather than turning black or white. Fully opaque GIFs are encoded without a transparency flag, exactly as they came in.
Why does a long recording take up to a minute?
Each frame must be composited (GIFs store partial updates), cropped and re-encoded individually — a 500-frame GIF is 500 rounds of real work on your own device. The tool warns you when the frame count is large, and the progress bar counts actual frames, not vibes.

All Image Tools

Solutions by use case