Drop image or click to upload
About Image to ICO
This image to ICO converter transforms PNG, JPEG, and WebP images into ICO icon files locally in your browser. ICO is the Windows icon format: a file begins with an ICONDIR header followed by multiple ICONDIRENTRY directory entries, each embedding bitmap data at a different size. This tool generates multi-size ICO files (16x16 up to 256x256), using the Canvas 2D API to scale the source image into each target size and encode all of them into one ICO container. A common misconception is that an icon is just one size — in practice Windows and browsers pick the best entry for each scenario (taskbar, tab, address bar, context menu) and for the display's DPI scaling, so shipping multiple sizes gives crisp results everywhere. It is best to start from a square, subject-centered image so it reads well even at 16x16. Output works directly as a favicon.ico in a site root or as a Windows application icon, and everything runs locally so brand assets never leave your device. An icon file usually bundles several sizes, the clearest difference from an ordinary image. A browser picks differently by context — tab, bookmark bar, desktop shortcut and taskbar each need their own size — so shipping one size forces scaling elsewhere and looks soft. List the sizes from the intended uses rather than producing a single largest one. Format choice follows the use case rather than the one that sounds most advanced. The bitmap icon format is more dependable for multi-size bundling and older environments, while the web vector scheme scales crisply to any size but covers fewer old browsers. Offer both: the vector for modern browsers and a multi-size bitmap as a compatibility fallback and for system icons. Edge quality on transparency depends on whether the source was smoothed. Converting artwork with anti-aliased edges blends the semi-transparent pixels with whatever sits behind after shrinking, leaving a light or dark halo that also differs between a light and a dark theme. View the result on both backgrounds to confirm no halo appears. The size ladder should cover the tiers actually used rather than a few arbitrary integers. The system picks the nearest available size and scales from there, so a large gap in the ladder widens the scaling and loses sharpness. Derive the ladder from the platform common tiers and verify the file really contains each listed size. Generating from a vector source is more reliable than from a bitmap, most obviously when many sizes are needed. A vector renders afresh at each size, keeping strokes and corners consistent across tiers, while shrinking a bitmap blurs progressively and makes sizes look unlike each other. Where a vector original exists, prefer it for the whole set. Finally, weigh file size against file count. Bundling sizes into one file cuts requests but grows the file, while splitting them loads on demand at the cost of more requests and more items to maintain. For a heavily visited site fewer requests usually matter more; for size-sensitive cases on-demand loading wins. Decide by traffic pattern, not preference.
How It Works Internally
An icon file may contain several sizes and the system picks the most suitable for each context, so shipping a single size means scaling elsewhere. Icons are also commonly 32-bit with alpha, and converting to a format without it leaves a background square outside the rounded corners. Prepare one size per use case and package them together.
Shipping only a 256×256 sizeSmall contexts such as a taskbar scale it down and blur it; include 16, 32, 48 and 256 togetherMeasured on This Page
| Structure correct | The header reads 00 00 01 00 (the ICO magic) and the directory declares 4 frames: 16/32/48/256 |
|---|---|
| Every frame decodes | All four payloads are PNG (149–2400 bytes each) and PIL reports the size the directory declares |
| 256 encoded as 0 | An ICO directory byte cannot hold 256, so the spec uses 0 — handled correctly here |
| Content not empty | The decoded 256 frame has non-zero alpha, proving the source image was actually drawn rather than a blank canvas |
| Non-square gets stretched | drawImage fills the target box, so a non-square source is distorted (favicons are conventionally square; noted) |
ICO means writing binary by hand, and the three usual failure points all hold here: the field order inside the 16-byte directory entry, 256 having to be stored as 0 because one byte cannot hold it, and the accumulated payload offsets. Verifying the bytes directly proved more reliable than a library's multi-frame API — PIL reported a single frame on first inspection while manual parsing confirmed four entries, each decodable on its own. Usage reminder: non-square sources are stretched to fill, and the 16x16 frame is the one browsers show in a tab, so keep the artwork simple.
How to Use
- Open "Image to ICO"
- Choose or drop an image; multi-size icons are built instantly
- A square source avoids stretching the favicon
- Inspect the preview at 16, 32 and 48 pixels
- Click "Download .ico" to save the favicon
Use Cases
- Website favicon — Convert brand logos to multi-size ICO files as favicon.ico to enhance browser tab recognition.
- Desktop app icons — Generate multi-size ICO icons for Windows desktop applications, adapting to different display scaling levels.
- Shortcut icons — Convert custom images to ICO format for Windows desktop or folder shortcut icons.
- Browser extension icons — Generate 16x16 and 48x48 ICO icon files for Chrome or Firefox extensions.
- Brand asset output — Batch-convert brand images to ICO format for delivery to development teams for Windows applications.
FAQ
What sizes does the ICO file include?
By default it includes 16x16, 32x32, 48x48, 64x64, 128x128, and 256x256. Browsers and the system auto-select the best size for each display scenario.
Why is the generated ICO file large?
Multi-size ICO files embed bitmap data at multiple resolutions. Uncheck large size options to reduce file size if only small icons are needed.
Will large icons look blurry?
No. A multi-size ICO renders each target size independently, and the system uses the most suitable entry for each scenario and DPI, so scaling stays sharp.
Does it support transparent backgrounds?
Yes. PNG transparency is preserved in the ICO file. Use PNG source images for the best transparency results.
Can JPEG images be converted to ICO?
Yes. PNG, JPEG and WebP input formats are supported. JPEG lacks an alpha channel, so the ICO background will be white.
Are images uploaded?
No. All conversion runs locally in your browser via the Canvas API, so brand design assets never leave your device.
The ICO looks blurry in the browser tab?
ICO is a multi-size container and the browser picks the closest size; a single large size gets scaled and blurs. Pack 16/32/48 together so the favicon stays crisp across DPRs — 32×32 is the size tabs actually use.
The site favicon did not update after replacement?
Mostly caching. Browsers cache favicons stubbornly: rename the file (favicon2.ico), add a version query to the link tag, or verify in a private window — all more reliable than refreshing. Also confirm the link rel="icon" points to the new file.