PNG to ICO Converter
Turn any image into a multi-size Windows ICO file — the classic favicon.ico format.
No data sent to serverRelated Tools
ICO Is a Container, Not an Image Format
This is the part that surprises people. An .ico file does not hold one icon — it holds a small collection of them at different sizes, and whatever is displaying the icon picks the closest match. A browser tab wants 16×16 or 32×32, a Windows desktop shortcut wants 48×48, and the taskbar in a high-DPI display may reach for 256×256.
That is why a single 512×512 PNG renamed to .ico looks smeared in a browser tab. The browser has to shrink it on the fly with a generic filter, losing the crispness that a purpose-made 16-pixel version would have. Packing several sizes into one file lets each context use an image drawn for it.
Which Sizes to Include
- 16×16 — browser tabs, address bar, bookmarks. Essential.
- 32×32 — high-DPI tabs, Windows taskbar, shortcuts. Essential.
- 48×48 — Windows desktop icons and file listings. Recommended.
- 64, 128, 256 — large icon views and Retina displays. Optional, and each one adds file size.
16, 32, and 48 is the practical default and keeps the file under about 15 KB. Adding 256 can triple that for a size most visitors never see.
Designing for 16 Pixels
A logo that reads beautifully on a business card usually turns to mush at 16×16. There is simply not enough room for fine strokes, gradients, or text. The icons that survive shrinking share the same traits: one bold shape, high contrast against both light and dark tab bars, and no lettering beyond a single initial.
If your source is a detailed logo, consider making a simplified mark specifically for the icon rather than feeding the full logo through a resizer and hoping.
Technical notes
- Encoding: each size is stored as a PNG inside the ICO container, supported by every browser since Internet Explorer 11 and by Windows Vista onward
- Transparency: preserved through the alpha channel — no separate mask needed
- Non-square input: scaled to fit and centred rather than cropped, so nothing is cut off
- Resampling: high-quality browser smoothing
- 256×256: written with a dimension byte of 0, which is how the ICO specification encodes 256
Where ICO Files Are Still Required
The format looks archaic, and it survives because of defaults rather than merit. Browsers request /favicon.ico from the site root automatically, with no markup involved, so a site without one generates a steady trickle of 404s. Windows uses ICO for desktop shortcuts, pinned taskbar items, and file type associations. Some older content management systems and site builders accept nothing else for the site icon.
None of that is likely to change soon, which is why an ICO remains worth generating even on a site that also serves modern PNG or SVG icons.
Making a 16-Pixel Icon That Reads
At 16×16 you have 256 pixels to work with, and a logo designed for a business card will not survive the trip. The icons that do share a few characteristics.
One shape, not a composition. A single bold mark reads; a wordmark with three elements becomes mush.
Heavy strokes. Anything thinner than about two pixels at final size either disappears or turns grey through anti-aliasing.
Contrast against both light and dark. Tab bars differ by browser and theme, so a design that relies on being dark vanishes in a dark tab.
At most one letter. Two characters at 16 pixels are already unreadable.
The practical approach is to design the icon separately at 16 pixels rather than shrinking the logo and accepting whatever comes out.
FAQ
Can I just use a PNG as my favicon?
Yes, modern browsers accept PNG favicons via a link tag. ICO still earns its place because browsers automatically request /favicon.ico at the site root even with no markup, and Windows uses ICO for shortcuts and pinned sites.
Where do I put the file?
At the root of your site as favicon.ico. That path is requested automatically. Adding <link rel="icon" href="/favicon.ico" sizes="any"> makes it explicit.
My new favicon isn’t showing up.
Favicons are cached aggressively — often beyond a normal hard refresh. Try a private window, or load the icon URL directly to confirm the new file is being served.
Does transparency work?
Yes. The alpha channel is carried into each embedded PNG, so rounded and irregular shapes sit correctly on light and dark backgrounds.
Can I convert an SVG?
Yes. The SVG is rasterised at each requested size, which actually produces sharper small icons than downscaling a large PNG.
Can I convert a JPG or SVG rather than a PNG?
Yes. Any image the browser can decode works, and SVG in particular produces sharper small icons because it is rasterised fresh at each size rather than downscaled from one bitmap.
Does adding more sizes hurt anything?
Only file size. Each embedded size adds bytes to a file that is requested on every page load, so 16, 32, and 48 is the practical set unless you specifically need the large variants.
My logo turns to mush at 16 pixels. What should I do?
Design a simplified mark specifically for the icon — a single bold shape, thick strokes, at most one letter. Shrinking a detailed logo rarely produces a usable favicon.
Should the icon have a background?
Often yes. A solid shape behind the mark guarantees contrast in both light and dark tab bars, where a transparent icon in a single colour can disappear entirely.
⚠️ Reference Only
Output is generated based on your input and is provided for reference. Results may vary depending on your specific use case, edge cases, or environment-specific behavior. We do not guarantee accuracy of conversions, validations, or computed values.
Always verify critical outputs against official documentation or production environments. We are not responsible for any decisions or losses based on these tool results.