A favicon is quite simply an icon. The idea behind its inception was for browsers to use them to make a quick, easy to identify visual representation of a website in the browser's UI.
The first favicons were implemented in 1999 by Microsoft in their Internet Explorer browser. Since then, they were widely adopted by almost all browsers, and today it is commonplace to find favicons being displayed all over the browser, such as in bookmarks menus, window and tab headings, address bars, history, etc.
Microsoft's original idea was to load that icon from a specific place relative to a website. If your website's address was
pokemon.com, Internet Explorer looked for it at
This original implementation worked alright at first. But at the time, lots of websites were hosted with companies like Geocities, Angelfire and Tripod. They would give your website an address like
tripod.com/my-pokemon-website. The problem with this was that the browser would always use Tripod's favicon located at
tripod.com/favicon.ico and not one that the website's author might want to show!
Eventually, the people responsible for standardising HTML on the web, the World Wide Web Consortium (W3C), created a specification for how both browsers and website authors should use these icons. In the HTML of the page, an HTML tag would be included, telling the browser where to find that icon.
But, since the original Internet Explorer needed to work because lots of websites had been using it, browsers began supporting them both.
A lot of things changed when the smartphone became mainstream. One notable thing that changed for favicons was that people could save websites to their home screen. But the
favicon.ico icons up to this point were all too small – sometimes they were as tiny as 16 pixels! These icons were supposed to be shown next to app icons, which are much more high fidelity images – up to 10 times bigger, in fact!
Android and iOS use different icon sizes. Also, Windows began using yet another icon type for displaying websites in its Metro tile display.
As a result of all these different specifications, there are now a lot of places to look for favicons. And the different icons you can get will vary depending on which one you request. Some sites will have some but not others!
The list includes:
Some sites end up with dozens of different icons. These vary, from the usually tiny
favicon.ico to the higher resolution icon used by iOS's home screen feature. Additionally, a lot can go wrong with fetching these.
So, requesting something as simple as a tiny little website icon can be a very complicated task! Clearly there is no one-size-fits-all solution to grab the icons.
So all that being said, how do you make sure your website has all the different icons it should have, and they're properly referenced in your HTML markup?
Quite simply, the best way to do this is to use a service that generates the markup and icons for you. The best I've found so far is the ol' faithful realfavicongenerator.net. You can upload an icon image, specify some preferences, and it will generate a ZIP file with your icons properly sized and set up, as well as the HTML to insert into your site's
If you use Webpack, you could also try out the plugin jantimon/favicons-webpack-plugin that will automatically work its magic to give you favicons.
domain.com/favicon.ico, but be prepared for 404s.
Icon Horse navigates these crazy waters to get the icon you want, when you want it. And if it doesn't exist, we know that the worst thing the icon do is show up as a broken image. That's why we will return what we call a "fallback" – an image that can work as a placeholder in case the icon does not resolve.