PNG to ICO Converter — Multi-Size Favicon Maker
Turn a PNG into a multi-size favicon.ico — 16, 32 and 48 pixels in one file — ready to drop in your site root.
Choose an image to begin.
—
What this tool does
It converts a PNG into an .ico file — the multi-size icon format Windows and browsers
have used for favicons since the beginning of the web. The image is resized to 16, 32 and 48 pixels,
each copy is PNG-encoded, and all three are packed into one file so a single
favicon.ico covers every context that asks for one.
One file, several sizes
| Size | Where it shows |
|---|---|
| 16×16 | Browser tab, bookmark bar, address-bar icon. |
| 32×32 | Higher-density tabs, taskbar shortcuts. |
| 48×48 | Windows desktop shortcut for the site. |
Modern browsers can also use a plain PNG favicon, so many sites ship both — the PNGs for current
browsers and the .ico for everything that still looks for one by name.
How the .ico is packed
An .ico is a small container: a header, a directory entry per image giving its size and
byte offset, then the image data. This tool puts PNG-encoded images inside it, which Vista and every
later Windows — and every current browser — read directly, so there is no bulky uncompressed bitmap
and the file stays tiny.
Everything local
The resizing and packing happen on a canvas in your browser; the .ico is generated and
downloaded without any upload. A brand logo or an unreleased mark never leaves your machine.
Frequently asked questions
What is an .ico file?
A Windows icon file that can hold several sizes of the same image in one file. A browser or Windows shell picks whichever size it needs — 16 pixels for a tab or a small list, 32 or 48 for a larger context — so a single favicon.ico can serve them all without a separate request per size.
Why would I use .ico instead of a PNG favicon?
Modern browsers accept a PNG favicon, but .ico remains the most compatible: some older browsers, Windows shortcuts and tools still expect favicon.ico specifically. Shipping both — the PNGs plus a multi-size .ico — is the belt-and-braces approach that covers every case.
How is the .ico built here?
The PNG is resized to 16, 32 and 48 pixels on a canvas, each resized copy is PNG-encoded, and those PNGs are packed into one .ico container with a directory that points at each image. Vista and later read PNG-compressed icon entries directly, so the file stays small and sharp.
Why these three sizes?
16 and 32 are the sizes a browser tab and a bookmark use, and 48 is what Windows shows for a site shortcut on the desktop. They are the sizes favicon.ico files have carried for years, which is why the tools that look for one expect exactly them.
What should the source PNG be?
Square, since the icon is square and a non-square image will be scaled to fit and may look off-centre. 256×256 or larger gives the cleanest result when downscaled to the small sizes, and a simple, high-contrast mark reads best at 16 pixels.
Is my image uploaded?
No. The resizing and packing happen in your browser; the .ico is generated and downloaded locally and never sent to a server.
Go deeper
Longer explanations of the problems this tool solves:
Sources
- Microsoft — ICO file format (icon directory + PNG entries).
- MDN Web Docs — Link types: rel="icon".
Everything runs in your browser — your file never leaves your device.