1Upload your GIF animations and wait for the preview to appear.
2Drag out the region you want to keep, or lock the selection to 1:1, 4:3 or 16:9 and drag freely inside that ratio.
3Confirm the crop — the same rectangle is applied to every file you uploaded, which is how a set ends up genuinely consistent.
4Download the cropped GIF file, with everything outside the frame discarded.
Crop GIF FAQ
Can I crop several files to the same region at once?
+
Yes, and that is the case worth doing here rather than in an editor: the same rectangle is applied across the batch, which is how a set of product shots ends up genuinely consistent instead of approximately consistent.
How does Crop GIF select and cut the area?
+
Concretely, the same rectangle is applied to every frame so the animation stays coherent, and frame delays and the loop count are carried across unchanged. You drag the region you want directly on the preview, or type exact pixel coordinates if you already know them.
Anything specific to GIF worth knowing before I crop?
+
Yes — the palette is shared across the whole animation, so any change to one frame is negotiated against the colours every other frame needs. That is the sort of detail that only shows up after you have overwritten the original.
What is the most common mistake when cropping GIF animations?
+
Cropping before resizing. Crop first from the full-resolution original, then resize the result — doing it the other way round means the region you keep has already lost detail it did not need to lose.
What can I upload to Crop GIF?
+
Animated and static GIFs, plus animated WebP. Still images work too and are treated as a single-frame animation, which is occasionally what you want when building one.
Is there a file size limit on Crop GIF?
+
Yes: free accounts process images up to 25 MB each, which is a real constraint for animation — a few seconds of full-frame GIF reaches that quickly. If an animation is over the limit, cutting the frame rate is almost always a better first move than cutting the dimensions — the eye forgives 12 fps far more readily than it forgives a smaller picture.
Will Crop GIF lower the quality of my GIF animations?
+
The binding constraint on a GIF is not the operation, it is the 256-colour palette. Anything that changes pixel values forces a re-quantisation against a palette shared by every frame, which is where banding and dithering come from. Frame timing and loop count are preserved.
Can I run Crop GIF on several GIF animations at once?
+
Yes, and it is worth doing — per-file overhead on an animation is dominated by decoding every frame, so a batch amortises far better than the equivalent set of single runs.
Why does a EPUB site host Crop GIF?
+
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Crop GIF runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once Crop GIF is finished?
+
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Crop GIF means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Crop GIF here the same tool the sibling sites run?
+
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.
