Favicon is more or less complex from a platform to another. I think Chrome for Android is the trickiest.
With iOS, things are not that easy but clear: Apple defined the Apple Touch icon, a proprietary mechanism. This approach makes sense. After all, when iOS was introduced, it required new, high resolution icons that did not exist anywhere else. As a result, we have a somehow proprietary markup with a specific apple-touch-icon relation attribute. The Apple Touch icon comes with an advantage: because it is specified for iOS, Apple can enforce design guidelines. Solid background, rounded corners, etc.
Unlike iOS Safari, Android Chrome (Chrome for short) does not define any proprietary mechanism. That surely sounds good. No one likes vendor-specific stuff. But this approach comes with a cost. More of this below.
As indicated in the specs, Chrome relies on two sets of icons:
It is easy to figure out Google's strategy: introduce a dedicated 192x192 high resolution icon and fallback to the Apple Touch icon when not available. Pragmatic, as it should be. But the devil is in the details, and when you try to create the ideal favicon, things become quite tough.
A small detail as a starter. I started to study Chrome's icon for almost a year. In the beginning, it was a 196x196 icon. When I started this article, I re-read the specs, something I had not done for a while. I realize there was a change: 196x196 became 192x192.
As we will see below, this is a major change because today's Chrome (version 37) does not use the 196x196 PNG icons that were designed especially for it.
Since Chrome supports two kind of icons, which one does it use? Looking at the compatibility page of RealFaviconGenerator:
| Android Chrome version | Favicon | Bookmark icon | Home screen icon | | -------------------------------------- | ---------------- | ------------------------ | ------------------------ | | 31 | 16x16 PNG icon | 152x152 Apple Touch icon | 152x152 Apple Touch icon | | 32 | 196x196 PNG icon | 152x152 Apple Touch icon | 196x196 PNG icon | | 35 | 32x32 PNG icon | 152x152 Apple Touch icon | 152x152 Apple Touch icon | | 36 | 160x160 PNG icon | 160x160 PNG icon | 160x160 PNG icon | | 37 (latest version at time of writing) | 160x160 PNG icon | 160x160 PNG icon | 160x160 PNG icon |
Apparently, Google finally set its preference to the PNG icon, if it can find one.
This brings consistency: let's design a PNG icon and Chrome will not pick anything from Apple. But now comes the trick. Sure we can design an icon for Chrome. But as the PNG icons are declared with standard HTML5, other browsers can use it, too. This is what happens with the current pictures and code generated with RealFaviconGenerator (version 0.7). Because the Chrome PNG icon is quite large, some browsers, such as IE11, consider it as a good choice. This is no good news when the author of RealFaviconGenerator decides that the Chrome icon must be designed after the iOS icon.
According to the specs, Chrome picks the 192x192 icon if it finds it, the 128x128 icon otherwise. Is that the case? To demonstrate this, I generated all PNG icons from 16x16 to 256x256 and declared them:
<link rel="icon" type="image/png" href="/16.png" sizes=16x16> <link rel="icon" type="image/png" href="/17.png" sizes=17x17> <link rel="icon" type="image/png" href="/18.png" sizes=18x18> ... <link rel="icon" type="image/png" href="/255.png" sizes=255x255> <link rel="icon" type="image/png" href="/256.png" sizes=256x256>
With this code, Android Chrome uses the 192x192 icon, as expected. Good.
What if it is not present? Chrome selects the icon just below: 191x191. This make sense, although the specs say nothing about this. And it goes on and on. Delete everything from 129x129 to 192x192 and Chrome uses the "low resolution" 128x128 icon. Delete it and Chromes takes the 127x127 icon. In the end, if you offer Chrome a 16x16 icon and icons larger than 192x192 (eg. 193x193, 194x194, etc.), it uses the 16x16 icon.
Thus, this general rule about Android Chrome 37: Chrome uses the same icon as the favicon, bookmark icon and "Add to home screen" icon. It picks the widest PNG icon it can find which is no larger than 192x192.
The goal of this post is to prepare a fix for issue #26. In the next version of RealFaviconGenerator, Chrome's icon and classic PNG icons will be correctly dispatched.