ICO Converter

For the most common job, use the dedicated ICO to JPG converter.

How to Convert ICO to Any Format

1. Upload Your ICO File: Drag and drop your .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.
2. Pick an Output Format: Choose the target from the output dropdown — PNG, JPG, WebP, BMP, GIF, TIFF, SVG, PDF, AVIF, HEIC, and more. PNG is the default for icon work because it keeps the alpha transparency. Set the Quality Preset (default "Very High (Recommended)") or switch to Specific file size to cap the output in KB.
3. Resize or Set Transparency (Optional): Under Image resolution, keep original, scale by Resolution Percentage, or enter a custom Width × Height with aspect ratio locked. For formats without an alpha channel (JPG, BMP), pick a background Color to fill what was transparent. TIFF exposes Bit Depth and compression type; GIF exposes the color-palette size.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared.

Popular ICO Conversions

• ICO to PNG — extract the icon artwork as a transparent image for web design and documents
• ICO to JPG — a flat, widely-compatible photo image (transparency is filled with a background color)
• ICO to WebP — smaller transparent images for modern web pages
• ICO to SVG — wrap the icon bitmap in an SVG container for scalable embedding
• ICO to GIF — a simple paletted image with single-color transparency
• ICO to BMP — an uncompressed bitmap for legacy Windows tools
• ICO to PDF — drop the icon onto a single PDF page for printing or sharing

Why Convert an ICO File?

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:

• Editing the icon artwork — Photoshop, GIMP, Figma, and most design tools open PNG far more cleanly than a multi-frame ICO. Converting to PNG hands you one image at the size you choose, with transparency intact, ready to recolor or composite.
• Using an icon on the open web — A favicon ships as ICO, but if you want to display that same logo in a page body, an email, or a docs site, you need PNG or WebP. WebP keeps the alpha channel and lands smaller than PNG, which is why modern sites prefer it for inline icon graphics.
• Pulling a single resolution out of the container — An ICO might hold five sizes; you usually want just the 256×256 (or just the 32×32). Converting extracts the frame you ask for instead of the whole bundle.
• Compatibility with non-Windows tools — macOS Preview, Linux viewers, and many CMS uploaders won't accept ICO. PNG, JPG, or BMP get the image into those workflows.
• Printing or sharing — Converting to PDF puts the icon on a page you can print or attach; JPG flattens it for platforms that reject transparency.

ICO Format at a Glance

Common ICO Sizes and What They're For

Frequently Asked Questions

What opens an ICO file?

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.

Will converting ICO to PNG keep the transparency?

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.

My ICO has several sizes inside it — which one do I get?

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.

Can I convert ICO to a true vector SVG?

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.

Do I still need an ICO favicon, or is PNG/SVG enough now?

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.

What sizes should a favicon.ico contain?

The common recipe is a single favicon.ico bundling 16×16, 32×32, and 48×48 layers; the browser or OS picks whichever fits the context — a tab, a bookmark bar, or a pinned shortcut. Many sites add a 256×256 layer for high-DPI displays. You don't need a separate file per size, since the whole point of ICO is that one file carries them all. Modern best practice pairs the ICO with an SVG favicon as the crisp primary and PNG touch icons for mobile.

Can I make an ICO from a PNG instead (the reverse)?

Yes — use PNG to ICO to turn a square PNG logo into a favicon.ico. Start from the highest-resolution square PNG you have (256×256 or larger) so the converter can generate the smaller 16/32/48 layers cleanly. Upscaling a tiny PNG into a large icon only produces a soft, blocky result, so bigger source art is always better.

Is there a file size limit, and what happens to my icons after conversion?

ICO files are tiny — usually a few KB to a couple hundred KB — so size is never a concern: free uploads are limited to 400 MB per file and 5 jobs at a time, which no ICO will approach. 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.