Initializing... drag & drop files here
Supports: ICO
\System32 extract or icon library.ICO is Microsoft's container format for application and shortcut icons — a single .ico file holds several bitmap layers at different sizes and color depths so Windows can pick the right one for the taskbar, desktop, file explorer, or Alt-Tab UI. BMP is the underlying flat-bitmap format Windows has shipped since 1990. Converting ICO → BMP unpacks one of those embedded layers into an editable, single-image bitmap.
.exe / .dll extracts — Tools like Resource Hacker dump icons as ICO. Converting to BMP gives you a flat raster you can diff, archive, or feed into asset-tracking workflows.| Property | ICO | BMP |
|---|---|---|
| Origin | Microsoft icon container (Windows 1.0, 1985) | Microsoft DIB / device-independent bitmap (Windows 3.0, 1990) |
| Layers per file | Multiple (typical: 16, 32, 48, 64, 128, 256 px) | One bitmap, single resolution |
| Compression | Per-layer: uncompressed BMP or PNG-compressed | Uncompressed RGB by default; optional RLE / Deflate |
| Color depth | 1, 4, 8, 24, 32-bit (per layer) | 1, 4, 8, 16, 24, 32-bit |
| Transparency | Yes (1-bit AND mask, or 32-bit alpha for PNG layers) | Yes (32-bit BITMAPV4HEADER+); rarely used in practice |
| Typical file size | 5-200 KB depending on layer count | Large — a 256×256×24-bit BMP is ~196 KB uncompressed |
| Best for | Application / shortcut / favicon icons | Editing, embedded firmware, lossless interchange |
| OS support | Windows native; partial macOS / Linux | Universal |
| Layer size | Original use | When to pick it |
|---|---|---|
| 16×16 | File explorer small icon, taskbar overflow | Tiny UI sprites, retro pixel art |
| 32×32 | Desktop, classic Alt-Tab | Most common edit target — sharpest pixel art |
| 48×48 | Vista+ medium icon | Medium-detail edits, control-panel icons |
| 64×64 | High-DPI taskbar | Modern Windows shell scaling |
| 128×128 | Tile / large icon | Print stickers, packaging mockups |
| 256×256 | Windows Vista+ extra-large, jumbo view | Highest-resolution edit; usually PNG-compressed inside the ICO |
The converter picks the layer closest to your chosen output resolution. If you leave resolution at default, the largest layer (often 256×256) is unpacked so no detail is thrown away. Set a specific width × height (for example, 32×32) to grab that exact layer. To unpack every layer separately, run the conversion once per target size or split the ICO first with ICO to PNG and convert the PNGs to BMP.
Partially. ICO uses either a 1-bit AND mask (hard edges) or a 32-bit alpha channel (soft edges, Vista+). BMP can carry 32-bit RGBA via the BITMAPV4HEADER, but many older Windows tools — including classic Paint pre-Windows 7 — render the alpha channel as solid black or white. If your target reader is one of those legacy tools, flatten transparency to a chosen background color before converting.
ICO files compress their large layers (typically the 256×256 frame) as PNG inside the container. BMP defaults to uncompressed raw pixels: a 256×256 24-bit BMP is roughly 196 KB regardless of content. Use Deflate compression to shrink the BMP, or drop bit depth to 8-bit (256-color) for icons that only use a small palette — that alone cuts size by two-thirds.
8-bit (256-color indexed) is best for classic pixel-art icons, monochrome glyphs, and palette-locked artwork — smallest file, exact color match. 24-bit RGB is the safe default for any modern icon with gradients or photographic content. 32-bit RGBA preserves the alpha channel but only matters if the consumer actually reads alpha (modern editors yes, embedded firmware usually no).
favicon.ico) to BMP?Yes — favicons are standard ICO files, just typically 16×16 and 32×32 layers. Drop the favicon.ico in and the converter unpacks one of the embedded frames as a BMP. Note that some modern favicons are PNG-encoded inside the ICO container; that's handled transparently. For the reverse direction (e.g., turning artwork back into a favicon), see BMP to ICO.
.exe and .dll files?Yes — icons dumped from executables by Resource Hacker, IconViewer, or similar tools are normal ICO files and convert the same way. If the dumped file is a .icl (icon library) instead of .ico, extract the individual icons first; .icl is a different container format.
PNG is usually better — smaller, lossless, alpha-aware, and universally supported. Pick BMP when your target tool specifically demands it: legacy Windows imaging code, embedded display libraries that ship a BMP-only parser, certain CNC / laser engraver workflows, or forensic / archival pipelines that mandate raw-pixel uncompressed storage. For everything else, ICO to PNG is the better choice.
Yes — drop in entire icon archives, .exe extract folders, or theme bundles. Each file converts in parallel within your browser session and downloads individually or as a single ZIP. Settings (bit depth, DPI, target resolution) apply uniformly across the batch.