UtiliKit
Back to blog

BMP to PNG: Why the File Shrinks 90 Percent (and When It Doesn't)

Published: November 9, 2026 - 6 min read

A BMP file is big because it usually isn't compressed at all: every pixel is stored as three raw bytes, one each for red, green and blue. PNG stores exactly the same pixels but packs them with lossless compression, so converting BMP to PNG typically cuts the file by 80 to 95 percent without changing a single pixel. Screenshots and graphics shrink the most. Photos shrink less, but they still shrink a lot.

That's the short answer. Here's why it happens, what the numbers look like on real files, and when PNG isn't the right target.

Why BMP files are so large

The size of a normal 24-bit BMP is almost pure arithmetic. Width times height times 3 bytes, plus a 54-byte header, plus a little padding (each row is rounded up to a multiple of 4 bytes).

So a 1920 × 1080 image is 1,920 × 1,080 × 3 = 6,220,800 bytes of pixel data. Add the header and you get 6,220,854 bytes, about 6.2 MB. It doesn't matter whether the picture is a detailed photo or a completely white rectangle. Same size, every time.

That's the whole problem.

A few BMP files use simple run-length compression, and some 32-bit ones carry an extra alpha byte per pixel, which makes them a third bigger again. But the BMPs people actually run into (old scanner output, Windows Paint saves, exports from industrial or medical software, screenshots from older tools) are nearly always the plain uncompressed kind.

What PNG does differently

PNG is lossless too. The pixels you get back after decoding are identical to the BMP's, bit for bit. The difference is that PNG doesn't just dump them into the file.

Before compressing each row, the encoder applies a filter that turns pixel values into small differences from their neighbours. In a screenshot, where a whole row of a window background is the same grey, those differences are mostly zero. Then DEFLATE (the same family of compression used in ZIP files) squeezes out the repeats. Long runs of identical or predictable values compress extremely well, which is why flat UI, text, diagrams and charts collapse to a fraction of their raw size.

Photos have noise, gradients and fine texture, so there are fewer exact repeats and the compression has less to work with. You still get a big saving, just not a 95% one.

Real numbers from three test files

I converted three images from 24-bit BMP to PNG with a standard PNG encoder at default settings, to see how far the "90 percent" claim actually holds:

ImagePixelsBMPPNGSmaller by
Desktop screenshot1360 × 7683.13 MB230 KB92.7%
Social banner graphic1184 × 5011.78 MB279 KB84.3%
Interior render, photo-like1920 × 10806.22 MB1.33 MB78.6%

So the headline is roughly right for screenshots and a bit optimistic for anything photographic. A noisy camera photo with lots of grain would likely land lower than the render above, because sensor noise is close to random and random data barely compresses. Different encoders will also give slightly different sizes. The pixels stay identical either way.

One thing that surprises people: a bigger PNG isn't a "higher quality" PNG. Since it's lossless, two PNGs of the same image can differ in size only because one encoder tried harder. The picture is the same.

How to convert BMP to PNG in your browser

The quickest way is the BMP to PNG converter. Drop the file in, pick PNG as the output, and download. The conversion runs locally in your browser, so the image isn't uploaded anywhere, which matters if the BMP came out of a scanner and happens to be a signed contract or an ID card.

A few practical notes from using it:

The main Format Converter handles the other directions too, if you need JPG or WebP instead.

When PNG is the wrong target

PNG is the right choice when the image is a screenshot, a diagram, a logo, a scan of text or anything you'll edit again. Lossless means you can open and save it a hundred times without it degrading.

For photos, though, it's often not the best end point. That 1.33 MB render above would be around 200 to 400 KB as a good-quality JPG or WebP, and nobody would see the difference on a web page. If the BMP is a photograph and it's going on a website, into an email or onto a form with an upload limit, convert it to JPG or WebP instead, or convert to PNG first and then run it through the Image Compressor.

And if a form demands a specific size, say under 200 KB, Compress to a File Size will hit that number directly, measured on the final file.

Does anything get lost going from BMP to PNG? Not pixels. What can change is metadata. BMP stores a print resolution (DPI) in its header, and PNG has its own field for the same thing, but not every converter copies it across. For screen use that's irrelevant. For a scan you plan to print at an exact physical size, check the DPI in the output before you delete the original.

What I'd actually do with a folder of BMPs

Since the conversion is lossless, you don't strictly need the BMP after you've checked the PNG opens properly. I'd still keep originals from scanners or measurement equipment until you've confirmed the PNG works in whatever software reads them next, because some older industrial programs only accept BMP. Everything else, screenshots and old Paint files especially, can go.

My own routine is simple. Screenshots, diagrams and scans of text go to PNG and stay there. Photos go to PNG only if I still plan to edit them, otherwise straight to JPG at around 85% quality or WebP at about 80%, which usually lands a 1920 × 1080 image well under 500 KB. Anything headed for a strict upload form gets a final pass through the compressor with a target size, because guessing quality settings by hand wastes more time than it saves.

If you've got a folder of old BMPs eating disk space, start with one in the free BMP to PNG converter and compare the sizes yourself. For a whole archive at once, bulk conversion is part of UtiliKit Premium (EUR 4.99 a month or EUR 49 lifetime).

Frequently asked questions

Does converting BMP to PNG reduce quality?

No. Both formats are lossless for normal images, so the PNG contains exactly the same pixels as the BMP. Only the way the data is stored changes, which is why the file gets much smaller.

Why is my BMP file so big?

Most BMP files are uncompressed. A 24-bit BMP always takes width times height times 3 bytes, so a 1920 by 1080 image is about 6.2 MB no matter what it shows.

Should I convert BMP to PNG or JPG?

PNG for screenshots, diagrams, logos, scanned text and anything you will edit again. JPG or WebP for photos going on the web or into email, where a much smaller file matters more than perfect pixel accuracy.

Is my image uploaded when I convert it on UtiliKit?

No. The converter runs in your browser and processes the file on your own device, so the image is not sent to a server.

More guides