Everyone in tutorialworld seems to be obsessed with CREATING multi-resolution .ico's to use as favicons. My question, however, is what browser support for these multi-resolution .ico's is like. Will the common browsers (Chrome, FF, Safari, and IE7+) treat an .ico containing two resolutions (16x16 and 32x32) in some sane way? The consensus seems to be that going larger than 32x32 starts to bloat the file size without providing much benefit (except to IE9/Windows 7 and whatever they do with 64x64 images), at least.
The standard size for favicons is 16x16 pixels, but most designers start with 32x32 pixels to accommodate retina screens. This way, the larger favicons show up nicely on retina screens and can also be scaled down.
7. Favicon is a file that contains one or more icons and is used to differentiate your website. You can configure a custom favicon file or files for your sites in the . The supported file formats for favicons application Settings are and ico, png, svg, gif.
ico format anymore (even though browsers do support . ico still). Favicons' format is always . png .
Favicon images are small in size, only 16 pixels in height by 16 pixels in width, so there is not much space for complex designs. Still, a good favicon that is clean, simple and easily identifiable can provide a good visual indicator for visitors navigating to your site through their tabs or bookmarks.
There's a lot of fairly good information on wikipedia, but not about size support specifically:
http://en.wikipedia.org/wiki/Favicon
However, I don't think most web browsers have a use case for an icon over 16x16. I certainly haven't seen a large icon, but I'm not surprised since larger icons would tend to expand url-bars, bookmarks and tabs to the point that they take up prohibitive amounts of vertical screen real-estate. I wouldn't bother until you knew somewhere it would be used and decide that the bandwith is worth it.
One thing to look into is whether or not they are utilized by any accessibility features for low vision users (this would make sense), but the screen shots here (for example):
http://www.accessfirefox.org/Firefox_Accessibility_Themes.php
seem to show the same old 16x16 icon despite the increased font size. I suspect the fact that one cannot rely on the existence of a 32x32 resolution means that nobody spends the time to program in code that looks for it.
As I understand it this multi-resolution feature for icons is intended to target reuse in "other contexts" such as Prism (defunct) or Air (proprietary)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With