ConversionMarch 12, 20265 min read

How to create a favicon – convert PNG to ICO the easy way

The tiny image in your browser tab is the favicon, and it's essential for any site that wants to look professional. Modern web increasingly leans on PNG and SVG, but the classic ICO format remains relevant: it works in every browser, on every system.

Browser tab with favicon and ICO file icon

Which sizes a favicon needs

A good favicon contains multiple resolutions: 16×16, 32×32, 48×48 and 64×64 pixels. Browsers show different sizes in different contexts — small in the tab, larger in bookmarks, bigger again on hi-DPI displays.

ICO is a container and can bundle all these sizes into one file. You drop a single `favicon.ico` in the site root and you're done.

Convert PNG to ICO online

Start with a square PNG of at least 256×256 pixels and a transparent background. On Pixshift, pick ICO as the target — the tool generates every standard size into the container automatically.

Important: the motif has to read at 16×16. Detailed logos may need a simplified version for the smallest size, or you isolate the central shape. Always test locally before deploying.

Hooking up the favicon

Place `favicon.ico` in your site root and add `<link rel="icon" href="/favicon.ico">` to `<head>`. Modern devices benefit from a PNG set on top: `<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32.png">` and so on.

iOS and Android use their own apple-touch-icons at 180×180. To get it fully right, also generate `apple-touch-icon.png` and a `manifest.json` for progressive web apps.

Do you still need ICO at all in 2026?

Modern browsers happily use SVG or PNG favicons. But: Microsoft Edge legacy, Outlook mail previews and a handful of search crawlers still reach for favicon.ico. If reach matters, ship both.

Mandatory set in 2026: favicon.ico (16/32/48 px) in the root + favicon.svg for modern browsers + apple-touch-icon.png (180x180) + manifest.webmanifest with 192/512 PNG for PWAs. Three minutes of work, three years of calm.