1Upload your ICO icons 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 ICO file, with everything outside the frame discarded.
Crop ICO 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 ICO select and cut the area?
+
Concretely, the crop is applied to each bitmap in the stack and the entries are re-squared afterwards, because a non-square icon entry is not a valid icon entry. You drag the region you want directly on the preview, or type exact pixel coordinates if you already know them.
Anything specific to ICO worth knowing before I crop?
+
Yes — an ICO is a stack of square bitmaps, not one image, so operations apply to the stack and Windows still picks whichever size it wants. That is the sort of detail that only shows up after you have overwritten the original.
What is the most common mistake when cropping ICO icons?
+
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 ICO?
+
ICO files containing one or several sizes, plus ordinary PNG or JPG artwork if you are building an icon rather than editing one. Windows .ico and browser favicon files are the same format.
Is there a file size limit on Crop ICO?
+
Yes: free accounts process images up to 5 MB each, which no icon file will ever approach — a full 16-to-256-pixel stack is typically well under 200 KB. Icons are the one part of the image family where the cap is genuinely irrelevant.
Will Crop ICO lower the quality of my ICO icons?
+
The sizes stored inside an ICO are lossless bitmaps, so the pixels themselves do not degrade. What actually decides how good an icon looks is whether the size the operating system asks for exists in the stack — a 256 px entry downscaled on the fly by Windows always looks worse than a real 32 px entry.
Can I run Crop ICO on several ICO icons at once?
+
Yes. Icon files are tiny, so a batch of them completes almost instantly; the round trip is dominated by the upload, not the processing.
Why does a EPUB site host Crop ICO?
+
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 ICO 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 ICO 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 ICO means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Crop ICO 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.
