What Is a BMP File? (And Why One Screenshot Is Somehow 40 MB)

You saved a single image and it came out bigger than a hundred photos combined. That's BMP doing exactly what it was designed to do in 1990. Here's what a .bmp file actually is, why it's so enormous, and the one conversion that fixes it.

The File That Shouldn't Be This Big

You exported an image, or some old program spat one out, and the file ends in `.bmp`. You go to email it, upload it, or drop it in a chat — and you stop. One image. 40 MB. Maybe more.

That can't be right. A photo from your phone is 3 MB. A whole folder of screenshots is smaller than this single file. You double-check the dimensions: it's a plain 1920×1080 image, nothing fancy, no hidden layers. And it's the size of a short video.

This is not a bug, and your file isn't corrupted. BMP is doing precisely what it was built to do thirty-five years ago — store every single pixel, exactly, with almost no compression at all. The format is fine. The use case is the problem. Here's what's actually going on, and how to get a normal-sized image back in about ten seconds.

What a BMP File Actually Is

BMP — short for bitmap — is one of the oldest image formats still in regular circulation. Microsoft introduced it with early Windows, and it became the native image format of the operating system: the thing Paint saved, the thing your desktop wallpaper was stored as, the format Windows itself used for icons and interface art.

The core idea of BMP is brutally simple. An image is a grid of pixels. Each pixel has a color. BMP stores the color value of every single pixel, one after another, in a big list. A 1920×1080 image has just over two million pixels. At 24 bits (three bytes) per pixel for full color, that's roughly 6 MB of raw pixel data before anything else — and BMP often stores even more per pixel, or pads each row out to tidy boundaries, which is how you end up north of 40 MB for higher-resolution or 32-bit images.

There's no clever trick here, and that's the point. BMP makes no attempt to be efficient. It just writes down everything.

Why It's So Ridiculously Large

Every modern image format you actually use is built around compression — the art of storing a picture in far less space than its raw pixels would take. BMP, in its standard form, does essentially none of this.

Compare it to the formats you know:

JPG uses lossy compression: it throws away visual detail your eye can't easily detect, shrinking a photo to a fraction of its raw size.

PNG uses lossless compression: it finds repeated patterns — a block of identical sky-blue pixels, say — and stores them as "this color, times 4,000" instead of writing each one out.

WebP does both, and does them better than either.

BMP does the equivalent of writing out "blue, blue, blue, blue, blue…" four thousand times. A solid white background that PNG would crush into a few kilobytes, BMP stores pixel by identical pixel. That's why a basically empty screenshot can still be tens of megabytes — emptiness costs BMP just as much as detail does.

This was a reasonable trade in 1990. Computers were slow, and *decoding* a compressed image took real CPU effort. BMP's "no compression" meant the OS could throw a pixel onto the screen instantly without any math. Storage was the sacrifice, and back when screens were 640×480, the files were small enough that nobody cared.

Screens are now 4K. The math didn't change. The files just got enormous.

Why You're Even Seeing a BMP in 2026

You generally don't go looking for BMP files — they find you. The usual sources:

Old Windows software. Legacy business apps, industrial tools, medical imaging exports, and point-of-sale systems still dump BMPs because that code was written decades ago and never updated.

Microsoft Paint (the classic one). For years it defaulted to BMP, and plenty of saved-once-and-forgotten images are still floating around.

Scanners and fax/document tools set to "maximum quality," which often meant "no compression."

Screenshots on older Windows setups, or images pasted out of one program and saved by another.

Embedded systems and game modding, where a simple, no-decoding-required format is genuinely convenient.

The file usually opens fine — Windows Photos, Preview on a Mac, and most editors all read BMP without complaint. The trouble starts the moment you try to *move* it: email attachment limits, upload size caps, chat apps, and web forms all choke on a 40 MB image that should have been 500 KB.

The Ten-Second Fix

You almost never need what BMP gives you. Its one advantage — pixel-perfect, zero-compression storage — matters for a handful of technical workflows and absolutely nothing you're doing when you try to email a picture. The fix is to convert it into a format built for this century.

Which one depends on what the image is:

BMP → JPG (for photos and anything photographic)

If your BMP is a photo, a scan, or a screenshot full of imagery, BMP to JPG is the obvious move. A 40 MB BMP routinely comes out as a 1–2 MB JPG that looks identical at normal viewing size. This is the single biggest size win available to you.

BMP → PNG (for screenshots, logos, graphics, anything with sharp edges or transparency)

If the image is a screenshot of text, a logo, a diagram, or interface art — where crisp edges matter and you don't want any lossy fuzz — use BMP to PNG. PNG is lossless like BMP, so the image stays pixel-exact, but its compression collapses all those repeated background pixels. Same picture, often a tenth of the size or less.

BMP → WebP (for web upload and the smallest possible file)

Uploading to a website, CMS, or anywhere modern? BMP to WebP gives you the smallest result of the three while keeping quality high, and every current browser supports it. It's the right call when the destination is the web.

If you've got a stack of them, you can also push the converted files through the image compressor to squeeze out the last bit of bloat. And for archival or print workflows where you genuinely want lossless detail but not the BMP overhead, BMP to TIFF is a more sensible high-quality container.

When You Should Actually Keep BMP

In the spirit of honesty, BMP isn't useless — there are a few narrow cases where it's the right choice:

A program or device specifically demands a BMP. Some legacy software, embedded displays, and certain game-modding pipelines only accept raw bitmaps. If a tool asks for `.bmp`, give it `.bmp`.

You need a format with zero decoding overhead. Rare, but real in some low-level graphics work.

You're doing pixel-exact technical work where even lossless PNG compression introduces a workflow you'd rather avoid.

For literally everything else — emailing, uploading, sharing, storing, attaching — there is no reason to keep a BMP around.

Bottom Line

BMP isn't broken and your file isn't damaged. The format simply comes from an era when "store every pixel, compress nothing" was a feature, not a liability. On a 640×480 screen that produced small files. On a 4K monitor it produces 40 MB monsters that won't fit in an email.

You don't need raw, uncompressed pixels to send someone a picture. Convert the BMP — to JPG for photos, to PNG for screenshots and graphics, to WebP for the web — and watch a 40 MB file turn into a few hundred kilobytes that looks exactly the same.

The image was never the problem. The wrapper just came from 1990.