What a favicon has to do
A favicon is the small icon in the browser tab, the bookmark list, the history, the home screen shortcut, and โ on mobile search results โ next to your site's name. It is the smallest brand asset a site owns and the one users see most often, usually at 16 pixels square.
It is not a ranking factor. It is a recognition detail: a tab with an icon is findable among twenty tabs, and a search result with a familiar icon is the one that gets clicked. The work is small and the payoff is entirely in being recognisable.
The sizes you actually need
favicon.ico with 16, 32 and 48 pixel versions inside one file covers browser tabs, bookmarks and Windows desktop shortcuts, and older browsers and tools that request nothing else. It is the one file every site should have.
apple-touch-icon.png at 180ร180 is what iOS uses when someone saves the site to their home screen. Without it, iOS takes a screenshot of the page instead, which looks exactly as bad as it sounds.
192ร192 and 512ร512 PNGs are the sizes the web app manifest asks for, used by Android home screens and install prompts. Generate them from the same source image and the set is complete: one ICO, one Apple icon, two manifest icons.
Google's current rules, checked November 2026
Google's favicon guidance asks for a square image (1:1 aspect ratio) of at least 8ร8 pixels, and recommends one larger than 48ร48 pixels so it looks good on the various surfaces where it appears. That is the whole size rule as it stands today.
The older rule โ that the favicon must be a multiple of 48 pixels square โ was removed from Google's documentation in October 2024. A great many favicon guides still repeat it, and several platform help pages still say it, but it is no longer what Google asks for. A 96ร96 or 192ร192 icon satisfies both the current rule and the old one, which is the practical reason to use those sizes.
Formats: Google lists BMP, GIF, ICO, PNG, JPEG, PPM and TIFF as supported. SVG is not on the list, so a site that serves only an SVG favicon may find Google never shows its icon in results. Serve a raster icon as well.
Three more conditions: the homepage must link the icon, Googlebot and Googlebot-Image must be able to fetch both the page and the file, and the icon's URL must be stable. Favicons are scoped per hostname โ a subdomain can have its own, a subdirectory cannot. And Google states plainly that a favicon is not guaranteed to appear in results even if every guideline is met.
Designing for 16 pixels
The icon renders at 16ร16 in most of the places that matter, and a detailed logo at that size is a coloured blur. The rule is one bold glyph or one or two letters, in high contrast, with no text smaller than the glyph itself.
The full logo is not a favicon. Take the mark โ the letter, the shape, the symbol โ and drop the wordmark, the tagline and the fine detail. Then look at it at actual size, in a real tab, next to ten other tabs: if you cannot pick it out in a second, simplify it further.
The HTML you need
Three lines cover the common cases. The classic icon, the Apple touch icon, and the manifest that points at the larger PNGs:
<link rel="icon" type="image/x-icon" href="https://example.com/favicon.ico"><link rel="apple-touch-icon" sizes="180x180" href="https://example.com/apple-touch-icon.png"><link rel="manifest" href="https://example.com/site.webmanifest">
Browsers also request /favicon.ico from the root by default, even without a tag โ which is why the file belongs at the root and not in an assets folder. The tag still matters: it is how you declare a PNG icon, and it is what Google reads.
Testing and waiting
After uploading, hard-refresh a page and look at the tab. Browsers cache favicons aggressively, so a stale icon after a change usually means the cache, not the file โ a cache-busting query string on the icon URL (/favicon.ico?v=2) forces a fresh fetch.
Google is slower. A new favicon appears in search results on Google's crawl schedule, which takes days to weeks after the homepage is next crawled. If it never appears, check three things: that the homepage links the icon, that robots.txt does not block Googlebot-Image from fetching the file, and that the file is in a supported format.
A worked example: from logo to favicon in five minutes
Start with the logo file and crop to the mark โ for a wordmark, the first letter in the brand's typeface, on the brand's background colour, in a square. Export that as a 512ร512 PNG: that one file is the source for everything else.
Generate the sizes from it: 16, 32 and 48 into the ICO, 180 for Apple, 192 and 512 for the manifest. Upload the files to the domain root, add the three link tags to the page head, and check the tab. Then wait for Google โ the icon will show up when the homepage is next crawled, and there is nothing to do in the meantime but leave the URL alone.