Convert WebP to a proper Windows icon
Upload a WebP and get back one ICO file that contains 16x16, 32x32, 48x48, and 256x256 versions of the same icon. Windows then picks the sharpest size for each place it shows the icon, instead of stretching one small image.
That one file works for desktop shortcuts, folder icons, app icons, and as a favicon.ico for a website. Your transparency is kept, your file is processed in your browser with no upload, and you download each ICO individually, with no ZIP step.
Tick the sizes you need, check the preview at 16 pixels first — that is where a bad icon fails — and then download the finished icon.
What an ICO file actually is
The directory, not just a picture
An ICO file is not a picture in the same sense as a WebP or PNG. It is a container that bundles several pictures, at several sizes, into a single file, together with a directory that tells Windows where each picture starts and how big it is.
The file begins with an ICONDIR header: two reserved bytes, a type field set to 1 for icons, and a count of how many images follow. After that header comes one ICONDIRENTRY per image, sixteen bytes each, recording the width, height, colour count, planes, bit depth, byte size, and byte offset of that image.
Only after the directory does the actual image data begin. That structure is the whole reason ICO still matters in 2026, long after newer image formats arrived.
No single-size format can tell Windows, in one file, to use this picture at 16 pixels and that picture at 256 pixels.
- ICONDIR — header, reserved bytes, type 1, image count
- ICONDIRENTRY — 16 bytes per image, with size, bit depth, byte size, and offset
- Image data — follows only after the directory
PNG entries, not BMP
Each embedded image inside a modern ICO is usually a complete PNG file, compressed exactly as a standalone PNG would be, including its alpha channel. That is the format this tool writes, and it is why transparency survives the conversion cleanly.
Older ICO files instead embedded a BMP-style DIB image, with a separate AND mask for transparency, which was fiddly and easy to get wrong. PNG-compressed entries have been supported since Windows Vista, so for Windows 10 and 11 they are the normal, correct choice, and they are what most current converters produce.
The one honest caveat is legacy: a PNG-compressed ICO will not work on Windows XP-era software that only understands BMP entries. If you are targeting truly ancient systems, that is a different tool, but for current Windows, shortcuts, folders, and app packaging, PNG entries are right.
The 256 trap
One detail in the directory is easy to miss, and it causes real bugs in hand-rolled encoders: a width or height of 256 is stored as zero, because a single byte cannot hold 256. So an entry for a 256-pixel icon records 0 for width and 0 for height, and Windows interprets that as 256.
This tool handles that explicitly, rather than writing 256 into a byte and silently corrupting the file. The same care applies to offsets.
Each entry's offset must point exactly to the start of its PNG data, after the header and after every preceding entry. Otherwise, Windows will read the wrong bytes and show a broken or blank icon.
Why Windows needs 16x16 and 256x256 in the same file
Windows does not display an icon at one size. The same icon file is asked, in different places, to be tiny, medium, and huge, sometimes on the same screen.
At 16 pixels it appears in window title bars, in small Explorer list views, in the taskbar, and in notification areas, where every pixel counts and a detailed design collapses into mush. At 32 pixels it appears as a standard desktop icon, a folder icon, and a classic favicon size.
At 48 pixels it appears in larger Explorer views and in places that need a little more presence without going full size. At 256 pixels it appears in extra-large Explorer views, in large Start tiles, and, crucially, on high-DPI displays and at display scaling settings of 150% and 200%, where the system needs a large master to downscale cleanly rather than upscaling a small one and blurring it.
- 16x16 — title bars, small Explorer views, taskbar, notification area
- 32x32 — standard desktop icons, folder icons, classic favicon
- 48x48 — larger Explorer views
- 256x256 — extra-large views, large Start tiles, high-DPI displays, 150% and 200% scaling
Display scaling is where a single-size ICO fails most visibly. If your ICO contains only a 32-pixel image and Windows needs to show it at an effective 64 pixels on a high-DPI screen, it has no choice but to upscale, and upscaling cannot invent detail.
Edges soften, text smears, and a crisp logo looks like a thumbnail that was stretched in a slide. If the ICO also contains a 256-pixel master, Windows can downscale from that master instead, which preserves edges far better than upscaling ever can.
That is also why the 256-pixel size matters even if you never consciously use extra-large icons. It is the insurance policy that makes every smaller display size sharper, because the system can pick the nearest larger size and scale down, rather than the nearest smaller size and scale up.
It is worth being precise about what packing four sizes does and does not guarantee. Windows also uses intermediate sizes, such as 20, 24, 40, and 64 pixels, in different parts of Windows 10 and 11, depending on scaling and view.
A four-size ICO does not contain every possible size, and Windows will still scale from the nearest embedded size for those in-between requests. The win is not perfection at every size, it is a dramatic reduction in scaling distance.
Instead of stretching a single 32-pixel image to 256 pixels, or shrinking a single 256-pixel image to 16 pixels with no chance to check legibility, you give the system a close match at each major breakpoint. That is why the classic set of 16, 32, 48, and 256 has survived so long: it covers the breakpoints that matter most, without bloating the file with a size for every conceivable request.
Favicon vs Windows desktop icon: do not confuse them
A favicon and a Windows desktop icon look similar, but they live in different worlds and they fail in different ways. A favicon lives in a browser tab, in bookmarks, and in browser history.
It is served from your website, it is usually 16 or 32 pixels, and modern browsers will happily accept a PNG favicon, an SVG favicon, or a classic favicon.ico. If your only job is a website tab icon, you do not need a 256-pixel Windows master, and you do not need to worry about Explorer views or display scaling in the same way.
You need a clean, high-contrast mark that still reads at 16 pixels, and you need it served correctly from your site.
A Windows desktop icon lives in Explorer, on shortcuts, on folders, and inside application packages. It is not served from a website, it is read by the Windows shell, and it is the format that actually requires the ICO container.
A PNG file renamed to .ico will not work as a shortcut icon, because the shell expects the ICONDIR directory and the embedded sizes, not a single PNG stream. A WebP file will not work either, for the same reason.
That is why this tool defaults to the Windows preset — all four sizes — rather than a favicon-only preset. Most people searching for webp to ico are not just decorating a browser tab, they are trying to make something Windows will accept, and a favicon-only file will look blurry or fail in exactly the desktop contexts they care about.
Use the Favicon preset only when you know the file will never leave the browser.
The mock preview in the tool exists to make that distinction tangible. The browser tab mock shows you the favicon job: 16 pixels, next to a page title, on a tab bar.
The taskbar and desktop mocks show you the Windows job: 32 pixels pinned, 16 pixels in the tray, 48 pixels on the desktop, and 256 pixels in a large Explorer view. If your icon reads in the tab mock but turns to mush in the desktop mock, you have a Windows problem, not a favicon problem, and you need to simplify the artwork, not just re-export it.
That is a check no thumbnail grid can give you, because a grid shows sizes in isolation, while the mocks show sizes in the places where they will actually be judged.
- Favicon — browser tab, 16/32, served from your website, PNG / SVG / ICO all accepted
- Windows icon — Explorer, shortcut, folder, and app, ICO container required, 16 to 256, high-DPI scaling
WebP for the web, ICO for Windows
WebP and ICO solve different problems, which is why converting between them is not just a rename. WebP is a modern web format from Google, designed to make images smaller and faster to load in browsers.
It supports both lossy and lossless compression, it supports transparency, and it even supports animation, all in a single-size file that is excellent for web pages, product photos, and blog media. What it is not, is a Windows icon format.
Windows Explorer, the taskbar, shortcut dialogs, and application packaging do not treat a .webp file as an icon. Simply renaming a WebP file to end in .ico does not change its bytes or its directory structure, so Windows will reject it or show a blank icon.
ICO, by contrast, is a poor web format and an excellent Windows format. It is larger than WebP for the same picture, because it bundles several sizes, and it is not designed for photographs or for fast web loading.
Its value is entirely in its container structure and in Windows native support: you can point a shortcut at it, set it as a folder icon, embed it in a Windows application, or save it as favicon.ico and have browsers pick it up. The conversion therefore has a clear direction of travel.
You start from a WebP because that is what you have — perhaps exported from a design tool, downloaded from the web, or saved from a modern workflow — and you convert to ICO because that is what Windows asks for. Going the other way, from ICO back to WebP, is a different job, for extracting a single size from an icon for web use.
Transparency, and why padding beats stretching
Transparency is the feature that most often breaks in a careless WebP to ICO conversion, and it breaks in two distinct ways. The first is flattening: a converter that draws the WebP onto a white canvas before encoding throws away the alpha channel, so a logo that should float over any background instead arrives with a white box around it.
That is fatal for taskbar and desktop icons, which sit on wallpapers, themes, and dark modes where a white box looks amateur. The second is a black fringe or halo, which happens when semi-transparent edge pixels are composited badly during resizing.
This tool avoids the first failure entirely by keeping the canvas transparent throughout. It minimises the second by resizing with high-quality smoothing from a transparent square canvas, rather than flattening and then re-adding transparency as an afterthought.
Non-square sources need a separate decision, and the right one is padding, not stretching. If your WebP is a wide banner or a tall portrait, stretching it to a square will distort it: circles become ovals, text leans, and a logo looks wrong at every size.
Padding instead centres the original inside a transparent square, preserving its aspect ratio exactly, and then resizes that square to each icon size. The trade-off is transparent margins on the long side, which is honest and usually invisible once the icon sits on a desktop or in a taskbar.
If you can, start from a square source — a square logo, a square app icon, a square export from your design tool — and you avoid the margins altogether. If you cannot, padding is still far better than distortion, and the preview in the tool lets you see the padded result before you download.
Source size matters as much as format. The best ICO comes from a source at least 256 pixels on its longest side, ideally larger, because downscaling from a detailed master preserves edges better than upscaling from a small one.
If your source is only 64 pixels and you tick 256, the tool will still produce a 256-pixel entry, but it will be an upscale, and it will look soft — the tool warns you in that case rather than pretending otherwise. At the other end, a photographic source with fine detail will always struggle at 16 pixels, no matter how good the converter is, because 16 pixels simply cannot hold that detail.
For tiny sizes, simplify: bold shapes, high contrast, no small text. Check the 16-pixel preview in the tool, not just the large preview, because that is the size where a good icon and a mushy icon diverge.
How to use your new ICO in Windows
For a desktop shortcut, right-click the shortcut, choose Properties, then Change Icon, then Browse to your .ico file and select it. Windows will show the embedded sizes and pick the right one for the shortcut view.
For a folder, right-click the folder, choose Properties, then the Customize tab, then Change Icon, and browse to the same file. The change applies to that folder's icon in Explorer, and it survives moving the folder on the same machine, because the icon path is stored with the folder.
For a website, save the file as favicon.ico in your site root, or link to it explicitly, and browsers will pick it up as the tab and bookmark icon.
- Shortcut: right-click, Properties, Change Icon, Browse to your .ico file
- Folder: right-click, Properties, Customize, Change Icon, Browse to your .ico file
- Website: save as favicon.ico in your site root, or link to it explicitly
- App packaging: point your build at the single .ico file — the sizes are already inside
For developers packaging a Windows application, the ICO is the icon resource you embed in your executable or installer, whether you are using a traditional desktop framework, Electron, Tauri, or a similar tool. In those workflows you typically point the build configuration at a single .ico file and let the packager embed it.
You do not need to ship separate PNG files for each size, because the sizes are already inside the ICO. That is the practical payoff of multi-size packing: one file to manage, one file to version, one file to ship, with Windows doing the size selection at runtime.
If you later need a web version of the same icon, extract a PNG size from the ICO or convert from your original source, rather than screenshotting the icon from Explorer.
One final practical note: do not use ICO for macOS app icons or for Android launcher icons. macOS uses .icns, Android uses adaptive PNG and vector assets, and neither will accept an ICO as a native app icon.
ICO is a Windows and legacy favicon format, and using it outside that context is a common source of wasted effort. Within its context, though, it remains the correct, native, expected format, and a well-packed multi-size ICO will look sharp in places where a single PNG or a renamed WebP simply will not work at all.
How this tool compares
Most current WebP to ICO tools get the basic conversion right but force a compromise somewhere else. Some offer only a single size per download, so you have to convert four times to build a proper multi-size icon.
Some flatten transparency to white, which ruins logos on dark backgrounds. Almost all batch tools push multiple files into a ZIP archive, which adds an unzip step before you can even test the icon in Windows.
A few cap file size at 10 MB, which is awkward for high-resolution brand assets. This tool removes those compromises together: tick the sizes once, keep transparency, preview each size in a mock tab, taskbar, and desktop, and download each ICO individually, with no ZIP, no upload, and no account.
- Rivals: single size only, transparency flattened to white, batch pushed into a ZIP, file caps around 10 MB
- This tool: all four sizes in one ICO, transparency kept, mock preview, individual downloads, no ZIP
Related icon converters
Going the other way? Try our ICO to WebP converter.
Starting from a different source? Try PNG to ICO for PNG sources, JPEG to ICO for JPEG sources, or SVG to ICO for vector sources that need rasterising at each icon size.