How to Convert ICO to PNG and Pick the Right Icon Size
Last updated: July 8, 2026
The reliable workflow is to extract a specific icon layer, not simply change the filename extension. For example, when a tutorial writer needs a 128-pixel image from an ICO, selecting a genuine 256×256 layer and resizing down is safer than enlarging the first 16×16 preview.
Steps 1–3: protect and inspect the ICO
Step 1: Keep the original ICO file unchanged
Copy the ICO to a working folder and leave the source untouched. The original may be required by Windows or an application, and it may contain useful layers that are not part of the first PNG export.
Step 2: Open or upload the ICO file
Use a converter or icon editor that can decode ICO data. A useful tool shows the embedded images rather than displaying only one composite preview. Do not rename the extension to PNG; that leaves the original encoding unchanged.
Step 3: Check whether the ICO has multiple sizes
List every available width and height. Also note whether two entries share dimensions but have different color depths. Typical files may include 16×16, 32×32, 48×48, and 256×256, but do not assume those layers exist until the file is inspected.
Step 4: choose the best size for the task
| Task | Layer choice | Reason |
|---|---|---|
| Inspect a tiny favicon or title-bar design | Exact small layer | Preserves pixel-tuned small artwork |
| Edit, annotate, or create a large preview | Largest genuine layer | Provides the most source pixels |
| Place at a known pixel size | Exact size, or next larger layer scaled down | Avoids upward scaling |
| Archive all ICO contents | Export every layer separately | Keeps size-specific differences visible |
| Prepare a Windows app resource | Follow the framework requirements | A single PNG may not replace the ICO set |
Do not choose by apparent size in a zoomed preview. Read the numeric dimensions. If the destination requirement can change, retain a larger PNG derivative as well as the ICO master.
Steps 5–7: export and verify transparency
Step 5: Export the selected layer as PNG
Choose PNG as the output and export only the intended icon layer. If the tool can export all entries, use filenames that include dimensions, such as sample-icon-16x16.png and sample-icon-256x256.png.
Step 6: Confirm transparency
Open the PNG in an editor that reports alpha transparency. Confirm that the area around the icon is transparent rather than painted black, white, or another solid color. Some source layers use a hard mask, so their edge may be binary rather than softly antialiased.
Step 7: Preview on light and dark backgrounds
Place the PNG over white, black, and a mid-tone color. Look for a rectangular fill, pale halo, dark fringe, missing shadow, jagged edge, or insufficient contrast. This catches problems that a checkerboard preview can hide.
Steps 8–10: protect detail and save the result
Step 8: Avoid upscaling tiny icons
If a 16×16 PNG is too small, return to the ICO and select a larger embedded layer. Upscaling with sharp interpolation creates blocky pixels; smooth interpolation creates blur. Neither method creates the detail of a real larger icon.
Step 9: Save the PNG delivery copy
After the layer is selected, create the PNG delivery copy with ConvertiImage. Include the size or purpose in the filename, then test the copy in the actual editor, page, documentation layout, or upload screen.
Step 10: Keep the original ICO for future use
Store the ICO with a small extraction note: selected layer, output dimensions, intended destination, and transparency result. Future exports should start from the ICO or the largest clean source, not from an already enlarged small PNG.
Final delivery checklist
- The original ICO still exists and opens correctly.
- The selected layer and its native dimensions are known.
- The PNG dimensions match the task or are safely larger.
- No small PNG was enlarged as a substitute for a missing layer.
- Transparent areas remain transparent.
- Edges look acceptable over light, dark, and mid-tone backgrounds.
- The icon remains recognizable at its actual display size.
- The final destination accepts PNG; ICO is retained if system use requires it.
Example: extracting an icon for documentation
Suppose a help page will show an app icon at 80×80 pixels. The ICO includes 16×16, 32×32, 48×48, and 256×256 layers. Extract the 256×256 layer, verify its alpha, and resize a copy down to 80×80 if the layout requires an exact asset. Compare the result with the 48×48 artwork because the smaller rendition may simplify an important feature. Keep both the ICO and the 256×256 extraction.
Workflow questions
Try an icon-aware tool that lists embedded dimensions. A single preview does not tell you whether other images are present or which one will be exported.
Do so when archiving, comparing artwork, or supporting several destinations. For one known task, exporting the selected layer plus keeping the ICO may be enough.
You can create a new ICO from PNG assets, but one PNG cannot recreate missing layers, color-depth variants, or pixel-tuned artwork from the original container.
Final summary
Preserve the ICO, inspect its entries, choose the layer by destination, export as PNG, and test alpha edges on contrasting backgrounds. Never use upscaling as a substitute for a larger source. Name the PNG as a delivery copy and keep the multi-size ICO for future extraction and system use.
