03
KEEP
ICO file lands on your device.
No cloud, no upload.
What it actually does
01
DECODE
JPG decoded; pixels resampled to standard favicon sizes.
16×, 32×, 48×, and 256× — the canonical resolutions Windows expects.
02
ENCODE
ICO container written with all resampled layers bundled in.
Each layer is a PNG inside the ICO container. Browsers and Windows both handle it.
04
BATCH
Drop multiple JPGs.
Each becomes its own .ico file.
How it works
- Open morph.cool in any modern browser.
- Drop your .jpg 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%Upload
Why it lives in the tab
ICO is the format Windows wants when it's looking for a favicon, an executable icon, or any other glyph the OS plans to show at multiple sizes. The clever part of ICO is that it bundles every size you'd ever need into a single file, so Windows can pick whichever fits the moment. We do the resampling in your browser tab and pack the layers in cleanly.
Frequently asked
What sizes get packed in?
16×16, 32×32, 48×48, and 256×256 — the four sizes Windows looks for in a favicon.
Will the small sizes look ok?
If the source is sharp, yes. Photos with fine detail can lose readability when resampled down to 16×.
Should I use ICO or PNG for a favicon?
ICO is the legacy standard; modern browsers handle PNG favicons too. ICO is safer for cross-browser, especially on older Windows.
Is there a maximum source resolution?
No artificial limit. We resample down to the standard sizes regardless of source size.
Does the conversion preserve color?
Yes, 24-bit color is preserved across all layers.