Grunt user, search no more. This is where you generate your favicon.
Craft the icons for all iOS, Android and friends, and get the
Grunt code and instructions to install the icons in your project.
All browsers
All platforms
Designed for Grunt
0% completed
Your favicon is not correct
Your master picture
Missing pictures
You have chosen to use a specific picture fot the iOS Web clip, but you haven't uploaded any picture.
Please upload a picture or choose another option.
You have chosen to use a specific picture fot the Windows 8 tile, but you haven't uploaded any picture.
Please upload a picture or choose another option.
Missing path
You have chosen to not place your files in the root of your web site.
Please specify a path.
Why put the favicon pictures in the root directory
When generating a favicon with RealFaviconGenerator, the instructions ask you to place all files at the root of your web site.
You may want to place them in a sub-directory, for example in http://mywebsite.com/icons/, just to make things clearer.
However, there are three drawbacks with this approach:
Internet Explorer looks for favicon.ico at the root of the web site. Granted: this is because we
ask you to not declare favicon.ico.
iOS devices look for files such as apple-touch-icon-144x144.png at the root of the web site,
as described by Apple.
This issue can be mitigated by declaring the icons in the HTML code (this is necessary for Android anyway),
but following Apple conventions is probably the best move.
By default, Internet Explorer 11 looks for browserconfig.xml at the root of the web site.
Several services, such as Yandex,
look for favicon.ico in the root directory.
The compression is lossy, meaning you might notice differences between the original and compressed pictures.
Yet the differences are (supposed to be) minimal:
Uncompressed picture (36KB)
Compressed picture (14KB)
You can see slight differences in the gradient part:
No zoom
4x zoom
When you download the compressed pictures, make sure they match your standards.