XCF to BMP

How to Convert XCF to BMP Online

1. Upload Your XCF File: Drag and drop or click "+ Add Files" to select GIMP .xcf projects from your computer. 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 is written, not the merged canvas. Batch upload is supported, so you can export many files in one pass.
2. Pick a Quality Preset: Under "Image Compression," the default Quality preset is High. Lower it to Medium or Low to write a smaller paletted/RLE-compressed BMP, or push it to Very High for a full 24-bit uncompressed bitmap. You can also enter a target file size as a percentage of the source, set an exact size in KB or MB, or fine-tune Image Quality directly.
3. Resize the Output (Optional): Under "Image resolution," keep the original dimensions, scale by percentage, or pick a Preset Resolution (1080p, 720p, 480p, etc.). You can also lock aspect ratio while typing a new Width or Height, or enter exact Width x Height in pixels.
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.

Why Convert XCF to BMP?

XCF is GIMP's native project format — released alongside GIMP in December 1997 — and it preserves layers, channels, paths, masks, selections, guides, and metadata so you can keep editing later. BMP (the Microsoft Device Independent Bitmap format, often called DIB) is the opposite: a single flattened raster grid documented by Microsoft's Win32 GDI APIs since the early Windows era. Converting reduces everything XCF tracks to one pixel array that almost any Windows tool can decode without a codec — flatten the project in GIMP before uploading and that array matches your canvas exactly.

• Legacy Windows software and embedded UIs — Old MFC apps, point-of-sale terminals, kiosks, and industrial control panels often only ship a built-in BMP/DIB decoder. Shipping art as 24-bit uncompressed BMP means no PNG/zlib dependency at runtime.
• Microcontroller and FPGA display assets — STM32, ESP32, and similar boards commonly load splash screens and UI sprites from raw BMP because the file layout (header + RGB array) maps cleanly to framebuffer memory.
• Game-engine and tool pipelines — Some level editors, tile-set tools, and texture pipelines (especially older Source/Unreal mod tools) still expect 24-bit BMP input and re-encode internally.
• Windows wallpapers and icon source art — When you need a pixel-exact wallpaper or want to feed a .ico builder, BMP avoids the lossy artifacts you'd get from JPEG and the gamma surprises you can hit with PNG.
• Forensic and archival reference copies — Uncompressed BMP gives you a byte-for-byte stable snapshot of the rasterized artwork, useful for chain-of-custody screenshots or print-shop deliverables that contractually require uncompressed source.
• Sharing flat artwork with non-GIMP users — Photoshop, Affinity Photo, and most stock Windows viewers don't open XCF natively; BMP is one of the safest "open it anywhere on Windows" handoffs alongside PNG.

XCF vs BMP — Format Comparison

BMP Quality Preset Quick Guide

If you also need to control output dimensions, the "Image resolution" panel accepts a percentage scale, common video resolutions as presets, or exact Width x Height in pixels.

Frequently Asked Questions

Will my GIMP layers be preserved in the BMP?

No — and the stack is not merged for you either, which is the part worth knowing before you upload. BMP is a single flat raster grid with no concept of layers, masks, or channels, and a multi-layer XCF arrives as a multi-page image from which one layer is written rather than the composite GIMP shows on canvas. In our testing with a three-layer GIMP project, the output carried only the bottom layer; everywhere the upper two would have painted, the frame was empty. Flatten in GIMP first — Image → Flatten Image, then re-save the .xcf — and the BMP matches your canvas pixel for pixel. A project that is already a single layer converts correctly as-is. If you need editable layers elsewhere, export to a layered format such as TIFF or PSD from GIMP and keep the .xcf master.

Will transparency carry over?

Only if the BMP is written as 32-bit. The BMP format supports alpha through the BITMAPV4HEADER and BITMAPV5HEADER structures Microsoft added with Windows 95, but a lot of older Win32 viewers ignore the alpha channel and render whatever sits in those bytes as opaque. If reliable transparency matters, prefer XCF to PNG — PNG's alpha support is universal across modern viewers.

Why is the BMP so much bigger than the XCF?

Default BMP is uncompressed: file size scales with width x height x (bits per pixel / 8) plus a small header. A 4000 x 3000, 24-bit BMP is roughly 36 MB regardless of how busy or empty the picture is. XCF, especially since GIMP 2.10's zlib-compressed v4 format, can be far smaller for the same image because flat color regions compress well. If size is a concern, choose a Medium or lower Quality preset for an indexed-palette BMP, or convert to XCF to JPG for a lossy-compressed alternative.

Should I pick BMP or PNG for modern use?

PNG, in almost every case. PNG is lossless, smaller (it uses DEFLATE), supports full RGBA, embeds gamma and color-profile data, and is supported everywhere from browsers to embedded boards. BMP is the right answer when you specifically need a Win32 GDI-friendly raster, a microcontroller framebuffer dump, or compatibility with a tool that documents BMP as its only input. Otherwise reach for XCF to PNG.

Do layer effects, masks, and blend modes get applied on conversion?

No — blend modes, layer opacity, and masks are all properties of a stack, and the stack is not composited here; a single layer of the file is written instead. That means anything whose appearance depends on how layers interact has to be resolved in GIMP first. Image → Flatten Image bakes blend modes, opacity, and masks into one layer exactly as the canvas shows them (hidden layers stay hidden), and the re-saved .xcf then converts to a BMP that matches. This is a one-menu-item step, but on a layered project it is not optional.

Can I batch-convert many XCF files at once?

Yes. Drop a whole folder of .xcf files into the upload area; each one is converted with the same Quality and Resolution settings and you get a zip of the BMPs at the end. This is useful when you've been authoring a sprite sheet or wallpaper set across dozens of GIMP files.

What about higher bit depths — can I export 16-bit or 32-bit-per-channel BMP?

Standard BMP encoders, including the one this converter uses, write 8-bit-per-channel pixels (24-bit RGB or 32-bit RGBA). Microsoft's BMP spec does describe 16 and 32 bits per pixel, but those are packed RGB layouts, not 16-bit-per-channel HDR. If you authored your XCF in GIMP 2.10's high-bit-depth mode and need to keep that precision, convert to TIFF instead — TIFF supports 16-bit-per-channel cleanly.

Is the conversion lossy?

The rasterization itself is lossless when you use the High or Very High preset (24-bit uncompressed BMP). What you lose is editability — paths, channels, and any GIMP-specific metadata are dropped, and any layer other than the one written is dropped with them, which is why a layered project needs its flatten step in GIMP before upload. Lower Quality presets that reduce the palette to 256, 16, or fewer colors are lossy in the color-quantization sense, similar to saving an indexed PNG or GIF.

Can I open the resulting BMP on macOS or Linux?

Yes. macOS Preview, Finder thumbnails, GIMP itself, ImageMagick, and almost every Linux image viewer read BMP. The format is "device-independent" by design — that's literally what the DIB acronym stands for — so portability isn't an issue. The historical caveat is very old DIBs that use BITMAPCOREHEADER (OS/2 / Windows 2.0 era), which some modern viewers handle imperfectly; the converter writes BITMAPINFOHEADER, the variant every modern decoder supports.