Favicon / ICO Generator
A real multi-size favicon.ico plus the PNGs modern browsers use — no upload.
Your image
Processed in your browserHow this processes your file
The image is cropped to a square from its centre, then each icon size is rendered from the original — never downscaled from the previous, smaller icon, which would compound the softening three times over by the time it reached 16 pixels. The ICO container is assembled here in the page: a header, one directory entry per size, and the PNG data itself, which is what every modern generator emits and what browsers have accepted since Vista. The size list is deliberately short. Guides that produce twenty files are describing an era when every phone wanted its own icon; today it is the ICO for legacy, one Apple touch icon, and two sizes for the web manifest.
What the results mean
- favicon.ico
- Contains 16, 32 and 48 pixel versions in one file. Still requested by convention from the site root, including by browsers that never read your HTML.
- apple-touch-icon (180px)
- What iOS uses when someone adds your site to their home screen. iOS scales this one file for every device.
- 192 and 512 px
- Referenced from a web app manifest for Android home screens, install prompts and splash screens.
- Centre-cropped
- The source was not square, so a square was taken from the middle. Check the previews to make sure the mark survived it.
Common problems and fixes
- The 16px icon is an unreadable smudge
- Most logos are. Make a simplified mark for the small sizes — a single letter or shape — rather than shrinking a detailed logo into 256 pixels of space.
- My new favicon does not show up
- Browsers cache favicons hard, often past a normal refresh. Try a private window, or load /favicon.ico directly to confirm the file is being served.
- The large icons look soft
- Your source is smaller than 512 pixels, so they were enlarged. Re-run from a larger original or an SVG exported at 512.
Frequently asked questions
What favicon sizes do I actually need in 2026?
Four files cover everything that matters: a favicon.ico containing 16, 32 and 48 for legacy requests, an SVG for browsers that support it and scale it perfectly, a 180-pixel apple-touch-icon for iOS home screens, and 192 and 512 PNGs referenced from a web manifest for Android. Lists longer than that are describing platform requirements that no longer exist.
Is favicon.ico still required?
Not by the standards, but yes in practice. Browsers and other clients still request /favicon.ico from the site root without reading your HTML first, and a 404 for it appears in every log. It is a small file and it removes a whole class of noise.
Is my logo uploaded to a server?
No. Every size is rendered on a canvas in your browser and the ICO container is assembled here in the page. That matters more than it sounds for a favicon generator — a logo is often the first public asset of a product nobody has announced yet.