What is an ICO file?
Learn how the ICO image format packages multi-resolution icons and website favicons, how transparency works, and how to convert your graphics efficiently. Free ICO converters included.
Microsoft introduced the ICO format in 1985 alongside Windows 1.0 to solve a fundamental user interface problem: displaying crisp visual markers across different display densities and interface states. Standard bitmap files forced operating systems to scale a single raster grid, which introduced heavy blur or jagged distortion. The ICO format resolved this issue by acting as an image container that bundles multiple icon resolutions and color depths into a single file payload. When the system needs to render an application shortcut on a desktop, menu, or taskbar, it automatically selects the optimal embedded sub-image.
Technically, an ICO file functions as a directory-based wrapper rather than a standalone raster codec. Each internal sub-image entry defines its width, height, color palette, and memory offset within the file stream. Historically, icons stored uncompressed DIB or BMP raster layers with 1-bit binary transparency masks, but Windows Vista updated the specification to allow full 32-bit PNG compression for 256x256 pixel layers. The format supports 8-bit alpha channels for smooth drop shadows and partial transparency, yet it strictly excludes animation, reserving multi-frame motion for the related ANI cursor container.
Today you encounter ICO files primarily in two environments: Microsoft Windows software development and web publishing. Every major web browser recognizes the root favicon.ico standard to display site branding on tabs, bookmark shelves, and browser history panels. Software developers bundle these files directly into executable resources so desktop operating systems can display sharp application shortcuts at scales ranging from 16x16 pixels up to 256x256 pixels. Graphic editors, web servers, and browser-based converters read and generate ICO archives to ensure legacy backward compatibility across both desktop platforms and web endpoints.
Technical specification
| Extension | .ico |
|---|---|
| MIME type | image/x-icon |
| Compression | A container holding PNG or uncompressed BMP layers |
| Transparency | Yes |
| Animation | No (the animated sibling is ANI) |
| Typical file size | A typical favicon file is 5-100 KB |
| Browser and system support | Every browser reads it as a favicon; it is the Windows icon format |
| Developed by / year | Microsoft, 1985 |
When to use it
- Choose ICO when you are compiling desktop application executables for Windows that require dedicated multi-size visual assets.
- Choose ICO when you need a standardized favicon.ico asset that guarantees root-level compatibility across all legacy and modern web browsers.
- Choose ICO when you want to package multiple resolutions such as 16x16, 32x32, and 48x48 pixels into one compact file.
- Choose ICO when you must provide Windows folder customization with tailored graphics that remain sharp across various system viewing modes.
When not to use it
- Avoid ICO for inline website photography and illustrations, choosing WebP or JPEG instead to achieve better compression and responsive rendering.
- Avoid ICO when you need animated graphics, opting for APNG, GIF, or the dedicated ANI cursor format instead.
- Avoid ICO for modern web vector logos, utilizing scalable SVG files to maintain crisp vectors without embedding multiple raster resolutions.
Our tools for this format
4 tools that take ICO files in or write them out. Each one runs in your browser, so nothing is uploaded.
Convert to this format
Convert from this format
Common problems
The favicon looks blurry or pixelated on high-DPI browser tabs.
This happens when your ICO file contains only a single low-resolution layer like 16x16 pixels. You should rebuild the file to embed 16x16, 32x32, and 48x48 pixel versions so high-resolution screens can pick the sharpest asset. Modern browsers will select the larger 32x32 raster layer automatically on high-density displays.
The transparent background appears as a solid black or white box in Windows Explorer.
Older BMP-based layers in ICO files rely on 1-bit transparency masks, which fail if the alpha channel is incorrectly exported. Convert your source graphic from a 32-bit PNG with an explicit alpha channel before generating the ICO archive. This ensures the operating system correctly blends anti-aliased edges against any desktop wallpaper.
The ICO file size exceeds several megabytes and slows down website loading.
Uncompressed BMP layers at 256x256 pixels consume substantial memory within an icon container. Re-encode the largest embedded layers using PNG compression within the container to reduce the file footprint below 100 KB. Keep only essential dimensions such as 16x16, 32x32, and 48x48 pixels for web favicons.
A mobile web browser ignores the favicon stored in the ICO file.
Mobile operating systems often bypass legacy ICO files in favor of explicit PNG touch icons declared in the HTML header. While you should keep favicon.ico for browser desktop tabs, provide dedicated 180x180 or 192x192 PNG link tags in your page markup for mobile home screens. This dual approach guarantees proper icon rendering across all desktop and handheld clients.
Frequently asked questions
What is the maximum resolution an ICO file can support?
The standard ICO specification supports individual icon layers up to 256x256 pixels with 32-bit color depth. Dimensions beyond 256 pixels require alternative image formats like PNG or SVG.
What standard icon sizes should be included in an ICO file?
For web favicons, embedding 16x16, 32x32, and 48x48 pixels covers standard desktop tabs and taskbars. For Windows desktop applications, you should also include 64x64, 128x128, and 256x256 pixel layers.
Can an ICO file contain animated frames?
No, the standard ICO format does not support animation or multi-frame playback. Animated Windows cursors use the closely related ANI format, while animated web graphics rely on GIF or APNG.
What is the typical file size of an optimized ICO file?
A standard multi-resolution web favicon containing 16x16, 32x32, and 48x48 pixel layers typically measures between 5 KB and 25 KB. Files that include 256x256 PNG layers usually remain under 100 KB when properly compressed.
Is ICO still necessary for modern website favicons?
Yes, placing a 16x16 or 32x32 favicon.ico file in your website root remains essential because browsers and web crawlers request it by default to avoid 404 server errors. Modern sites pair this file with 192x192 PNG and SVG declarations for newer displays.