· 4 min read
How to Extract Icon Sizes From an ICO File as WEBP
Heshan Fernando
Co-founder & COO
You’ve got a .ico file — an old application icon, a favicon, a downloaded asset — and you need one of its embedded images as a modern, standalone image file for use somewhere that doesn’t work with the .ico format directly. What a lot of people don’t realize until they actually open one is that an .ico file usually isn’t a single image at all — it’s a container holding several versions of the same icon at different resolutions, bundled together.
That structure is exactly why you can’t just “convert” an ICO to another format the way you would a simple JPG — you first need to pull out the specific size you actually want.
What extracting images from an ICO file actually involves
An .ico file bundles multiple resolutions of the same icon — commonly sizes like 16×16, 32×32, 48×48, and 256×256 — so that whatever application or operating system displays the icon can pick the size that fits its context without having to scale a single image up or down. Extraction means reading that container structure, pulling out each embedded image at its native resolution, and converting each one into a standalone file — WEBP, in this case, chosen for its efficient compression and support for transparency.
Preserving transparency matters because icons are very commonly used against varied backgrounds, and a botched conversion that flattens transparent areas to a solid color would defeat much of the point of having an icon in the first place.
Why people get stuck here
- ICO files aren’t single images. People often expect to convert “the” image in an ICO file, not realizing there are usually several different-resolution versions bundled inside.
- Not every converter extracts all embedded sizes. Some naive converters only grab the largest or first image found, silently discarding the other embedded resolutions.
- Transparency handling isn’t automatic in every tool. A converter that doesn’t correctly preserve the alpha channel can flatten transparent icon backgrounds to an unwanted solid color.
- Choosing the right extracted size for your use case isn’t always obvious. Different contexts (a website favicon versus a large app icon mockup) call for different embedded resolutions.
What a good ICO to WEBP converter looks like
Extracts every embedded size, not just one
A thorough converter should surface all the resolutions bundled in the ICO file, letting you choose which one (or several) you actually need.
Preserves transparency correctly
The WEBP output should keep any transparent areas from the original icon transparent, not flatten them to a solid background.
Lets you preview each extracted size before downloading
Seeing each resolution before committing helps you pick the right one for your specific use case.
Common mistakes to avoid
- Assuming an ICO file contains just one image and being surprised when a converter surfaces several different sizes.
- Using a converter that silently only extracts the largest embedded size, missing smaller resolutions you might have actually needed.
- Not checking whether transparency was preserved correctly in the converted output, especially for icons meant to sit on varied backgrounds.
- Picking an extracted resolution that’s too small for your intended display size, resulting in a blurry or pixelated result once scaled up.
How to do it with ICO to WEBP
Online Tool Store’s ICO to WEBP converter extracts every embedded icon size entirely in your browser.
- Upload your
.icofile. - See every embedded resolution the file contains.
- Preview each one, checking that transparency is preserved.
- Download the specific size (or sizes) you need as WEBP.
Because the conversion happens locally, your icon file never needs to be uploaded to an external server just to extract its contents.
Frequently asked questions
Why does my ICO file contain multiple images instead of just one?
ICO files are designed to bundle several resolutions of the same icon together, so that whatever displays the icon (an operating system, a browser tab, a taskbar) can use the size that best fits its specific context without needing to scale a single image and lose quality in the process.
Will converting to WEBP preserve my icon’s transparent background?
Yes, if the converter correctly handles the alpha channel during conversion — WEBP fully supports transparency, so a properly built converter preserves transparent areas from the original ICO rather than flattening them to a solid color.
Which extracted size should I use?
Match the extracted resolution to your intended use — a favicon typically needs a small size like 16×16 or 32×32, while a large app icon mockup or promotional image benefits from extracting the largest available size (often 256×256) to avoid blurriness when scaled up.
Final thought
An ICO file’s multi-size structure is exactly why a simple rename or basic conversion doesn’t work — extracting each embedded resolution properly, with transparency intact, is what actually gets you a usable standalone image.