ICO to PNG Converter - Free Online Icon to PNG Converter

An ICO to PNG converter closes the loop between Windows icon containers and the raster formats designers and web pipelines understand best. ICO files are not a single image: they are archives that bundle one or more bitmaps—often several square resolutions so the operating system or browser can pick the sharpest match for a taskbar, tab, or shortcut. SynthQuery's tool unpacks those frames locally in your browser, preserves transparency when the source data supports it, and hands you standard PNG files you can edit in Figma, drop into a React public folder, or feed into documentation. Because decoding runs entirely on your device, unreleased branding, internal app icons, and client deliverables never traverse a third-party upload API. Many professionals encounter ICO files when they inherit a legacy favicon.ico from an older site, download assets from a Windows application, or receive a shortcut icon from a vendor. Opening ICO directly in creative tools is hit-or-miss; extracting to PNG gives you a predictable, widely supported format with an alpha channel you can inspect on a checkerboard. Multi-resolution ICOs are especially common for favicons: the same file might embed 16×16, 32×32, 48×48, and 256×256 variants. This utility lets you export just the largest frame for marketing slides, or explode every embedded size into separate PNGs when you need to audit or rebuild an icon set without redrawing from scratch. The workflow is intentionally straightforward for both quick one-offs and batch operations. You drag ICO files into the drop zone or activate the file picker with the keyboard, optionally toggle extraction of all embedded sizes, choose a specific resolution when you only need one frame from a multi-entry icon, and convert. Progress and error states are isolated per row so a corrupt download does not block the rest of your queue. Downloads can be single PNGs, per-row ZIPs when multiple sizes emerge from one ICO, or one master archive for an entire batch—mirroring patterns you may already know from our other image converters. The sections below explain usage in depth, highlight transparency and performance characteristics, explore real scenarios, compare approaches, and answer frequent questions about ICO structure and quality.

Transparency preservation is central to the pipeline. Modern ICO files frequently store the high-resolution slot as a PNG bitstream inside the container; in that case SynthQuery copies those bytes directly into your download, avoiding generational loss from unnecessary recompression. Smaller frames often use legacy BMP-derived DIB payloads with optional AND masks; the decoder interprets 32-bit BGRA samples, applies mask semantics where present, and rasterizes to RGBA before a single lossless PNG encode through the Canvas API. Eight-bit and twenty-four-bit DIB icons are supported within the same constraints documented in our shared ICO decoder—compressed BMP-in-ICO variants that fall outside BI_RGB remain unsupported and will surface explicit errors rather than silently corrupting pixels. Multi-resolution handling differentiates this tool from a naive “open and export” workflow. The directory listing embedded in every ICO describes width, height, and byte offsets for each frame; SynthQuery walks that table, validates bounds, and either targets one index or iterates all entries. Batch conversion processes files sequentially to keep peak memory predictable on laptops and tablets, while still giving you ZIP packaging via JSZip when you want one download for many outputs. Input validation rejects non-ICO picks with a toast, and per-row errors describe parser failures—wrong magic bytes, cursor files mislabeled as icons, truncated payloads—so you can fix the source or try another exporter. The interface follows SynthQuery's ToolShell layout: options sit in a compact card on wide screens beside the hero drop zone, and stack vertically on narrow viewports. Interactive controls expose data-testid hooks for Playwright suites. Keyboard focus rings remain visible, labels tie to switches and selects, and preview images use empty alt text because filenames are announced in adjacent text. Core Web Vitals are respected by avoiding automatic conversion on page load—work begins only after you click convert—and by dynamic import of JSZip at download time so the initial JavaScript payload stays smaller than bundling the archive library eagerly.

Structurally, an ICO begins with an ICONDIR header: reserved zero, type value one for icons (as opposed to two for cursors), and a count of images. Each ICONDIRENTRY records nominal width and height—where zero in either byte conventionally means 256—plus color counts, hotspot fields reused as zero for icons, payload size, and file offset. Payloads are either raw PNG streams starting with the PNG signature or DIB bitmaps without the BITMAPFILEHEADER wrapper, storing XOR bitmap data followed by an optional monochrome AND mask for per-pixel transparency in older conventions. PNG-in-ICO became prevalent with Windows Vista-era tooling because DEFLATE compression keeps large icons smaller than uncompressed DIB storage. When SynthQuery detects the PNG signature at the start of a payload, it emits identical bytes as your downloaded PNG, so color profiles and alpha semantics match the embedded source. DIB decoding respects bottom-up row order, combines AND masks with alpha for 32-bit sources, and maps palette entries for eight-bit icons. Unsupported compression modes in DIB payloads produce clear errors; if you encounter them, re-export from a design tool using standard 32-bit or PNG-in-ICO settings. Standalone PNG files use a different container: chunks for IHDR dimensions, IDAT compressed pixels, and optional tEXt or iTXt metadata. After extraction you can manipulate PNGs with any standards-compliant tool. Remember that repeatedly re-encoding PNGs through lossy pipelines (for example, forcing JPEG intermediates) will damage edges; keep ICO→PNG→editor→PNG as your lossless spine until you deliberately target a lossy format for delivery.

Favicon extraction is the most common motivation. You may need a crisp PNG of the 32×32 tab icon to illustrate a design review, or you may want every embedded size to verify that a third-party theme did not ship a blurry 16×16 variant. Rather than screenshotting the browser chrome—which introduces JPEG artifacts and wrong colors—unpack the actual favicon.ico and export the precise frames the author embedded. Icon repurposing spans marketing and engineering. A desktop app might ship a single ICO for shortcuts; marketing wants that same glyph for a blog post or changelog hero image. PNG export produces a file you can place in CMS media libraries, run through the PNG Compressor, or convert to WebP for faster delivery. Design documentation benefits when you archive “what we shipped” as layered or labeled PNGs per size, especially when auditing accessibility contrast at small scales. App asset conversion pipelines sometimes receive ICO from Windows-centric partners while iOS and Android expect PNG or PDF masters. Extracting to PNG lets you hand assets to mobile tooling, adaptive icon templates, or our App Icon Generator without forcing designers to redraw identical shapes. Internal IT and support teams occasionally need to inspect shortcut icons for phishing awareness training—unpacking to PNG makes zooming and annotation in slide decks trivial compared to pixel-peeping inside a compound container. Educational contexts—bootcamps, documentation sites, open-source readme illustrations—also benefit. Students learn that ICO is a container, not a codec, once they see multiple resolutions side by side. When combined with SynthQuery's PNG to ICO or JPG to ICO tools, the round trip demonstrates how favicon authoring practices evolved from single-bitmask images to PNG-in-ICO hybrids. Throughout, keeping processing local means classrooms and corporate labs behind strict firewalls can still complete the exercise.

Begin by gathering the .ico files you need. These might live beside an executable, inside a design handoff ZIP, or at the root of a website as favicon.ico. Check file sizes first: this page accepts up to twenty icons at ten megabytes each, which is generous for normal UI artwork but still protects mobile browsers from accidentally loading enormous archives masquerading as icons. If you are unsure whether a download is truly an ICO, rely on the extension and MIME type; the parser validates the header and will surface a readable error instead of producing garbage bytes. Drag your files onto the dashed upload region or press Enter or Space while the region is focused to open the system file dialog—an accessibility pattern shared across SynthQuery free tools. Each accepted file appears in the queue with a thumbnail when the browser can preview the ICO, plus a count of embedded sizes discovered during parsing. If an icon contains multiple resolutions, decide whether you need every frame or only one. Turn on **Extract all embedded sizes** when you want separate PNG files for each directory entry—ideal for rebuilding a favicon set, comparing how an asset was authored at 16×16 versus 128×128, or handing individual PNGs to a developer who will repack them later. Leave the switch off when you only need a single output per ICO; the tool defaults to the largest embedded square, which is usually the best candidate for slides or social crops. When extraction is off and multiple sizes exist, use the per-row dropdown to pick a specific width-by-height pair. Labels call out the largest entry so you can align with common defaults without mental arithmetic. After options look correct, press **Convert to PNG**. Rows enter a converting state with a numeric progress indicator driven by how many embedded images are processed. Successful runs show a small PNG preview on a checkerboard-friendly background so semi-transparent edges are obvious before you download. Use **Download** on a row for that icon's outputs—if several PNGs were generated, the browser receives a ZIP folder named after the source stem—or use **Download all as ZIP** to gather every successful conversion from the whole queue. **Clear queue** resets state and revokes object URLs to avoid memory leaks during long sessions. **Re-run all** repeats conversion with your latest toggle settings, which matters when you first extracted only the largest size and later decide you need the full multi-resolution breakdown for documentation.