A complete favicon set, from one upload
Upload a logo or image and this tool generates every size modern browsers, iOS, Android and Windows actually
request: eight standard favicon sizes, a real multi-resolution favicon.ico, four Apple touch icon
sizes, two Android/PWA icon sizes, and a Windows tile - 18 files in total, downloadable individually or together
as one ZIP, plus the exact HTML to paste into your page's <head>.
What's "AI" about it
Most uploaded logos aren't a perfect square, so before generating anything, the tool checks whether the image is already square and whether it has transparency. A square image is used as-is; a transparent one is centered on a transparent canvas; and a non-square, non-transparent image is centered on a square canvas filled with a color sampled from its own edges, rather than being stretched or harshly cropped. That's a plain read of the image's own pixels, not a trained AI model - and the "Fit" dropdown lets you override it (crop to square, or pad with a color or transparency of your choice) any time.
Why favicon.ico is still worth generating
Most sites get by on PNG favicons alone today, but favicon.ico is still what a browser falls back
to when nothing else matches, and some older software only ever looks for it. This tool builds a real one -
a proper multi-resolution file containing the 16, 32 and 48 pixel versions together in a single .ico,
not just a renamed PNG.
Why so many separate sizes
A browser tab, an iOS home-screen icon, an Android app icon, and a Windows Start tile are all rendered at different physical sizes, by different operating systems, with different expectations. Supplying each context its own correctly-sized file means every one of them gets a crisp icon rendered at its native size, instead of one size stretched, shrunk, or (worse) auto-cropped unpredictably by the browser.
site.webmanifest and browserconfig.xml
Modern Android/Chrome PWA support and Windows Start-menu tiles are both driven by a small config file rather
than just a <link> tag - site.webmanifest for the former, browserconfig.xml
for the latter. Both are generated automatically alongside the icons themselves (visible under "Advanced" above),
already pointing at the right filenames, so there's nothing left to hand-write.
Starting with a good source image
Every size here is scaled down from one working copy of your image, never scaled up - so a larger, simpler logo gives the best results throughout. A busy, detailed logo can lose legibility at 16×16, the smallest size a browser tab actually uses; a bold, high-contrast mark tends to stay readable at every size this tool produces.