The History of Favicons: From IE5 to Modern PWAs

The favicon started as a tracking mechanism, evolved into a branding tool, and ended up as a cross-platform identity system spanning browser tabs, mobile home screens, search results, and progressive web apps. Going from a single 16-pixel ICO file in 1999 to the SVG-powered, dark-mode-aware icons of 2026 involved more weird detours than you'd expect.

Adoption Over Time

Favicon usage grew slowly at first, then became effectively universal as mobile web use exploded and search engines started displaying them.

The Full Timeline

1999

Internet Explorer 5 introduces favicons

Microsoft added support for a file called favicon.ico placed at the root of a website. The format was ICO, the size was 16x16, and the purpose was to distinguish bookmarks in the Favorites menu. The sneaky part: requesting this file also let site owners detect when users bookmarked their page, making it an early (and accidental) analytics tool.

2000

W3C standardizes the link tag

The HTML 4.01 specification added the <link rel="icon"> tag, allowing websites to specify a custom path and format for their favicon. This meant the file no longer had to be named favicon.ico or sit at the site root.

2003

Firefox adds tab favicons

Mozilla Firefox popularized tabbed browsing, and each tab displayed the site's favicon. This was the moment favicons shifted from bookmark decoration to persistent brand visibility. Users could see your icon every time they glanced at their tabs.

2007

Apple introduces touch icons with the iPhone

The original iPhone let users add websites to their home screen, but it needed a larger icon than 16 pixels. Apple created apple-touch-icon, a 57x57 PNG (later 180x180). This was the first time favicons needed to exist at multiple sizes for different devices.

2011

Android adds home screen shortcuts

Android browsers started supporting home screen shortcuts with their own icon requirements. The web manifest format emerged as a way to declare multiple icon sizes in a single JSON file, laying the groundwork for PWAs a few years later.

2014

Windows 8 tiles demand a new format

Microsoft's tile-based Start menu needed icons at completely new sizes (70x70, 150x150, 310x150, 310x310). The browserconfig.xml file was invented to declare these. Favicon sets grew from one file to a dozen.

2018

PWA icons and maskable format

Progressive Web Apps needed installable-quality icons at 192px and 512px, plus maskable versions that could handle different shaped masks across Android device manufacturers. The "purpose: maskable" attribute was added to the web manifest.

2019

Google adds favicons to search results

Google started showing favicons next to URLs in mobile search results. Overnight, favicons went from cosmetic to commercial: they now affected click-through rates in organic search. Sites without favicons looked unfinished next to competitors.

2021

SVG favicons gain broad support

Chrome and Firefox added support for SVG favicons. A single SVG file could replace multiple PNG sizes, scale to any resolution, and even adjust colors automatically for dark browser themes.

2026

The modern favicon is a system, not a file

Today a complete favicon setup includes ICO, SVG, multiple PNGs, a web manifest, browserconfig, social preview images, and maskable icons. AI-powered generators can now produce the entire package from a single text prompt, so you no longer have to deal with the manual work that piled up over 27 years.

A 27-year accretion

No one designed the favicon system. It grew organically as each new platform bolted on its own requirements. That is why you need 18 files for something that was originally a single 16-pixel ICO. Each file represents a different era and a different platform's idea of what a website identity should look like.

Milestone Impact Timeline

Not all favicon milestones mattered equally. Some were technical curiosities; others fundamentally changed how websites thought about their icon. This chart shows the relative impact of each milestone on a scale from 1 (minor spec update) to 10 (industry-wide shift in behavior).

The 2019 Google Search integration scored highest because it was the first time favicons had direct commercial impact. Before that, a missing favicon was an aesthetic problem. After that, it was a competitive disadvantage — your search listing looked less trustworthy next to competitors who had one.

The favicon.ico Format Deep Dive

The ICO format was invented by Microsoft in 1985 for Windows 1.0 program icons, fourteen years before it was repurposed for the web. It is, technically, a container format: a single .ico file can hold multiple images at different resolutions and color depths. This is why it survived so long — one file, multiple sizes.

Inside an ICO file, each image is stored as either a BMP (the original approach) or a PNG (added later for better compression). Modern ICO files almost always use PNG internally, which means the file is essentially a wrapper around several PNGs with a directory header telling the OS which resolution to use.

The ICO directory header stores each image's width, height, color count, and byte offset. When Windows or a browser needs a 32x32 icon, it reads the directory, finds the matching entry, and extracts just that one image. This lookup is instant because the directory is at the beginning of the file.

Why is ICO still around in 2026? Three reasons. First, every browser on earth supports it, including ancient corporate intranets running IE11. Second, it is the only format browsers request automatically — if you put a favicon.ico at your domain root, browsers will find it without any <link> tag. Third, certain non-browser tools (PDF viewers, desktop email clients, RSS readers, Windows shortcuts) only look for ICO and ignore all other formats.

The automatic request

Even in 2026, if a page has no favicon tags at all, browsers will send a GET request to /favicon.ico. This behavior is hardcoded from the IE5 era. If the file does not exist, you get a 404 in your server logs — one of the most common 404s on the internet. Either provide the file or return a proper 404 response to avoid log noise.

The Modern Favicon Stack: 2005 vs 2026

In 2005, shipping a favicon meant dropping a single .ico file in your web root. In 2026, doing it right means generating an entire package of files. Here is the full contrast:

Requirement	2005	2026
Primary format	favicon.ico (16x16 BMP)	SVG with dark mode support
Fallback format	None needed	favicon.ico (multi-res: 16, 32, 48)
Apple support	Not applicable	apple-touch-icon.png (180x180)
Android support	Not applicable	manifest.json icons (192, 512)
Maskable icons	Not applicable	Separate maskable variants with safe zone
Windows tiles	Not applicable	browserconfig.xml (removed by most in 2024)
Social previews	Not applicable	OG image (1200x630)
Dark mode	Not applicable	CSS media query inside SVG
HTML tags needed	0 (auto-detected)	4-6 link/meta tags
Total files	1	6-12 depending on coverage
Total effort	Drop file in root	Generate full package + add HTML

The silver lining is that the recommended minimum has actually gotten simpler in the last few years. In 2018-2020, you arguably needed 15+ files to cover every platform edge case (Windows tiles, every Android size, multiple apple-touch-icon sizes). By 2026, the consensus has settled on a practical minimum: one ICO (multi-resolution), one SVG, one 180px PNG for Apple, one 192px PNG and one 512px PNG in a manifest.json. Five files cover 99% of real-world usage.

Favicons in Search Results

Google first started showing favicons in mobile search results in May 2019. The change was controversial — some SEO professionals argued it made ads harder to distinguish from organic results. Google adjusted the design several times but kept the favicons.

In October 2023, Google expanded favicon display to desktop search results. This was the second major milestone because desktop search has more visual real estate, making the favicon more prominent.

Google's requirements for search result favicons are specific. The icon must be at least 48x48 pixels (they display it at 16x16 but want a high-res source). It must be a multiple of 48px — so 48, 96, 144, etc. It cannot contain inappropriate content, and it cannot be a generic icon like a globe or a plain colored square. If your favicon does not meet these criteria, Google shows a default globe icon, which looks noticeably worse than a real favicon next to your competitors.

Google caches favicons aggressively. If you change your favicon, it can take days to weeks for the new version to appear in search results. Google re-crawls favicons on its own schedule, and there is no way to force a refresh. The Google Search Console will eventually reflect the change, but there is no manual "recrawl favicon" button.

Bing shows them too

Bing started displaying favicons in search results in 2019 as well, following Google's lead. DuckDuckGo, Brave Search, and Yandex also show favicons. At this point, every major search engine uses favicons in results, making them a universal search branding element.

What Changed in 2026

The biggest shift is that SVG has become the recommended primary format. With Safari finally supporting SVG favicons on macOS, every major desktop browser can now use a single SVG file with dark mode support. The ICO fallback is kept for edge cases (PDF viewers, old email clients), but it is no longer the primary format.

AI-powered generation is the other big change. Instead of manually creating and resizing icons across 18 files, you type a prompt and get the whole package. Twenty-seven years of accumulated complexity, collapsed back into one step.