Rendered in the browser

Favicon generator

One image in, the whole icon set out — six PNGs, a genuine favicon.ico, a manifest and the exact head markup to paste.

Icons are rendered in this browser tab. Your image is never uploaded.

Short answer: drop a square image of at least 512 px and download the ZIP. It contains 16/32/48/180/192/512 px PNGs, a real favicon.ico, a web manifest and the head snippet with the paths already matched.

Why the .ico still exists

Modern browsers read PNG icons, but Windows shortcuts, some feed readers and older bookmarks still ask for /favicon.ico. Shipping one real ICO file covers those without a 404 in the logs, and it is the file many crawlers request first.

Keep the source square

Icons are square by definition. A non-square image is centre-cropped, which is right for a logo in a circle and wrong for a wordmark. Pad the source to a square first when the whole mark has to survive.

Favicon questions

Why so many sizes?

Browsers pick a 16 or 32 px tab icon, Android installs want 192 and 512, and iOS uses a 180 px apple-touch-icon. Serving one large PNG works badly: the browser scales it with visible blur, so each size is rendered from the source instead.

Is the .ico file real?

Yes — a proper ICO container with PNG payloads and a directory entry per size, written byte by byte rather than renamed from a PNG. Legacy clients and Windows shortcuts read that format, and a renamed PNG shows as a broken icon there.

What image should I start from?

A square image at least 512 px, with the subject centred. Non-square images are centre-cropped rather than squashed, so a wide logo loses its edges — pad it to a square first if the whole mark matters.

Where do the files go?

The ZIP mirrors the paths the head snippet expects: the icons and manifest at the site root. Unzip into your public directory, paste the snippet into <head>, and the browser picks the right file per context.

Related tools