Why one PNG isn’t enough
Browsers use 16 px icons in tabs and 32 px in bookmark lists and pinned tabs; 48 px covers older Windows shortcuts; iOS reads a 180 px apple-touch-icon when someone adds your site to a home screen; and Android along with the PWA install prompt pulls 192 and 512 px PNGs from the manifest. The .ico file is the awkward part to build by hand — it’s a container most editors can’t write, and it works best with the 16, 32, and 48 px versions bundled inside so each browser picks the size it wants instead of scaling one bitmap badly. That bundling is exactly why tiny favicons from single-size generators so often look blurry.
Step by step
- Prepare a square source image of at least 512 × 512 pixels. Icons scale down cleanly but never up, and if your logo is strongly rectangular, crop it square first so nothing important gets trimmed at the edges.
- Open the Favicon Generator on SafeFileConvert and drop the image onto the dropzone. There are no settings to study — the standard sizes are what every site needs.
- Download the ZIP. Inside are a favicon.ico with 16, 32, and 48 px layers, a 180 × 180 apple-touch-icon.png, the 192 and 512 px PNGs for Android and web app manifests, and a ready-to-paste HTML snippet, so you don’t have to look up the link tags.
- Upload the files to your site root — or wherever the snippet’s paths point — and paste the provided link tags into the <head> of your pages.
Design notes for icons that survive 16 pixels
Simple, high-contrast shapes hold up all the way down to tab size; fine text and thin lines turn to mush. If the smallest sizes look muddy, simplify the mark rather than fighting the scaler. And although modern browsers accept PNG and SVG icons through link tags, keep shipping the favicon.ico as well — many browsers, crawlers, and older clients still request /favicon.ico directly, and having the file there avoids 404s and missing icons.
Unreleased branding stays confidential
All the resizing and ICO encoding run on your own device, inside your browser. That’s a practical privacy point for designers and agencies: an unreleased logo or a client’s unannounced rebrand is never exposed to a third-party server, because no server is involved at any step of the generation. There’s no account to create, no watermark on the output, and no cap on how many icon sets you generate while you iterate on the design.