Favicon Generator - Every Size a Site Needs
Upload one square image and get the complete set of icon sizes browsers, iOS and Android actually ask for, generated in your browser with nothing uploaded.
Convert any image into a complete set of website icons with our private favicon converter.
Supports PNG, JPG, WebP. Best results with square images.
Why one favicon file is not enough any more
For years a single favicon.ico in the site root did the job. That stopped being true once phones, tablets, high-DPI displays and installable web apps all started asking for icons at their own sizes and in their own formats. A modern site needs a small set rather than a single file.
The sizes that actually matter are few. 16x16 is the browser tab and the address bar, and it is the hardest one to design for. 32x32 covers the taskbar, bookmark bars and retina tabs. 180x180 is the Apple touch icon used when someone adds your site to an iOS home screen. 192x192 and 512x512 are the Android and PWA manifest sizes, the larger one used for splash screens.
Designing for 16 pixels is the part people underestimate. At that size a detailed logo becomes an unreadable smudge, because there simply are not enough pixels to carry fine strokes, gradients or text. The favicons that work are drastically simplified: a single bold letterform, one distinctive shape, or a solid colour block with high contrast against both light and dark browser themes. If your full logo has fine detail, design a reduced mark for the small sizes rather than shrinking the whole thing.
Start from a square source at 512 pixels or larger so every size is downsampled rather than enlarged, and keep a little padding around the mark since some platforms round the corners or crop to a circle. Everything is generated in your browser, so an unreleased brand identity is never uploaded.
How to generate a favicon
- Start from a square image, 512px or larger. Downsampling looks clean; enlarging does not.
- Simplify the design first. One letter or one bold shape survives 16x16. A detailed logo will not.
- Upload and generate. The full size set is produced at once.
- Check the 16x16 at actual size. This is the one that decides whether the favicon works. If it is unreadable, simplify further and repeat.
- Download and add the link tags to your HTML head, plus the icon entries in your web app manifest if you have one.
Test against both light and dark browser themes, since a dark mark on a transparent background vanishes in dark mode. Use the rounded corners tool if you want the shape pre-rounded, and SVG to PNG to rasterise a vector logo cleanly at 512 first. Full guide: how to create a favicon.
Frequently asked questions
Which favicon sizes do I actually need?
16x16 for the browser tab, 32x32 for taskbar and bookmarks, 180x180 for the iOS home screen, and 192x192 plus 512x512 for Android and PWA manifests.
Why does my logo look like a smudge at 16x16?
There are not enough pixels to carry fine strokes, gradients or text. Favicons that work are drastically simplified: one bold letterform, one distinctive shape, or a solid high-contrast block.
What size should my source image be?
Square and at least 512 pixels, so every output size is downsampled rather than enlarged. Leave a little padding, since some platforms round the corners or crop to a circle.
Does it work in dark mode?
Test it. A dark mark on a transparent background disappears against a dark browser theme, so a favicon needs contrast against both.
Do I still need favicon.ico?
PNG icons declared with link tags cover current browsers. Keeping an .ico in the site root is a harmless fallback for very old clients that request it by default.
Is my logo uploaded?
No. All the sizes are generated in your browser, so an unreleased brand identity stays on your machine.
🔎 Verify it yourself: nothing uploads
Don’t take our word for it. Open your browser’s DevTools (F12 → Network tab), then run this tool on any image. You’ll see no upload request at all — your file never leaves this tab. You can even turn off Wi‑Fi once the page has loaded and keep working. Every tool on this site works the same way — all processing happens on your device.