When the only copy of a logo is a favicon
ICO files become interesting exactly when everything else is gone. A company rebrand starts and the only surviving trace of the old mark is the favicon on an archived site. A developer documenting legacy software needs its icon for a migration guide. An auditor comparing a phishing page to the real one needs both favicons side by side as normal images. In each case the asset exists, but locked in a format that editors, wikis and slide decks refuse to open. This tool unpacks the container and hands you the largest image inside as a clean PNG, transparency intact, without the file ever leaving your machine. From there the image behaves like any other: shrink it for the web with PNG to WebP, or flatten it for an email with PNG to JPG.
What is actually inside an .ico file
Despite the singular name, an ICO is an archive. The format, dating to Windows 1.0 in 1985, starts with a directory listing every image stored in the file, each entry recording its dimensions and where its data begins. A well-built modern icon carries the same artwork at 16, 32, 48, 64, 128 and 256 pixels so each context gets a version rendered for its size; a lazy one might contain a single 16 pixel bitmap, which is why some extracted favicons turn out tiny. Individual entries may be stored as old-style bitmaps or, in modern files, as embedded PNGs. This converter reads the directory, picks the entry with the largest dimensions, and decodes just that one. To go the other way and build a proper multi-size icon, use PNG to ICO, ideally starting from a sharp master exported through SVG to PNG.
Common questions
Which of the sizes inside the ICO do I get?+−
The largest one. An ICO is a container that typically holds the same artwork at several resolutions, commonly 16 up to 256 pixels, and for editing, documentation or redesign work the biggest version is almost always the one you want. Extracting the largest image gives you the most detail the file has to offer; smaller sizes contain strictly less information.
Why convert ICO to PNG at all?+−
Because almost nothing outside browsers and Windows opens ICO files. Image editors handle them inconsistently, chat and email previews usually fail, CMS media libraries reject them, and documentation tools cannot embed them. PNG is the neutral, lossless container everything accepts, so extracting the icon as PNG turns a locked-up asset into a usable image.
Is transparency kept in the extracted PNG?+−
Yes. Icons rely heavily on transparent backgrounds to sit cleanly on tabs, taskbars and desktops, and the alpha channel stored in the ICO carries straight into the PNG, which supports transparency natively. The extracted image will composite onto any background exactly the way the original icon did, with no white box appearing around the artwork.
How do I get a site's favicon to convert?+−
Try the site root first: most sites serve their icon at /favicon.ico, so entering the domain followed by /favicon.ico in your address bar usually downloads or displays it. If that returns nothing, view the page source and look for link elements with rel set to icon, which point at the actual file. Note that some modern sites use PNG or SVG favicons, which need no conversion.