Favicon Generator
Generate a multi-size favicon.ico plus 16-512 px PNGs from one image.
Overview
The Favicon Generator turns a single source image into a complete favicon bundle: a multi-resolution favicon.ico, individual PNGs from 16 px up to 512 px, and the HTML link tags you need to wire them into a site head. Upload a square image — ideally a logo with even padding — and the tool produces a ZIP that drops straight into a wwwroot/ or public/ directory.
Web developers and designers use it when launching a new site, refreshing a brand mark across browser tabs and mobile home screens, or generating Apple touch icons and Android web app icons from one master file. It is the practical alternative to redrawing the same artwork at six different pixel grids.
How it works
Each output size is produced by downsampling the source image with a high-quality Lanczos filter. The .ico container is then assembled by concatenating PNG-compressed images at standard sizes (16, 24, 32, 48, 64) inside the legacy icon directory header, which browsers select from automatically based on display density.
For sharp results on small sizes the tool aligns the rendered pixel grid to whole-pixel boundaries, which prevents the half-pixel blur that often plagues 16 px favicons resampled from a 1024 px source. The Apple touch icon (180 px) is output without rounded corners — modern iOS adds its own mask — while the Android web manifest icons preserve the original alpha channel.
Examples
Source: logo.png (1024x1024, transparent background)
Output ZIP:
favicon.ico (multi-res: 16, 24, 32, 48, 64)
favicon-16x16.png
favicon-32x32.png
apple-touch-icon.png (180x180)
android-chrome-192x192.png
android-chrome-512x512.png
site.webmanifest
snippet.html (link tags ready to paste)
FAQ
Should the source be a PNG or an SVG?
PNG at 512 px or larger works for all bitmap outputs. For pure-vector favicons consider the SVG to Favicon Generator instead — modern browsers prefer the SVG when both are linked.
Why does the 16 px favicon look fuzzy?
Logos with thin strokes lose detail at 16 px no matter the algorithm. Design a simplified 16-grid version manually for the cleanest result and the tool will pack it into the ICO alongside the larger sizes.
Do I need separate Apple and Android icons?
Yes — Apple expects an opaque 180 px PNG via apple-touch-icon, while Android reads icons from site.webmanifest. The bundle includes both.
Will browsers cache the old favicon?
Aggressively. Bust the cache by appending a query string (?v=2) to the link tag or renaming the file after each release.
Is the manifest file required?
It is needed only for Android home-screen installation and for full PWA support. Drop it if your site doesn't target installable web apps.