Technical
Favicon Generator
One source image, every icon file a browser asks for
Upload a square image and get back the ICO, the PNG sizes browsers and mobile home screens request, an Apple touch icon, a web app manifest listing them, and the link tags to paste into the head in the right order.
Get early accessWhat it returns
- A favicon.ico containing the small sizes, plus standalone PNGs at the sizes browsers, Android home screens and Apple devices ask for.
- A web app manifest listing the icons with their sizes and purposes, ready to drop in next to them.
- The link and meta tags to paste into the head, in an order that does not leave an older browser picking the wrong file.
- A preview of the icon at 16 pixels, in a light and a dark browser tab, which is where a logo with fine detail or a white background stops working.
When this matters
A rebrand ships and the old icon is still in the tab for weeks. Part of that is caching, which you cannot do much about, but the rest is that nine files were needed and six were replaced. Browsers fall back to /favicon.ico when the tags do not resolve, the old one is still sitting at the root, and the tab happily shows last year's logo to anyone who has visited before.
How to answer this today
Site audit is the place this shows up as a problem rather than a task: it crawls the site and reports referenced files that return a 404, which is how a manifest pointing at an icon nobody uploaded gets found. Audit will not generate the files, and a favicon set is a five minute job once you have a square source image, which is what this tool is for.
Site auditWhy this is harder than it looks
The size list is a moving target
Browsers, Android, iOS and Windows have each asked for different sizes at different times, and advice written three years ago over-generates files nobody requests. The useful set is small and current, and the page has to say when it was last checked.
A 16 pixel icon is not a small logo
Wordmarks, thin strokes and gradients all turn to mush at tab size. The real work is deciding what survives the reduction, usually a single glyph or shape, and a generator can only show you how badly the full logo fails.
Caching makes mistakes persist
Favicons are cached aggressively by browsers and often separately from the rest of the page, so a replacement can look unchanged on your own machine for days. Verifying a fix means a cold profile, not a hard refresh.
Fallbacks hide the error
When the declared icon path fails, browsers request /favicon.ico at the site root. That fallback means a broken configuration still shows an icon, which is exactly why the wrong icon survives a redesign unnoticed.