03
KEEP
Both files stay local on your device.
No cloud, no upload.
What it actually does
01
DECODE
PNG decoded by the browser. Alpha channel preserved.
Lossless input. Sharp at every pixel.
02
ENCODE
Resampled to 16×, 32×, 48×, 256× and packed into one ICO.
Each layer is a PNG inside the ICO container. Alpha intact across all sizes.
04
BATCH
Drop a folder of PNGs.
Each becomes its own .ico.
How it works
- Open morph.cool in any modern browser.
- Drop your .png file onto the drop zone, or click to browse.
- Pick ICO as the output format.
- Download your converted .ico file. Done in seconds.
0sizesLayers
0%Alpha
Why it lives in the tab
PNG is the modern lossless image format. ICO is the multi-resolution Windows favicon container. The conversion is mostly a packaging operation — resample the source to four canonical sizes and bundle them. We do it in your browser tab so the file never has to round-trip through a service.
Frequently asked
Why use PNG as the source for an ICO?
PNG already supports transparency and lossless compression. It's the cleanest possible input for a favicon.
What sizes get packed in?
16×16, 32×32, 48×48, 256×256 — the four sizes Windows expects.
Does transparency carry over to all sizes?
Yes. Modern ICO uses PNG-encoded layers; full alpha is preserved at every resampled size.
Will the small sizes look ok?
If your source is sharp at high resolution, the resampled small sizes will be clean. Detailed photos may lose readability at 16×.
Should I use ICO or PNG as a favicon?
ICO is the safest bet for cross-browser, especially older Windows. Modern browsers also handle PNG favicons.