ICO is a container format built specifically for Windows icons and favicons, not a general purpose image format, so most everyday image tools cannot open one directly. A ico to png converter exists for exactly that gap: turning a file built for taskbar icons and browser tabs into a PNG that any editor, slideshow tool or content management system can read without complaint.
The conversion is entirely local. Your browser already knows how to decode ICO files, since it is the same file type used for favicon.ico, so this tool simply asks the browser to draw that decoded icon onto a canvas and export the pixels as PNG, without ever sending the file to a server.
What happens when a taskbar icon meets software that never heard of .ico
The most common reason is needing to edit or reuse an icon in software that has no idea what a .ico file is. Design tools, presentation software and most mobile apps expect PNG or JPG, so an icon extracted from an old application or downloaded as a favicon needs converting before it can be dropped into a design.
It also comes up when rebuilding a favicon set from an inherited file. Many sites still ship a single favicon.ico from years ago, and converting that favicon to png is the first step toward regenerating a full modern icon set at several sizes.
- Convert to PNG when you need to edit the icon in ordinary image software.
- Convert to PNG when uploading the icon somewhere that does not accept .ico files.
- Convert to PNG to extract icon as png before rebuilding a modern favicon set.
- Keep the ICO file itself if the destination is specifically a Windows executable or a legacy favicon slot.
- Check the exported pixel dimensions match what you expect, since ICO files can bundle more than one size.
What actually happens when a browser decodes an ICO file
A single ICO file can bundle several versions of the same icon at different resolutions, from a tiny 16 by 16 pixel version for a taskbar up to 256 by 256 for a high resolution shortcut. Browsers decode ICO files natively through the standard image element, exactly the way they load favicon.ico, and they choose one of the embedded images to display rather than exposing every size at once.
In practice this means the PNG this tool produces reflects whichever image the browser's own decoder selected from the file, which is typically the largest or highest quality entry available. If the ICO only contains one size, that is exactly what gets exported. If you specifically need a smaller embedded size rather than the one the browser picked, a dedicated ICO inspection tool that reads the container format directly is a better fit than a browser based converter.
Transparency and icon backgrounds
ICO files commonly carry an alpha channel, since transparent icon corners are what let a square image sit convincingly on a round taskbar button or a coloured browser tab. That transparency is preserved through this conversion, because PNG supports a full alpha channel and nothing needs to be flattened onto a background colour the way it would for a JPG export.
If the exported PNG looks like it has an unexpected solid background, the source ICO likely never had real transparency in the entry the browser selected. That is a property of the original icon file rather than something the conversion introduced.
This ico to png converter does no special ICO parsing, the browser already knows the format
No special ICO parsing happens here at all. The browser's own image decoder already understands the ICO container format, the same way it decodes any favicon.ico referenced from a page, so this tool loads the file into a standard image element and lets the browser do that decoding work.
Once decoded, the image is drawn onto a canvas at its natural pixel dimensions and the canvas element's toBlob method encodes those pixels as PNG. Because both the decode and the encode happen through built in browser APIs, the file never has to leave your device, which is the real difference from an ico to png online service, since that kind of tool has to receive an upload before it can run those same two steps on a server instead of inside your tab.
Converting several ICO icons at once
Drop or select multiple .ico files and each one is decoded and converted independently, appearing in the results list with its own pixel dimensions and download link. This suits pulling a batch of legacy application icons out of an old asset folder and getting them all into an editable format in one pass.
Each result reports the width and height the browser actually decoded, which is worth checking across a batch since files exported from different tools years apart do not always default to the same embedded resolution.
| Property | ICO | PNG |
|---|---|---|
| Purpose | Windows icons and favicons | General purpose raster image |
| Multiple sizes | Can bundle several in one file | One image per file |
| Transparency | Supported per entry | Full alpha channel |
| Software support | Narrow, mostly Windows and browsers | Universal |
How to convert ICO to PNG
- 1
Add your ICO file
Drag one or more .ico files onto the drop area, or click it to browse. Files stay on your device.
- 2
Let the browser decode it
The file is loaded through the browser's native ICO decoder, the same one used for favicon.ico.
- 3
Convert and download
Press convert to draw the decoded icon onto a canvas and encode it as PNG, then download the result.
Related tools worth bookmarking
Sources and further reading
- Microsoft: Icons specificationMicrosoft's own documentation of the ICO container format this tool decodes.learn.microsoft.com
- MDN: HTMLCanvasElement.toBlobThe browser API this converter uses to encode the decoded icon as PNG.developer.mozilla.org
- web.dev: Choose the right image formatGoogle engineering guidance on when a raster format like PNG is the right target.web.dev
Frequently asked questions
Common questions about the ico to png converter.
No. A browser decoding an ICO file selects one embedded image to display, typically the largest available, rather than exposing every bundled resolution. This tool converts whichever image the browser's own decoder picked, which covers the common case of pulling a usable PNG out of a legacy icon file.
Yes, if the source ICO entry the browser selected had an alpha channel. PNG supports full transparency, so nothing is flattened or filled in during the conversion, unlike a conversion to JPG which would require picking a background colour.
No. The same native ICO decoder your browser uses to show a site's favicon in its tab is what reads the file here, and the canvas element writes the PNG afterward. Both are decode and draw operations local to the tab, with no request involved at any point, unlike a service that has to receive your icon file before it can do the same thing remotely.
The output size matches whichever image the browser's decoder selected from inside the ICO container, since this tool does not resize the result. If you need a different pixel size, resize the exported PNG afterward with a dedicated image resizing tool.
Yes. A favicon file is an ordinary ICO container, often bundling 16, 32 and 48 pixel versions of the same icon, and this tool decodes it exactly the same way a browser tab would when loading a site's favicon.
ICO is a container format built specifically for Windows icons and browser favicons, capable of bundling several resolutions in one file. PNG is a general purpose lossless raster format with no concept of bundling multiple sizes, which is exactly why converting between the two loses the multi size bundling but gains universal software support.