Drop in one square image and get favicon.ico, apple-touch-icon, and PWA-ready PNGs with matching HTML — generated entirely on your own device.
From one square source image, the generator produces the complete set most sites need: a favicon.ico containing 16, 32, and 48 px versions; a 180 × 180 apple-touch-icon.png; and 192 and 512 px PNGs for Android and web app manifests. A ready-to-paste HTML snippet is included, so you do not have to look up the link tags, and everything downloads as a single ZIP.
The sizes are not arbitrary. Browsers use 16 px icons in tabs and 32 px in bookmark lists and pinned tabs, while 48 px covers older Windows shortcuts. iOS reads the 180 px apple-touch-icon when someone adds your site to their home screen, and Android along with the PWA install prompt pulls the 192 and 512 px PNGs from the manifest.
Bundling three resolutions into a single .ico file lets each browser pick the version it wants rather than scaling one bitmap badly, which is why tiny favicons from single-size generators often look blurry.
Start from an image of at least 512 × 512 pixels — icons scale down cleanly but never up. Simple, high-contrast shapes survive the trip down to 16 px; fine text and thin lines turn to mush. If your logo is strongly rectangular, crop it square first so nothing important gets trimmed at the edges.
All resizing and ICO encoding run on your own device, which also means an unreleased logo or a client's unannounced branding stays confidential until you decide to ship it. There is no account to create and no cap on how many icon sets you generate.
No. The image is resized and encoded to ICO and PNG entirely inside your browser, so pre-launch designs are never exposed to any server.
A favicon.ico with 16, 32, and 48 px layers, a 180 px apple-touch-icon, 192 and 512 px PNGs, and an HTML snippet — packaged together in one ZIP.
Place them in your site root, or wherever the snippet's paths point, then paste the provided link tags into the <head> of your pages.
Modern browsers accept PNG and SVG icons via link tags, but many browsers, crawlers, and older clients still request /favicon.ico directly, so shipping one avoids 404s and missing icons.
Close to square works best. If the image is noticeably wide or tall, crop it square beforehand so the important part of the design is not lost at small sizes.