Is this ICO to PNG converter free?
Yes. This ICO to PNG converter is completely free with no sign-up or limits on how often you convert.
Does it upload my ICO file to a server?
No. The ICO is decoded, previewed, and exported to PNG entirely in your browser, so the file stays private on your device and is never uploaded.
Can I choose which embedded size to export?
Yes. The tool lists the icon sizes embedded in the ICO and lets you export the exact one you want, with the largest selected by default.
Does it support every legacy ICO encoding?
It supports PNG-backed entries and practical 32-bit BMP-backed icons, and it clearly reports any unsupported legacy variants it cannot decode.
Does the PNG keep transparency?
Yes. Where the source icon has an alpha channel, the exported PNG preserves transparency.
Which embedded size should I export?
The largest supported one, which the tool preselects, unless you specifically want the small artwork. Well-made icon files contain hand-drawn 16 and 32 pixel versions that are not merely downscales, and those are worth grabbing separately if you are rebuilding an old brand mark.
One of the entries says it is unsupported. What does that mean?
It means the entry uses a legacy encoding this decoder does not handle: usually a 4-bit or 8-bit palette bitmap. The tool supports PNG-compressed entries and 32-bit uncompressed BMP entries, and it reports anything else with a reason rather than exporting a broken image. Other entries in the same file are still exportable.
Is the exported PNG re-compressed?
Not if the entry was already a PNG. In that case the bytes are lifted out of the container untouched. Only BMP-backed entries go through a canvas, and those are re-encoded to PNG losslessly, so either way nothing is degraded.
Does transparency survive?
Yes. PNG entries keep their alpha channel directly. For 32-bit BMP entries the per-pixel alpha is read, and the separate 1-bit AND mask is applied on top, so pixels the mask marks as transparent come out transparent.
Is my icon file uploaded?
No. The container is parsed and every entry is decoded in your browser. This is useful when the icon came from a site or a binary you do not want to hand to a third-party converter.