image/x-icon ICO (Favicon) Common
Identifies ICO files — the traditional favicon format, capable of bundling multiple icon sizes in one file.
What it's for
image/x-icon identifies ICO files — historically the standard favicon format, notable for its ability to bundle multiple icon sizes/resolutions (16×16, 32×32, 48×48, and others) within a single file, letting the browser or OS pick the most appropriate size for the context (browser tab, bookmark, desktop shortcut) automatically. While modern favicon setups increasingly use PNG or SVG instead (simpler, single-purpose files with responsive sizing handled via CSS/HTML rather than the format itself), ICO remains widely supported and still commonly referenced for maximum backward compatibility, especially for the classic favicon.ico file convention.
Format & syntax
Content-Type: image/x-icon
The image/vnd.microsoft.icon type is also occasionally seen as an alternative for the same format, though image/x-icon remains the more commonly used and widely recognized value in practice. An ICO file's internal structure is a small header followed by one or more embedded images at different resolutions, each essentially a mini bitmap or PNG-compressed image within the container.
How it's used in practice
- The classic
favicon.icoconvention — browsers historically (and many still do, as a fallback) automatically check for a file at/favicon.icoat the site root, even without an explicit<link rel="icon">reference, making this the traditional zero-configuration favicon approach. - Multi-resolution bundling for broad compatibility — because ICO can bundle several sizes in one file, it's historically been favored specifically for covering many different display contexts (browser tabs, Windows taskbar/shortcuts, bookmarks) without needing separate files for each.
- Legacy browser and OS compatibility — some older browsers and Windows-specific contexts have more reliable, native support for ICO specifically, which is part of why it persists as a fallback option even as PNG/SVG favicons have become the more common modern primary choice.
- Alongside modern PNG/SVG favicon setups — many current sites include an ICO file as one of several favicon references (alongside PNG at specific sizes and often an SVG for modern browsers), covering the full range of browser/device favicon requirements through a combination of formats.
Common mistakes & gotchas
- Assuming ICO is still strictly required — modern browsers support PNG and SVG favicons directly via
<link rel="icon">, and a dedicated ICO file, while still good practice for maximum legacy compatibility, isn't strictly required the way it once was for basic favicon functionality. - Not including multiple resolutions when generating an ICO — while ICO supports bundling multiple sizes, some quick/simple ICO generation tools only include a single resolution, missing out on the format's actual multi-resolution advantage and potentially looking pixelated in contexts expecting a larger size.
- Forgetting the
/favicon.icoroot-path convention still matters as a fallback — even with a modern<link rel="icon">setup pointing elsewhere, some browsers/contexts still check for/favicon.icodirectly as a fallback, so leaving that path entirely empty (404) can occasionally still produce an unexpected fallback icon or console warning in some browsers. - Serving the wrong MIME type for the ICO file — some server configurations don't have
image/x-iconmapped correctly by default for.icofiles, causing them to be served with an incorrect or generic Content-Type, which can affect how reliably browsers recognize and use them.
Comparison & FAQ
| Type | Purpose | Key difference from image/x-icon |
|---|---|---|
| image/png | Modern, simpler favicon format | Single resolution per file (though multiple can be linked via HTML), but simpler and more broadly supported for modern favicon setups |
| image/svg+xml | Scalable vector favicon | Infinitely scalable single file, increasingly used as the modern preferred favicon format for supporting browsers |
Do I still need a favicon.ico file in 2026?
It's good practice for maximum legacy compatibility, since some browsers/contexts still check for it as a fallback, but it's no longer strictly required the way it once was — modern browsers support PNG and SVG favicons directly via explicit <link rel="icon"> references.
What's the advantage of ICO over just using a PNG favicon?
ICO can bundle multiple icon resolutions within a single file, letting the browser/OS automatically pick the appropriate size for different contexts (tab, bookmark, shortcut) — though modern setups often achieve similar coverage using multiple linked PNG/SVG files at different explicit sizes instead.
Why isn't my favicon.ico showing up correctly?
Check that your server is sending the correct image/x-icon Content-Type for the file, and verify the file actually contains valid, properly-sized icon data — a common issue is a quickly-generated ICO file containing only a single low resolution, appearing pixelated at larger display sizes.
Should I use SVG instead of ICO for my favicon?
SVG offers infinite scalability with a single small file for supporting browsers, making it an increasingly popular modern primary choice — though pairing it with PNG and/or ICO fallbacks remains common practice for broader compatibility across all browsers and contexts.