Initializing... drag & drop files here
Supports: ICO
.ico file or click "Add Files". A single ICO can hold several images at different sizes (16×16, 32×32, 48×48, 256×256) — the converter reads the embedded frames so you can pull out the resolution you need. Batch is supported; drop in multiple icons at once.ICO is Microsoft's Windows Icon format, introduced with Windows 1.0 in 1985 and used ever since for application icons, desktop shortcuts, and website favicons. Its defining trait is that one .ico file can bundle several images at different sizes and color depths — typically 16×16, 32×32, 48×48, and 256×256 — and Windows (or a browser) automatically picks the right one for the context. Since Windows XP it carries an 8-bit alpha channel for smooth transparency, and since Windows Vista it can store its larger frames as embedded PNG data to keep file size down.
That multi-size container is great inside Windows and for a favicon.ico, but it's the wrong file almost everywhere else. Most image editors, web <img> tags, design tools, and operating systems outside Windows expect a single-image format. People convert ICO to extract the artwork into something usable:
| Property | Value |
|---|---|
| Full name | Windows Icon (ICO) |
| Origin | Microsoft, introduced with Windows 1.0 (1985) |
| Type | Raster container — holds one or more bitmap (or PNG-compressed) images |
| Max recommended size | 256×256 px (larger is technically possible but not recommended by Microsoft) |
| Color depth | 1, 4, 8, 24, and 32-bit (32-bit adds an 8-bit alpha channel, since Windows XP) |
| Transparency | Yes — 1-bit mask, plus full alpha channel on 32-bit images |
| PNG embedding | Supported for frames since Windows Vista (keeps large icons small) |
| Native browser support | All browsers read .ico for favicons; not displayable via a normal <img> everywhere |
| Closest relative | CUR (cursor) — an almost identical format that adds a hotspot coordinate |
| Best for | App icons, desktop shortcuts, favicon.ico |
On Windows, ICO files are handled natively by the OS for icons and favicons. To view or edit the artwork, image editors like GIMP, Photoshop (with a plugin), Paint.NET, and IrfanView open them directly. On macOS and Linux, native viewers usually won't display ICO, which is the most common reason people convert it to PNG first. Browsers read ICO only in the favicon role (the <link rel="icon"> slot), not as a general <img src> image in every browser.
Yes. PNG supports a full alpha channel, and a 32-bit ICO already carries one, so the transparent background survives the conversion intact. This is exactly why PNG is the default target for icon work. If you instead convert to a format with no alpha channel — JPG or BMP — the transparent pixels get filled with a solid background color, which you can choose in the options before converting.
An ICO can bundle multiple frames (commonly 16×16 up to 256×256). The converter reads the embedded images and produces the resolution you select under Image resolution — by default it extracts the largest available frame so you keep the most detail. If you need a specific smaller size, set a custom Width × Height or use Resolution Percentage to scale down from the full-size frame.
Not in the way people usually hope. ICO is a raster (pixel) format, so ICO to SVG wraps the existing bitmap inside an SVG container — it does not trace the pixels into editable vector paths. The result scales as a contained image but won't get sharper when enlarged the way a hand-drawn vector logo would. For a genuinely scalable icon you need the original vector artwork; auto-tracing a low-res 16×16 icon rarely produces a clean result.
You generally still want a favicon.ico as the baseline. Modern best practice is to ship an SVG favicon as the primary (crisp at any zoom) plus a small favicon.ico containing 16×16, 32×32, and 48×48 layers as the universal fallback, along with PNG Apple-touch and Android icons. SVG favicons are supported in Chrome and Edge 80+, Firefox 41+, and Safari 26+, but older Safari versions ignore them — so the ICO and PNG fallbacks still matter for full coverage.
ICO files are tiny — usually a few KB to a couple hundred KB — so there's no practical size concern; the real limit on any upload is your connection speed, not a fixed cap, and batch jobs have no quantity limit. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours. There's no sign-up, no watermark, and your files are never shared or made public. In our testing, a standard multi-size favicon.ico (16/32/48/256 px) converts to a transparent 256×256 PNG in under a second.