Favicon generator
Generated in your browser · nothing is uploaded
Makes favicons at every size that is actually used, from an image or from a letter. It produces PNGs rather than an ICO, because every browser still in use takes a PNG.
How to use the favicon generator
The ICO format exists for Internet Explorer, and nothing else has needed it for years. Every current browser takes a PNG, and most prefer an SVG because it stays sharp at any size and can respond to dark mode. Generating a multi-image ICO to satisfy a browser nobody runs is work spent on nothing, so this produces PNGs and gives you the markup that matters.
The sizes are not arbitrary. 16 and 32 are the browser tab and bookmark bar — 16 is the one that actually appears in a tab, and anything with detail turns to mush at that size. 180 is the Apple touch icon for a home-screen shortcut. 192 and 512 are what a web app manifest wants for Android install prompts and splash screens.
Design for 16 pixels first and everything else follows. A logo that works on a letterhead almost never works in a tab, because at 16 pixels you have room for one shape or one letter and nothing else. That is why so many favicons are a single initial — not laziness, but the only thing that reads at that size.
Images are cropped to fill rather than fitted inside, because a favicon with letterbox bars looks like a rendering fault rather than a design. Give it something square if you can.
One thing worth knowing about caching: browsers cache favicons aggressively and often ignore a normal refresh. If a new icon does not appear, the file is usually fine and the cache is stale.
Questions
Every browser still in use takes a PNG or an SVG. ICO exists for versions of Internet Explorer that are long gone.
32 for the tab, 180 for the Apple touch icon, and 192 with 512 for a web app manifest. 16 if you want to be thorough.
At 16 pixels there is room for one shape or one letter. That is why so many favicons are a single initial.
Browsers cache favicons aggressively and often ignore a refresh. The file is usually fine; the cache is stale.
No. Everything happens in your browser — you can load the page, go offline, and it still works.