Converting ICO to PNG extracts the largest icon image to a lossless format with proper alpha support. This is the standard way to edit an icon: extract to PNG, edit in a design tool, then re-pack to ICO.
Drag & drop image files here, or browse
Drop your ICO files here
Lossless conversion preserving alpha transparency and all pixel data from the largest ICO size. Other embedded sizes are not preserved unless the tool explicitly exports them separately.
PNG is supported everywhere: every browser, OS, and image tool.
ICO is the Windows icon format. A single .ico file can hold multiple resolutions (16×16, 32×32, 48×48, 256×256) and color depths simultaneously, letting the OS pick the best for context. Every browser serves favicons as ICO, and Windows desktop icons use it natively.
PNG is a lossless image format designed to replace GIF. It uses DEFLATE compression, supports an 8-bit alpha channel for full transparency, and preserves every pixel exactly. PNG excels at images with sharp edges, large flat-color regions, text, UI screenshots, and anything you'll re-edit.
The largest size in the ICO, typically 256×256. If the ICO only has smaller sizes (16, 32, 48), the largest available is used.
Yes. PNG fully preserves ICO's alpha channel including soft anti-aliased edges.
ICO is the Windows icon format. A single .ico file can hold multiple resolutions (16×16, 32×32, 48×48, 256×256) and color depths simultaneously, letting the OS pick the best for context. Every browser serves favicons as ICO, and Windows desktop icons use it natively.
PNG is a lossless image format designed to replace GIF. It uses DEFLATE compression, supports an 8-bit alpha channel for full transparency, and preserves every pixel exactly. PNG excels at images with sharp edges, large flat-color regions, text, UI screenshots, and anything you'll re-edit.
Yes. The converter runs entirely in your browser using WebAssembly. Your images are never uploaded, never sent to a server, and never leave your device.
There's no hard limit, but because everything runs in your browser you're bounded by available memory. Very large images (over a few hundred megapixels) can hit browser memory limits. Process in smaller batches if you run into issues.