PNG to favicon
Have a PNG logo? Turn it into a real favicon.ico and every size your site needs — resized, packaged and ready to drop into your site root.
Open the favicon generator →How it works
Drop your PNG into the generator. GenHub reads it as an image, then draws it onto a canvas at 16, 32, 48, 180, 192 and 512 pixels. The 16/32/48 renders get packed into a single hand-written favicon.ico container; the 180, 192 and 512 renders are saved as standalone PNGs — apple-touch-icon.png, android-chrome-192x192.png and android-chrome-512x512.png. A site.webmanifest and the HTML snippet come bundled in the same ZIP. Every step happens in your browser — your PNG never touches a server.
Why a real .ico still matters
A .ico is a container that holds several resolutions at once, so the browser can pick the crispest one for each context. Some "PNG to favicon" tools just rename a single PNG to favicon.ico — that loads in some Chromium builds but breaks in Safari and anything that actually parses the ICO header expecting a real structure. GenHub writes an authentic ICO: a 6-byte header, one directory entry per image, and PNG-encoded payloads at each offset, which is exactly what browsers have parsed since ICO's 32-bit-color support arrived.
PNG vs ICO vs SVG favicons
Modern browsers can read <link rel="icon" type="image/png"> directly, and some (Chrome, Firefox) support SVG favicons that can switch between light and dark variants via a prefers-color-scheme query inside the SVG. But favicon.ico is still the one file every browser and crawler falls back to when nothing else is specified — which is why GenHub always includes it even though you're starting from a PNG.
Preparing your source PNG
- Start square — 512×512 or larger downsamples cleanly to every smaller size.
- Transparency is preserved through the conversion, so a logo on a transparent background stays clean at every size except the apple-touch-icon, which always gets a solid backing (iOS renders transparency as black on some versions).
- Avoid fine detail or small text — anything intricate disappears at 16px. Preview the shrunk-down version before committing.
What's in the download
The ZIP contains favicon.ico, favicon-16x16.png, favicon-32x32.png, apple-touch-icon.png, android-chrome-192x192.png, android-chrome-512x512.png, site.webmanifest, and the paste-in <head> snippet — everything needed to drop into your site root and go live.
PNG logo vs PNG photo
Favicons work best from a simple, high-contrast mark — a logo, initial or icon — rather than a detailed photograph. A photo downscaled to 16px usually turns into an unrecognizable smear of color, since there just isn't room for fine detail at that size. If you only have a full logo lockup with text, crop it to just the icon or initial before converting; a wordmark reads as a blur at favicon sizes no matter how good the source PNG is.
FAQ
Will transparency be preserved?
Yes. PNG alpha is kept through the conversion, so rounded or transparent logos stay clean — except on the apple-touch-icon, which is always given a solid background.
Is there a watermark?
No. Free downloads are clean — no logo is added to your favicon.
Do I need to resize my PNG myself first?
No — upload any reasonable size (ideally 512×512 or larger) and GenHub handles every resize on canvas.
Can I use a non-square PNG?
You can, but it will be cropped or padded to a square before rendering — for predictable results, crop it square yourself first.
My PNG has a logo and text together — will it still work?
It will convert, but text usually becomes unreadable at 16–32px. For best results, crop to just the icon mark and drop the wordmark for favicon use.