drag & drop, click, or paste from clipboard
Drop to add
drag & drop, click, or paste from clipboard
Older Windows development workflows, legacy icon toolchains, and resource editors often produce or store assets as BMP files. Converting those BMPs to proper multi-size ICO files — the format that browsers, Windows Explorer, and modern OS environments actually use — is what this tool handles. Enhydra RPO takes your BMP source, generates all six standard icon sizes, and bundles them into a single ICO container.
The output ICO embeds sizes at 16, 32, 48, 64, 128, and 256 px. If your BMP source was created without an alpha channel (standard BMP has no transparency), the icon background will be the fill color from the BMP — typically white or whatever the original resource background was. For transparent icons, a PNG source works better; but for legacy BMP resources where the background color is part of the design, the direct BMP-to-ICO path is the right one.
Windows icon resources have existed since Windows 1.0. For decades, tools like Resource Hacker, PE Explorer, and older Visual Studio resource editors stored icon graphics as individual BMP files before assembling them into ICO containers or embedding them in EXE/DLL resources. Some workflows still do:
If you are migrating an old Windows application to modern packaging, converting its BMP icon resources to ICO is a standard step.
BMP files do not use compression, so there is no lossy quality degradation to worry about when using BMP as a source. The pixel data is exactly what was stored. What does affect output quality is the resolution of the BMP:
If the source BMP is 256×256 px or larger, all six embedded ICO sizes will be generated by scaling down — the preferred direction. If the source BMP is smaller (say, a legacy 48×48 icon resource), the 64, 128, and 256 px embedded sizes must be upscaled from that base, and upscaling produces softer results. Where possible, source the highest-resolution BMP available from your resource set.
For square sources the conversion is direct. Non-square BMPs are fit into a square canvas; if the original icon asset was designed to specific non-square proportions, be aware that the ICO output will letterbox it.
Standard 24-bit BMP has no alpha channel, so there is nothing to preserve. The icon background will be the background color from the BMP. If you need a transparent favicon, convert your source to PNG with a transparent background first, then use the PNG-to-ICO tool.
Yes. Upload up to 200 BMP files and each produces its own multi-size ICO, all packaged in a single ZIP download.
It will be upscaled, which produces a soft result. If a higher-resolution version of the BMP exists in your resource set, use that instead. For new projects, start with a 256×256 or larger square source.
An ICO file is a container that bundles multiple resolutions with metadata that tells the OS which size to use in each context. A standalone BMP is a single image with no such container. Browsers and Windows need the ICO container for favicons and shell icons.