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
Does my source format change how a crop behaves?
+
It can. ICO is a container that holds several square bitmaps at once (16, 32, 48, 64, 128 and 256 px) so Windows and browsers can pick the size they need. That decides whether the crop is a pure pixel operation or whether the file has to be rebuilt around it.
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.
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.
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.
Which sizes should the icon contain?
+
16, 32 and 48 pixels cover Windows Explorer and browser tabs; 256 covers large-icon view and modern shortcuts. Keeping all of them in one file costs almost nothing and stops the operating system from having to guess.
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.
Why does a Word site host Crop ICO?
+
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. Crop ICO shares the upload, the caps and the account with the conversions for that reason.
What should I do with the result once Crop ICO is finished?
+
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
Is Crop ICO here the same tool the sibling sites run?
+
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
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.
