ICO vs PNG Favicons: What Your Site Actually Needs
Favicon advice on the web is a pile of contradictions. Some tutorials tell you to ship a single ICO file and forget it. Others hand you a list of ten PNG sizes and a manifest file. Both camps are half right, and the wrong half costs you 404s in your server logs, a broken icon in search results, and ugly defaults in browser tabs. Here is what actually happens when a browser reaches your site, and the minimum set of files that covers it in 2026.
Why /favicon.ico still gets requested no matter what
Even if your HTML contains zero favicon links, browsers request https://yoursite.com/favicon.ico by default. This behavior dates back to 1999 and is not going away. Some user agents — old Safari versions, certain crawlers, RSS readers, enterprise proxies — skip your <link> tags entirely and just hit that URL.
If the file does not exist, every raw request becomes a 404 in your access logs and one wasted round trip. If your site gets crawled heavily, this is thousands of log lines for nothing. The practical conclusion: every site should have a real file at /favicon.ico, even if the rest of your favicon setup is PNG-based.
What an ICO file actually is
ICO is not an image format in the way people assume. It is a container that holds one or more images at different sizes — 16x16, 32x32, 48x48 — in a single file. The browser (or Windows Explorer, or a bookmark menu) picks the size that fits its rendering context. An ICO containing only one image forces the client to scale that image up or down, which is how you get blurry toolbar icons.
A good ICO contains at least 16x16 and 32x32, ideally plus 48x48. You can pack PNG-compressed frames inside an ICO, so the file stays small — a proper multi-size ICO is usually 15-40 KB.
Common mistake: taking a 512x512 PNG, renaming it to favicon.ico, and shipping it. Most browsers will render it anyway, but Windows shortcut icons, older tooling, and some crawlers choke or pick the single huge frame and scale it down badly. Convert, do not rename.
What PNG favicons give you
Modern browsers all support <link rel="icon" type="image/png">. A PNG favicon is simpler to produce, scales cleanly, and you can serve higher resolutions like 48x48 or 128x128 with a single file that Chromium, Firefox, and Safari all downscale reasonably well.
The setup that covers most cases looks like this:
<link rel="icon" href="/favicon.ico" sizes="any"><link rel="icon" href="/icon.png" type="image/png" sizes="48x48"><link rel="apple-touch-icon" href="/apple-touch-icon.png">
That is three files and three lines. Chromium and Firefox prefer the largest suitable PNG. Safari pulls the ICO for tabs in older versions and the apple-touch-icon for bookmarks and the home screen. Every client that blindly requests /favicon.ico gets a real file.
The apple-touch-icon you keep forgetting
iOS requests /apple-touch-icon.png whenever someone adds your site to the home screen, with or without a <link> tag. The requirements people get wrong:
- 180x180 pixels, PNG.
- No transparency. iOS puts your icon inside a rounded squircle and composites it over a black background. A transparent logo becomes a black blob.
- No pre-applied rounded corners. iOS masks it for you; doing it yourself double-rounds the edges.
Missing this file does not break anything visibly. The user just gets a screenshot of your page as the icon, which looks broken even though nothing reported an error.
Google search: a second consumer of your favicon
Since 2020, Google shows favicons next to results on mobile. Their requirements are stricter than any browser's:
- The icon must be reachable at
{host}/favicon.ico— not just linked. - It must be a multiple of 48x48, like 48x48, 96x96, or 144x144. A 32x32 file can fail the check.
- It must be square and a valid image URL that returns a stable status, not a redirect that changes.
Sites fail this constantly because they only ship a tiny ICO. If your favicon is missing from Google's mobile results, that is usually the reason. Serving a properly sized ICO at the root satisfies both browsers and Google with one file.
Where WebP and SVG fit
Chromium and Firefox accept <link rel="icon" type="image/webp">, and WebP is smaller than PNG for the same quality. Safari's support has been inconsistent by version, so WebP favicons are best shipped as an additional candidate, not your only icon. An SVG favicon (rel="icon" type="image/svg+xml") scales infinitely and supports dark-mode media queries inside the file, which is genuinely useful — but again, treat it as an enhancement on top of ICO and PNG, not a replacement.
The practical checklist
- Produce one master image, 512x512, with transparent background.
- Export a multi-size ICO (16, 32, 48) and place it at
/favicon.icoat your site root. - Export a 48x48 (or 96x96) PNG and link it as
rel="icon". - Export a 180x180 opaque PNG for
/apple-touch-icon.png. - Add the three
<link>lines from above. - Optionally add an SVG icon for dark mode and a WebP variant for size.
That is five minutes of work per site and it closes every real gap. The bigger setups with manifests and 12 sizes only matter if you ship an installable PWA, where the 192x192 and 512x512 maskable icons come in.
Mistakes worth avoiding twice
- Renaming a PNG to
.icoinstead of converting it. Works until it doesn't — Windows and some crawlers reject it. - Single-frame ICOs. Add the 16x16 frame or accept blurry bookmarks.
- Transparent apple-touch-icons. Fills black, always.
- Pointing
<link>athttps://cdn.example.com/icon.pngwhile serving no root favicon. Google's mobile result check looks at the root host. - Shipping a 200 KB ICO. Multi-size ICOs with PNG frames compress fine; if yours doesn't, optimize the source images first.
If you already have an ICO and need proper PNG exports from it for the root icon, an ico-to-png converter handles the unpacking. If your exported files come out heavy, run them through an image optimizer before deploying — favicon bloat loads on every single page view. And if you want to test whether WebP favicons work across the browsers you care about, a quick webp-to-png conversion gives you the fallback file in seconds.
The format war nobody asked for resolved itself in favor of "ship all three small files." Do that, verify /favicon.ico returns 200, and stop thinking about favicons for another five years.