Initializing... drag & drop files here
Supports: BMP
BMP (Windows Bitmap, also called a device-independent bitmap or DIB) is Microsoft's native raster image format, introduced alongside Windows 2.0 in the late 1980s and also adopted as the native bitmap format of OS/2. It stores an image as a literal grid of pixels, and in its common form it stores them uncompressed — every pixel's color is written out byte-for-byte. That makes BMP dead simple and perfectly lossless, which is exactly why Microsoft Paint, old scanners, and many Windows applications still produce it. It's also why a BMP is enormous: a 4000 × 3000 photo at 24 bits per pixel is roughly 36 MB as a BMP, versus a couple of megabytes as a JPEG of the same dimensions.
Because the format itself is rarely the problem and the size almost always is, nearly every BMP conversion is about getting the same picture into a smaller, more shareable, or more web-friendly file. The most common reasons people convert away from BMP:
| Format | Compression | Lossless | Alpha / transparency | Typical size vs. BMP | Best for |
|---|---|---|---|---|---|
| BMP | None (optional RLE for 4/8-bit) | Yes | Rare (V4 header, seldom used) | baseline (largest) | Windows apps, Paint, simple lossless storage |
| JPG | Lossy DCT | No | No | ~5-10% | Photographs, sharing, the web |
| PNG | Lossless DEFLATE | Yes | Yes | ~20-50% | Screenshots, line art, logos, transparency |
| WebP | Lossy or lossless | Either | Yes | ~10-40% | Modern web pages, smallest files |
| GIF | Lossless LZW (256 colors) | Yes (≤256 colors) | 1-bit (on/off) | varies | Flat graphics, simple icons, short loops |
| TIFF | Lossless (LZW / ZIP) or none | Yes | Yes | ~30-100% | Print, scanning, archival |
| Per-image (can embed JPEG) | Depends | n/a | varies | Documents, printing, sharing |
Because a standard BMP stores pixels uncompressed — each pixel's color is written out in full. A 24-bit BMP needs 3 bytes per pixel with no compression at all, so a 12-megapixel photo lands around 36 MB. JPG applies lossy compression that discards detail the eye barely notices, and PNG applies lossless compression that packs the data more efficiently, so both routinely produce files a fraction of the BMP's size. BMP does support an optional run-length encoding (RLE) mode for 4-bit and 8-bit indexed images, but most BMP files in the wild are saved fully uncompressed, which is the entire reason people convert them.
No. PNG uses lossless DEFLATE compression, so a BMP-to-PNG conversion keeps every pixel exactly as it was — the file just takes up far less space. This is the right choice for screenshots, diagrams, logos, and anything with sharp edges or text, where JPG's lossy compression would introduce visible "ringing" artifacts around the edges. In our testing, a 24-bit uncompressed BMP screenshot dropped from roughly 6 MB to well under 1 MB as a PNG with no visible change at all. If you instead pick JPG, you do trade some quality for an even smaller file.
Yes, slightly — JPG is a lossy format, so it discards some image data to achieve its dramatic size reduction. For photographs that loss is essentially invisible at the default "Very High" quality, which is why JPG is the standard target for shrinking a photographic BMP. For line art, screenshots, or anything with hard edges and flat color, JPG is a poor fit — it smears edges and adds blocky artifacts — and you should convert to PNG or WebP instead, both of which can stay lossless.
BMP is natively supported almost everywhere on Windows: Microsoft Paint, the Photos app, and the file preview all read it directly. On macOS, Preview opens BMP files, and on every platform image editors like Photoshop, GIMP, and Paint.NET handle them. Most modern web browsers can also display a BMP if you open the file directly, though BMP is essentially never used as an embedded web image because of its size — which is exactly why converting to JPG, PNG, or WebP is the common step before putting a bitmap online.
Transparency: technically yes, but practically no. An alpha channel was added to the format with the BITMAPV4HEADER in Windows 95, but very few applications write or read transparent BMPs, so you should treat BMP as an opaque format. If you need real transparency, convert to PNG or WebP, which support it reliably. Animation: no — BMP holds a single still image only. For a simple animated graphic, GIF or WebP is the right target.
For photographs, WebP at lossy quality usually produces the smallest file while looking nearly identical to the original, with JPG a close and more universally compatible second. For graphics, screenshots, and line art where you want zero quality loss, lossless WebP or PNG gives you the smallest lossless result. If you only care about absolute minimum size and the image is a simple flat graphic with few colors, GIF (capped at 256 colors) can be tiny. Pick Specific file size in the options if you need to hit an exact KB or MB target.
Yes. Your BMP is uploaded over an encrypted (TLS) connection, converted on our servers, and the original and the output are deleted automatically a few hours later. There's no sign-up, no watermark on the output, and files are never shared or made public. The only real limit on a very large bitmap is upload time over your connection — multi-hundred-megabyte BMPs convert fine, they just take longer to upload than a compressed format would.