What Is an ICO File?

ICO (icon) is a bitmap container format originally designed for Microsoft Windows. Each file can include multiple embedded images at different dimensions and color depths, along with metadata that tells the operating system which image to render at a given display context. A single favicon.ico might contain 16×16, 32×32, 48×48, and even 256×256 pixel versions of the same logo, all packaged together.

The format supports both BMP and PNG compression inside the container. Modern ICO files often store PNG-encoded frames because PNG achieves smaller file sizes at larger dimensions while preserving transparency. When a browser or shell requests an icon, it selects the closest matching size rather than scaling a tiny image up, which is why multi-size ICO files look noticeably sharper than a lone 16×16 graphic stretched to fit.

PNG is a single-resolution raster image. You export one width and height, and every consumer of that file scales it as needed. That works well for apple-touch-icon links and web manifest entries where you explicitly declare a 180×180 or 512×512 asset. ICO differs because it holds several resolutions in one download, which helps older browsers and Windows shell integration pick the best match without issuing separate HTTP requests for each size.

If you already have a square PNG—typically exported at 512×512 or 256×256 from your brand guidelines—converting to ICO is a practical step before uploading to a CMS or dropping favicon.ico into your site root. The conversion step downscales your master artwork into the tab-friendly sizes browsers expect. PNG remains the better choice when you need one large marketing icon; ICO remains the better choice when you need broad legacy desktop support from a single root file.

Reach for ICO when you want a single favicon.ico at the domain root that Just Works across Internet Explorer-era behavior, classic desktop browsers, and Windows shortcut pinning without maintaining a long list of link tags. Many enterprise intranet templates and older CMS themes still assume favicon.ico exists at /favicon.ico and never read modern manifest files.

Prefer PNG (plus manifest and apple-touch-icon tags) when you are building a progressive web app, targeting mobile home-screen installs, or optimizing for Lighthouse audits that reward explicit icon declarations. The strongest production setups combine both: an ICO for backward compatibility and PNG declarations for high-DPI mobile contexts. Neither format replaces the other entirely—they cover overlapping but not identical platform requirements.

Start with a square master image. Logos designed on rectangular canvases should be centered on a square artboard with safe padding so circular masks and browser chrome do not clip corners. Export at least 256×256 pixels; vector sources should be rasterized at this size or higher before conversion so downscaled tab icons retain clean edges.

Include 16×16, 32×32, and 48×48 in the ICO bundle at minimum. Optionally add 64×64 and 256×256 for Windows shell views and high-DPI taskbar pinning. After conversion, open the ICO in a preview tool and inspect each embedded size—fine details that read well at 256×256 often disappear or muddy at 16×16, so you may simplify the mark for the smallest frames.

All major desktop browsers still accept favicon.ico, whether referenced explicitly in HTML or discovered automatically at the site root. Chromium, Firefox, Safari, and Edge also support PNG favicons via link rel="icon" with a type attribute, and Safari uses separate apple-touch-icon assets for iOS home-screen bookmarks.

ICO does not support animation, SVG vectors, or adaptive light/dark variants inside one file. For animated tab indicators or theme-aware icons, use separate PNG or SVG link tags and treat ICO as the conservative baseline. Search engines index favicons for result listings, so a crisp multi-size ICO can improve brand recognition in SERPs even when most users never think about the format.

A well-built favicon.ico with four to six embedded PNG-compressed sizes typically weighs 10–40 KB for simple geometric logos. Complex photographic artwork balloons quickly because each embedded frame stores full raster data. Optimize the master PNG before conversion, reduce color depth where transparency allows, and avoid unnecessary 512×512 frames if your audience is exclusively modern mobile browsers using manifest PNGs.

Browsers fetch favicon.ico on nearly every first visit to a domain, so bloated icons slightly hurt performance metrics even though they rarely dominate total page weight. CDN caching and long Cache-Control headers help after the first request. Treat ICO as one asset in a broader icon strategy rather than the only icon asset on a performance-critical landing page.