BMP Format in 2026: The Three Use Cases That Aren't Anachronistic

Why BMP Still Exists

BMP (Bitmap) was Microsoft's image format from Windows 1.0 (1985). It stored uncompressed pixel data with simple headers. For 30 years it was the default Windows image format. Then PNG arrived in 1996, JPG conquered photography, WebP came in 2010, and BMP was relegated to "legacy compatibility" in most workflows.

Yet BMP is still everywhere. Open Windows Notepad, paste a screenshot from clipboard, save it: you get a .bmp file by default in some configurations. Industrial control software exports diagnostic images as BMP. Some embedded systems read only BMP. Some old WordPress plugins expect BMP.

This post covers the three use cases where BMP is the right choice, the four where it's not, and the conversion workflows for both directions. For broader image format choice, see JPEG XL vs AVIF.

What BMP Actually Is

A BMP file structure:

• File header (14 bytes): magic bytes BM, file size, data offset
• DIB header (40-124 bytes): width, height, color depth, compression
• Color palette (optional, for paletted bitmaps)
• Pixel data (uncompressed, in BGR order, padded to 4-byte rows)

The pixel data is uncompressed by default. A 1920×1080 24-bit BMP is roughly 6 MB. A 4K BMP is 24 MB. Compare to PNG (compressed lossless) at 4-8 MB or JPG (lossy compressed) at 0.5-2 MB for the same source.

24-bit BMP is what most modern BMP encounters use.

Where BMP Is Right

Three legitimate use cases for BMP in 2026:

Use Case 1: Industrial / Embedded Systems

Some industrial control panels, medical imaging hardware, and embedded systems read only BMP. The hardware was designed before PNG was widespread, and the firmware can't be updated. If your test image is for an embedded system: BMP is the format.

Examples in production:

• CCTV recorder DVRs from 2008-2012
• Industrial barcode scanners from older generations
• Medical thermal imaging hardware
• Some kiosks and signage hardware

Use Case 2: Specific Software Compatibility

A handful of specialty applications still default to BMP:

• Some CAD software (older AutoCAD plugins)
• Vintage photo editing software
• Specific GIS analysis tools
• Test pattern generators

For these, BMP is the lingua franca. PNG might work but BMP is guaranteed.

Use Case 3: Lossless Pipeline With Specific Pixel Order

BMP's row-by-row, no-filtering, BGR-ordered storage is convenient for direct memory mapping. C/C++ code can dump pixel arrays directly to BMP without library overhead. For raw image-processing algorithms that need to inspect pixels:

// Pseudocode
write_bmp_header(file, width, height);
for (int y = 0; y < height; y++) {
    for (int x = 0; x < width; x++) {
        write(file, pixel_array[y][x].b);
        write(file, pixel_array[y][x].g);
        write(file, pixel_array[y][x].r);
    }
}

This isn't elegant, but for low-level image processing in C/C++, it's straightforward.

Where BMP Is Wrong

Four cases where BMP is the wrong choice:

Wrong: Web Display

BMP files don't compress. A 4K wallpaper as BMP is 24 MB; same image as JPG quality 90 is 1.5 MB. Web hosts charge for bandwidth; BMP is uneconomical.

Modern browsers display BMP, but the file size penalty is severe. WebP, AVIF, or JPG are appropriate for web.

Wrong: General Photo Storage

Photographs lose nothing meaningful when saved as JPG quality 90+. BMP at 24-bit captures the same information but at 5-10x the file size. For photo libraries, JPG (or HEIC for Apple ecosystem) is correct.

Even for archival, FLAC-equivalent lossless image formats (PNG or TIFF with LZW compression) save 30-50% over BMP at zero quality cost.

Wrong: Print

Print services accept JPG, TIFF, or PDF. BMP isn't in the standard print format list. Even when a print service accepts BMP, conversion happens before printing; you might as well send the appropriate format.

For print-specific format choice, see CMYK vs RGB Printing.

Wrong: Email Attachment

Most email systems display BMP attachments as files (not inline previews). Emailing a screenshot as BMP forces the recipient to download and open. PNG or JPG inline-previews automatically.

Conversion BMP to Modern Format

For most cases, convert BMP to PNG (lossless) or JPG (compressed):

# Using ImageMagick - to PNG
mogrify -format png *.bmp

# Using ImageMagick - to JPG
mogrify -format jpg -quality 92 *.bmp

For batch conversion of mixed bit depths and old formats, see Batch Processing Files Guide.

Our image converter handles BMP-to-anything conversion in a browser without command-line tools.

Conversion to BMP

For workflows requiring BMP output:

# From PNG
mogrify -format bmp *.png

# From JPG
mogrify -format bmp *.jpg

ImageMagick produces standard 24-bit BMPs by default. For 32-bit BMP (with alpha):

convert input.png -define bmp:format=bmp4 output.bmp

For paletted BMP (older systems requiring it):

convert input.png -colors 256 output.bmp

File Size Reality

For a 1920×1080 image:

BMP is significantly larger than every modern alternative. The size penalty is the main reason BMP fell out of favor.

For underlying compression considerations, see JPEG XL vs AVIF.

RLE Compression in BMP

BMP supports run-length encoding (RLE) for 4-bit and 8-bit color depths. RLE is rarely used in modern BMPs. For 24-bit BMPs (most common), no compression is available within the BMP format itself.

If file size matters, BMP isn't the right format. Convert to PNG or modern alternatives.

Common Issues

BMP looks pink in some viewers: BGR vs RGB byte order. The image was saved with wrong byte order. Re-save with explicit format flag.

Antivirus flags BMP files: BMPs can carry executable code in unused header fields (the "BMP exploit" was a vulnerability). Modern Windows handles this safely; antivirus is being cautious.

File can't be edited in Photoshop: rare but happens with non-standard BMP variants. Convert to PNG first via our image converter.

Mac Preview won't open BMP: rare. macOS Preview handles standard BMP. If failing, the file is corrupted or non-standard.

Web upload rejects BMP: many CMS systems strip BMP because of the file-size and security concerns. Convert to PNG or JPG before upload.

Frequently Asked Questions

Why does Windows still default to BMP for screenshots?

It doesn't, anymore. Modern Windows (Win 10+) saves screenshots as PNG via PrtScn. Some legacy applications still use BMP for clipboard format, which can be saved as BMP if user explicitly chooses.

Can BMP support transparency?

Yes via 32-bit BMP (BMP version 4 or 5). Transparency support is inconsistent across viewers. PNG is more reliable for transparent images.

Is BMP lossless?

Yes. BMP stores raw pixel values without compression (in standard variants). Quality is preserved bit-for-bit through editing.

Should I convert my BMP archive to PNG?

If the BMPs are taking significant storage and you have access: yes, PNG saves 50-80% storage with no quality loss. If you have BMPs that work and don't need to convert: leave them.

Why is BMP still in some workflows?

Inertia. Once a workflow specifies BMP, it's expensive to change. Specialty hardware/software vendors stay on BMP because their customer base hasn't requested otherwise.

What about BMP variants like CompuServe Compressed Bitmap?

Niche variants (CompuServe, OS/2 BMP, Apple PICT) are rarely encountered in 2026. If you receive a "BMP" that won't open, it might be a non-standard variant. ImageMagick handles most.

Related Reading

• JPEG XL vs AVIF
• WebP to PNG: When to Convert
• CMYK vs RGB Printing

Bottom Line

For BMP in 2026: use it only for embedded systems, specialty industrial applications, or specific software compatibility requirements. For everything else (web, photo storage, print, email, archival), modern formats (PNG, JPG, WebP, AVIF) are smaller, faster, and universally supported. Our image converter handles BMP conversions in both directions.