Convert PNG to ICO
100% private — runs on your device, never uploaded. Works offline once loaded.
Convert a PNG image into a Windows .ico file containing sizes from 16 to 256 pixels. Everything runs locally in your browser.
What an .ico file actually contains
Unlike a PNG or JPG, an ICO file isn't a single image — it's a small container that can hold several versions of the same picture at different pixel sizes, all bundled into one file. Windows and browsers pick whichever size fits the context: a tiny 16×16 version for a browser tab or file explorer list view, larger versions for desktop shortcuts, taskbar icons, or high-DPI displays. This tool takes your one PNG and generates that full set of sizes automatically, packed into a single .ico.
Where you actually need one
The classic use case is a website's favicon.ico — the icon shown in browser tabs, bookmarks, and search results. Even though modern browsers also accept PNG or SVG favicons declared via a link tag, having a favicon.ico at the site root is still checked automatically by many browsers and by tools like Google Search Console as a fallback. ICO is also the required format for Windows desktop application icons and .exe file icons.
Getting good results
Since the tool has to shrink your image down to 16×16 pixels for the smallest size, start with a source PNG that's simple and recognizable at a glance — fine detail and thin text tend to disappear at that resolution. A square image works best; non-square PNGs get resized to fit each square icon slot, which can distort the proportions. Transparency in your PNG's alpha channel is carried through to every generated size, so icons will sit cleanly on any background color.
- Included sizes: 16×16, 32×32, 48×48, 64×64, 128×128 and 256×256 pixels.
- Start from a square PNG for undistorted results.
- Simple, high-contrast designs hold up best at the smallest 16px size.
A practical favicon workflow
If the icon is for a website, start with a larger square PNG master, generate the ICO, then test it in a real browser tab before you publish. The tiny 16px size is the harshest test, and it exposes whether a logo is too detailed long before users see it. For app icons, it also helps to keep the original PNG alongside the ICO, since other platforms may still ask for PNG files at larger sizes even if Windows itself wants the .ico container. In short: use PNG as the editable source, ICO as the compatibility output.
Frequently asked questions
What sizes are included?
16, 32, 48, 64, 128 and 256 pixel versions in one .ico file.
Are my images uploaded?
No — everything is generated on your device.
What sizes end up in the final .ico?
The generated file bundles 16, 32, 48, 64, 128 and 256 pixel versions of your image together, and Windows or the browser automatically picks the right one for each context.
Does my PNG need to be square?
It's strongly recommended — a non-square source gets resized to fit each square icon slot, which can visibly stretch or squash the image.
Will transparency in my PNG be kept?
Yes, the alpha channel is preserved in every generated size, so the icon won't have an unwanted white or black box behind it.
Is favicon.ico still needed if I already use a PNG or SVG favicon?
It's good practice to keep one — some browsers and crawlers still request /favicon.ico directly as a fallback even when a site declares a different favicon format in HTML.
Why does my icon look blurry or unclear at the smallest size?
Fine detail and small text don't survive being shrunk to 16×16 pixels; simple, bold shapes with strong contrast hold up far better at that size than a busy or highly detailed logo.
Can I use this for a Windows application icon, not just a website favicon?
Yes — the multi-size .ico this generates is the same format Windows expects for desktop shortcut and .exe application icons.
Should I design the icon directly at 16×16?
Usually no. It is better to design from a larger square PNG, then test how it survives shrinking. Working larger gives you flexibility, while the generated 16px version tells you whether the mark stays recognizable.
Why keep the original PNG if the ICO already contains multiple sizes?
Because many modern workflows still ask for standalone PNG icons in addition to favicon.ico. Keeping the source PNG makes it easy to generate Apple touch icons, PWA icons, or updated favicon sets later.
Advertisement