Dedicated, format-locked workflow
Create a practical ICO favicon from a PNG
Generate common embedded icon sizes while keeping existing PNG transparency and explaining what tiny icons can show.
Conversion settings
Multi-size icon output for favicons and Windows shortcuts.
Locked: PNG → ICO
Drop images here or choose files
PNG input only · 50MB each · 20 files per batch
Why this workflow exists
ICO remains useful for browser and Windows compatibility.
A multi-size container lets software choose an appropriate embedded icon resolution.
Browsers request favicon.ico automatically even when no markup declares it.
What PixelConvert does with a PNG file
The server validates the PNG signature, decodes the image with its alpha channel, and writes an ICO containing common embedded sizes from 16×16 up to 256×256 where the source dimensions support them. Existing transparency is preserved in each embedded size.
The output is a container holding several rendered icons, so its byte size is not comparable to a single PNG canvas. Our measured example turned an 11,839-byte source into a 30,353-byte ICO, which is normal and not worth optimising.
Design for 16 pixels, not for your screen
A favicon is displayed at roughly 16 by 16 pixels in a browser tab — 256 pixels in total, fewer than a single letter of this sentence uses. Everything about favicon design follows from that number.
Judging the design at any other size is the near-universal mistake. A mark that looks clean and detailed at 400 pixels can be an unrecognisable smudge at 16. The only reliable test is to look at it at actual size, in an actual browser tab.
A bigger source does not fix a bad favicon
When a favicon looks wrong, the instinct is to supply a higher-resolution PNG. It almost never helps. Downscaling to 16 pixels averages large areas of the source into single output pixels, so a 1024-pixel source and a 256-pixel source produce nearly identical results.
What does help is changing what is being averaged. A thin 2-pixel stroke in a 256-pixel design becomes an eighth of a pixel at tab size and vanishes. Making the stroke thick enough to still occupy a visible fraction at 16 pixels is a design change, not a resolution change — and it is the one that works. Reduce the number of shapes, thicken the strokes, raise the contrast.
Preparing the source
Start square and crop tight. If the mark floats in a large transparent canvas, it occupies only a fraction of the final 16 pixels and every wasted pixel counts. Use a symbol rather than a wordmark — a logo with the company name becomes illegible at tab size, and a single initial is often the right answer.
Check the mark against both light and dark browser themes before committing. A dark mark on a transparent background looks correct in a light-themed browser and can disappear entirely against a dark tab strip.
Verified format differences
| Property | PNG source | ICO result |
|---|---|---|
| Container | One raster canvas | Multiple embedded icon sizes |
| Transparency | Supported | Preserved |
| Typical size | 11,839 bytes in our test | 30,353 bytes as a multi-size ICO |
| Best source | Square, simple mark | Favicon or shortcut icon |
How to use PNG to ICO
- Step 1Use a square PNG with little empty space.
- Step 2Convert to the locked ICO output.
- Step 3Test the downloaded file at 16px, 32px, and in a browser tab.
Good use cases
- Website favicon fallback
- Windows shortcut icon
- Desktop application prototype icon
Limitations to check
- Fine text and detailed photographs are difficult to recognize at 16 or 32 pixels.
- Start with a square, high-contrast PNG and always inspect the icon at real display size.
- Embedded-size availability depends on the source dimensions.
Questions answered
- Which sizes are included?
- PixelConvert requests common sizes from 16×16 through 256×256 where the source supports them, so software can pick an appropriate resolution for its display slot.
- Can a photo work as a favicon?
- It can convert, but simple high-contrast artwork is far more recognisable. At 16 pixels a photograph averages into an indistinct blur.
- Will a higher-resolution source make it sharper?
- No. Downscaling to 16 pixels averages away the extra detail regardless of where it started. Simplify the design instead — thicker strokes, fewer shapes, higher contrast.
- I replaced the favicon but nothing changed.
- Browsers cache favicons aggressively and they survive ordinary refreshes. Use a private window, a hard refresh, or a changed filename.
- Do I still need an ICO, or can I use a PNG?
- Modern browsers accept PNG and SVG icons declared in markup. An ICO at the site root remains a useful fallback because browsers request it automatically. Most frameworks handle both.
Troubleshooting PNG to ICO
The browser still shows my old favicon
Why: Favicons are cached aggressively and survive an ordinary page refresh.
Fix: Open a private window, hard-refresh, or change the filename to force a new request. The conversion is almost certainly fine.
The icon is an unrecognisable blur
Why: Too much detail for 16 pixels — thin strokes, small text, or subtle gradients.
Fix: Simplify the source: fewer shapes, thicker strokes, higher contrast. A larger source file will not help.
The icon disappears in dark mode
Why: A dark mark on a transparent background has no contrast against a dark tab strip.
Fix: Choose a colour with contrast against both themes, or add a light shape behind the mark.
The ICO is bigger than my PNG
Why: An ICO holds several rendered sizes in one container.
Fix: Expected. Our measured example produced a 30,353-byte ICO from an 11,839-byte PNG. It is not worth optimising.