What a favicon actually has to cover
A favicon isn’t one image — it’s the small icon that appears in browser tabs, bookmarks, history, search results, mobile home screens, and PWA install prompts, each of which wants a different size or format. That’s why a one-click generator that produces every variant from a single source image saves real effort. Upload a square image (≥512×512, PNG with transparency or SVG is ideal) and it outputs the icons, the HTML <link> tags, and the manifest files.
The files and where they go
| File | Purpose |
|---|---|
favicon.ico | Universal browser-tab fallback (16/32/48) |
favicon.svg | Crisp, theme-aware modern icon |
apple-touch-icon.png (180) | iOS home-screen bookmark |
android-chrome-192/512.png | PWA install / Android |
site.webmanifest | Declares PWA icons + theme |
All icon files belong in your site root, and the generated <link> tags go in your <head>. Browsers automatically pick the most appropriate icon for each context.
Design for the smallest size
The hardest constraint is the 16×16 tab icon — there are almost no pixels to work with. A detailed logo that looks great on a business card turns to mush at 16px. Favicons that read well use simple shapes, strong contrast, and minimal detail — often a single letter, monogram, or bold symbol rather than the full logo. Always start from the highest-resolution source you have so the downscaling stays clean.
PWA gotchas
If you’re building an installable web app and the install prompt or home-screen icon doesn’t appear, check: the site.webmanifest is served over HTTPS and linked with <link rel="manifest">, the 192 and 512 icons exist at the referenced paths with the correct image/png MIME type, and DevTools → Application → Manifest shows no errors. These four conditions are the usual culprits.