XCF to ICO

How to Convert XCF to ICO Online

1. Upload Your XCF File: Drag and drop or click "Add Files" to load GIMP project files. Flatten layered projects in GIMP first (Image → Flatten Image, then re-save the .xcf) — a multi-layer XCF is read as a multi-page image and a single layer reaches the ICO encoder, not the merged canvas. Batch is supported, so you can drop in several .xcf projects and pull an icon from each.
2. Pick the Icon Size: ICO output uses the icon-sized resolution presets — 256p, 192p, 180p, 128p, 64p, 48p, 32p, 24p, or 16p (the standard Windows icon ladder). 32×32 is the long-standing taskbar default; 256×256 is the maximum a Windows ICO container will render in Explorer's "Extra large" view, introduced with Windows Vista.
3. Check the Shape Before Converting (Optional): The resolution preset is the whole option set on an ICO target — no quality preset, no bit-depth control, no colour palette, and no percentage, "Keep original" or Width × Height box. That preset sets the icon's height and the width follows your canvas's aspect ratio, with nothing cropped or padded, so a 16:9 GIMP canvas at 256P comes out 455×256 — wider than the 256 an ICO directory entry can declare. Design on a square canvas, or pick 128P.
4. Convert and Download: Click Convert. The image is re-encoded to ICO on our servers, then downloads to your device — no GIMP install required, no sign-up, no watermark.

Why Convert XCF to ICO?

XCF is GIMP's native project format. It preserves layers, channels, paths, masks, and selection state — everything needed to keep editing a design — but only GIMP can open it. ICO is the opposite end of the spectrum: a tiny Windows icon container that holds one or more square stills (16, 32, 48, 64, 128, 256 px) for the taskbar, desktop, Explorer, tray, and browser favicons. Converting XCF → ICO turns the icon design straight into a Windows-native asset without the JPG/PNG intermediate step — flatten the project in GIMP first and the icon matches your canvas. Common reasons people pull an ICO from a GIMP project:

• Application and installer icons for Windows builds — .exe resources still take ICO with embedded 16, 32, 48, 64, 128, and 256 px sizes. A GIMP design flattened to one layer exports cleanly to a 256 px ICO for the top of that bundle, then downscales for the smaller sizes.
• Browser favicons designed in GIMP — <link rel="icon" href="favicon.ico"> still expects an ICO. A GIMP project sized to 32×32 (or a multi-size layered design) goes straight to ICO without a PNG round-trip.
• Custom desktop and folder icons — Right-click a folder, Properties → Customize → Change Icon expects an .ico file. Use a GIMP-designed icon for that working directory's folder so it stands out at a glance in Explorer.
• Tray and Start Menu shortcut icons — System tray icons (16 / 24 / 32 px) need ICO. A GIMP design with a bold silhouette and high contrast reads cleanly even at 16 px in the notification area.
• Game launcher and emulator shortcut icons — Steam non-Steam shortcuts, RetroArch playlists, and Lutris menus all read ICO. A GIMP-painted box-art mockup or custom logo works as the source.
• Replacing a generic icon on a packed .exe — Tools like Resource Hacker and rcedit accept ICO; a GIMP project gives you a fully editable brand asset to mine for the icon at every size.

If you want to keep the lossless source pixels around for editing later, convert through XCF to PNG first, then build the ICO. For a flat shareable image without the icon constraints, XCF to JPG is the smaller path.

XCF vs ICO — Format Comparison

ICO Resolution Quick Guide

A typical Windows ICO bundle ships at 16, 32, 48, and 256. Favicons usually only need 32×32 (or 16/32/48 combined). Pick the size that matches where you'll actually use the icon.

Frequently Asked Questions

Are GIMP layers preserved in the ICO?

No — and they are not merged for you, which matters on icon work because so many GIMP icon projects are built as a stack of shapes. ICO is a flat raster format with no concept of layers, masks, paths, or selections, and a multi-layer XCF is read as a multi-page image from which a single layer is encoded rather than the composite the canvas shows. Everything on the other layers is missing, and the space they occupied comes through transparent — which on an icon usually reads as "half my logo vanished." Flatten in GIMP before uploading (Image → Flatten Image, then re-save the .xcf) and the icon matches your design; a single-layer XCF is fine as-is. Keep a copy of the layered .xcf if you want to keep editing later.

What happens to transparent areas in my XCF?

Transparency carries through — assuming the design is flattened, since an unflattened stack leaves the missing layers' area transparent too. ICO supports a 1-bit transparency mask and, in PNG-encoded ICOs (the format Windows Vista and later use for 256 px icons), full 8-bit alpha. Transparent and semi-transparent pixels in your GIMP design are preserved so the icon can sit over the desktop wallpaper, taskbar, or a folder thumbnail without a hard rectangular background.

What icon size should I export?

For a browser favicon, 32×32 is the most widely supported single size, with 16×16 and 48×48 as common companion sizes in a multi-image ICO. For a Windows app or installer, ship 16, 32, 48, 64, 128, and 256 so Explorer can pick the right size for every view (list, small, medium, large, extra-large). For a single desktop or folder shortcut, 256×256 is enough — Windows will downscale it for smaller views.

Can I pick the icon's bit depth, colour palette, or quality?

None of those render on an ICO target. The Image Compression group — quality preset and file-size targeting — is hidden, the colour-palette control belongs to GIF output, and the bit-depth control is PPM-only. The icon is written at standard 8-bit-per-channel colour with an 8-bit alpha channel, which is what Windows expects anyway. If you want a monochrome or reduced-palette icon, flatten the palette inside GIMP before exporting the XCF.

Why does my 16×16 icon look blurry?

Detail that fits comfortably in a 1024 px GIMP canvas turns into mush at 16×16. Thin strokes and small text downscale to a smear. For tiny sizes, design the source so the icon shape reads at 16 px — bold silhouette, no fine text, high contrast against the background. If you need a sharp 16×16, design that size separately in GIMP rather than relying on a downscale of the 256 px version.

How do I make a multi-size ICO bundle for a Windows installer?

Generate the highest-resolution ICO first (256p) from the XCF, then run additional conversions at 128p, 64p, 48p, 32p, 24p, and 16p. Bundle the individual ICO files into a single multi-size ICO with a tool that supports it (IcoFX, or magick convert with multiple input PNGs). For a plain favicon a single 32×32 ICO is enough — most modern browsers also accept the source PNG via <link rel="icon" type="image/png">, so converting through XCF to PNG is a viable alternative.

Do I need GIMP installed to convert XCF to ICO?

Not for the encoding — the converter decodes the XCF and writes the ICO entirely on our servers, no GIMP, no Photoshop, no plugins, which is useful when a designer sends you an .xcf and you just want the Windows icon. The one thing you do need GIMP for is compositing: if the file has more than one layer, run Image → Flatten Image and re-save before uploading, because that merge is not done here. Ask the designer for a flattened copy and you can skip the install entirely.

Can I batch-convert several XCF projects into icons at once?

Yes. Drop in multiple .xcf files and each one converts to its own ICO at the same resolution preset — handy for an app suite where every project file becomes the icon for a corresponding .exe or shortcut. Output downloads individually or as a ZIP archive.

Why does my GIMP design look slightly different in the ICO?

GIMP's working canvas shows the whole stack blended live; the ICO is one layer of the file downscaled to a fixed icon size. If the difference is dramatic — parts of the artwork simply absent — the file was not flattened before upload. If it is subtle (slight softening on hard edges, semi-transparent pixels snapping to the alpha mask), that is the downscale doing its job. For a pixel-perfect match at 16×16 or 32×32, design at the target size in GIMP rather than downscaling from a 1024 px canvas.