Turn one image into a complete favicon set in your browser — 16 to 512 px PNGs, a multi-size favicon.ico and the install HTML. Nothing is uploaded. Runs entirely in your browser — your numbers never leave this device.
No image loaded yet. A square source of at least 512 × 512 gives the crispest set; smaller or rectangular images are centre-cropped to a square and scaled, on this device only.
| Size (px) | Download filename | Used by |
|---|---|---|
| 16 × 16 | favicon-16x16.png | Browser tabs at standard density |
| 32 × 32 | favicon-32x32.png | Retina browser tabs, Windows taskbar |
| 48 × 48 | favicon-48x48.png | Windows desktop shortcuts |
| 180 × 180 | apple-touch-icon.png | iPhone / iPad home-screen bookmarks |
| 192 × 192 | android-chrome-192x192.png | Android home screen, web app manifest |
| 512 × 512 | android-chrome-512x512.png | Android splash screens, high-density manifest icon |
| 16 + 32 + 48 | favicon.ico | The classic default browsers request at /favicon.ico |
A modern site needs more than one icon: browsers ask for 16 and 32 px tab icons, Windows shortcuts want 48, an iPhone home-screen bookmark wants a 180 × 180 apple-touch-icon, and Android's manifest wants 192 and 512. This generator renders the whole set from a single image. Because every favicon is square, a non-square source is first centre cover-cropped — the largest centred square the image contains (an 800 × 600 photo contributes its middle 600 × 600, from x = 100 to x = 700) — and that square is then scaled to each size, so the subject stays centred and nothing is stretched.
Alongside the PNGs it assembles a real favicon.ico: not a renamed PNG, but the ICO container format — a six-byte header, one sixteen-byte directory entry for each of the 16, 32 and 48 px renders, and the three PNG payloads packed after them, each entry pointing at its payload's offset and length. The page also prints the two snippets that install the set: the link tags for your HTML head (which reference exactly the filenames the downloads use) and a site.webmanifest with the Android icons declared, each with a copy button.
Rendering happens entirely in your browser: the source image is decoded locally, every size is drawn and encoded locally, and the ICO is packed in memory. Your logo or photo is never uploaded to a server — there is no upload step in the tool at all, and it works offline once the page has loaded.
No. The source image is decoded, cropped, rendered at every size and packed into the ICO entirely inside your browser. Nothing leaves your device and nothing is stored — the generator works offline once the page has loaded.
favicon.ico covers the classic browser tab, and this generator builds a proper multi-size one (16, 32 and 48 px inside a single file). But phones never read it: an iPhone home-screen bookmark asks for the 180 × 180 apple-touch-icon, and Android installs use the 192 and 512 px manifest icons. The set covers every requester so no device falls back to a blurry upscale or a screenshot thumbnail.
A square PNG of at least 512 × 512 with a simple, bold mark and some padding around it. Fine text and thin lines disappear at 16 px no matter what generator you use — if your logo has a detailed and a simple version, feed the tool the simple one. Transparency is preserved in the PNG renders.
Download the files, put them at your site's root with the exact filenames offered (favicon.ico, favicon-16x16.png, apple-touch-icon.png and so on), save the manifest snippet as site.webmanifest at the root too, and paste the HTML snippet into your pages' <head>. The snippet's hrefs match the download filenames, so no editing is needed unless your files live in a subfolder.
Because it contains three PNGs, not one: 54 bytes of header and directory entries plus the 16, 32 and 48 px payloads. In the worked example that is 54 + 612 + 1,108 + 1,874 = 3,648 bytes. Browsers pick the size they need from inside the file.
More in Image Tools · Browse all tools