Favicon Generator
Turn any image into a complete favicon set: a multi-size .ico, the PNGs browsers read, an Apple touch icon and a web manifest. Nothing is uploaded.
Previews
Manifest
Related tools
All Webmaster tools →This tool runs entirely in your browser. Nothing you enter is sent to our servers, so there is nothing for us to store or see.
About the Favicon Generator
Drop in an image and get the whole favicon set as a ZIP: a multi-size favicon.ico, the PNGs browsers actually read, the Apple touch icon for an iOS home screen, the two Android icons, a site.webmanifest, and the five lines of HTML to paste into your head.
Six files, not forty. The advice to generate dozens of icons dates from 2014, when Windows tiles and a long tail of mobile browsers each wanted their own. iOS now reads one apple-touch-icon, Android reads the manifest, and every desktop browser reads a PNG link. The rest is bytes in your repository and lines in your head that nothing requests.
The .ico is still generated, because /favicon.ico is fetched by default when no link tag matches — by feed readers, by crawlers, and by anything that fails to parse the head. It costs a few hundred bytes and removes a 404 from your access log. It contains PNG images at 16, 32 and 48 pixels rather than the older bitmap form, which every browser since Vista reads.
Everything happens in your browser — decoding, resizing, encoding and zipping. The image never leaves your device, which matters when the logo you are turning into an icon belongs to a brand that has not launched yet.
How to use the Favicon Generator
-
Drop in your image
A square PNG or SVG at 512×512 or larger gives the best results. A non-square image is padded rather than stretched, and the tool says so.
-
Check the previews
Every size is rendered so you can see what happens to fine detail. A 16-pixel icon is sixteen pixels across — most logos need simplifying at that size.
-
Set the manifest details
The site name and theme colour go into site.webmanifest, which is what Android reads when someone adds your site to their home screen.
-
Download and install
The ZIP holds every file. Put them in your web root, or in a folder — set the path first and the generated markup will match.
Frequently asked questions
Do I still need a favicon.ico file?
Yes, though only one. Browsers request /favicon.ico by default when no link tag matches, and so do feed readers, crawlers and link-preview fetchers. It costs a few hundred bytes and stops a steady trickle of 404s. What you do not need is the twenty other files older generators produce.
What size should my source image be?
512×512 or larger, and square. That is the largest icon in the set, so anything smaller has to be upscaled and will look soft on an Android splash screen. Square matters because every icon size is square — a wide logo gets padded, which is usually not what people expect.
Why does my logo look like a smudge at 16 pixels?
Because sixteen pixels is not enough for detail. Thin strokes, small text and gradients all disappear. The usual answer is a separate simplified mark for the small sizes — a single letter, or the most distinctive shape from the logo — rather than the full logo scaled down.
What is site.webmanifest for?
It tells Android and Chrome what to use when someone adds your site to their home screen: the name to show, the icons to use, the theme colour for the status bar and the background colour for the splash screen. Without it, Android falls back to a screenshot and the page title, which looks unfinished.
Is my image uploaded anywhere?
No. Decoding, resizing, encoding and zipping all happen in your browser, and nothing is transmitted or stored. You can disconnect from the internet after the page loads and the tool keeps working.