Initializing... drag & drop files here
Supports: BMP
BMP (Windows Bitmap) is the device-independent raster format Microsoft introduced with Windows in the mid-1980s. By default it stores every pixel uncompressed, so a 1920x1080 image at 24 bits per pixel works out to roughly 1920 x 1080 x 3 bytes plus header — about 6.2 MB on disk. The same image saved as PNG is typically 1-3 MB; as a quality-80 JPG, around 200-400 KB. That gap is why BMP is rarely a good choice for anything that needs to be emailed, embedded, or served on the web.
These figures are derived from the BMP specification (header plus uncompressed pixel array; padding to 4-byte row boundaries adds a small overhead).
| Color Depth | Colors | 1920x1080 Uncompressed | Reduction vs 24-bit |
|---|---|---|---|
| 32-bit (RGBA) | 16.7M + alpha | ~8.3 MB | -33% larger |
| 24-bit (true color) | 16.7 million | ~6.2 MB | baseline |
| 16-bit (high color) | 65,536 | ~4.1 MB | ~33% |
| 8-bit (indexed + palette) | 256 | ~2.1 MB | ~66% |
| 4-bit (indexed + palette) | 16 | ~1.0 MB | ~84% |
| 1-bit (monochrome) | 2 | ~260 KB | ~96% |
| Property | BMP | PNG | JPG | WebP |
|---|---|---|---|---|
| Compression | None by default; RLE for 4/8-bit only | Lossless DEFLATE | Lossy DCT | Lossy or lossless |
| Typical size vs BMP | 1.0x | 0.15-0.45x | 0.03-0.10x | 0.10-0.30x (lossy), ~0.74x of PNG (lossless, per Google) |
| Transparency | 32-bit alpha only | Yes (alpha) | No | Yes |
| Best for | Legacy Windows apps, embedded indexed images | Screenshots, UI, logos | Photographs | Web, modern apps |
| Convert | — | BMP to PNG | BMP to JPG | BMP to WebP |
| Scenario | Recommendation |
|---|---|
| Software contract requires .bmp | Compress with resolution scaling or 8-bit indexed |
| Web publishing or CMS upload | Convert to WebP or JPG |
| Lossless archive of UI or screenshot | Convert to PNG |
| Print or prepress | Convert to TIFF with LZW |
| Multi-page document scan | Convert to PDF |
| Need exact target size for email | Use Specific file size with Smart Scaling |
Yes, but with limits. The Microsoft BMP specification defines two run-length encoding modes: BI_RLE8 for 8-bit (256-color) bitmaps and BI_RLE4 for 4-bit (16-color) bitmaps. These compress runs of identical palette indexes and work well for screenshots, line art, and indexed graphics. The spec does not define RLE for 1-bit, 16-bit, 24-bit, or 32-bit BMPs because those bit depths rarely contain long runs of identical bytes, so any encoding wins are negligible. For true-color photographs stored as BMP, the only practical size reduction is to lower the resolution or convert to a compressed format.
Because BMP stores raw pixel data with no entropy coding. A 24-bit pixel takes 3 bytes whether it is part of a flat blue sky or a noisy texture. JPG applies discrete cosine transforms and quantization to throw away perceptually unimportant detail, often shrinking the file by 10-30x. PNG applies lossless DEFLATE compression with predictive filtering, typically shrinking it by 2-5x. BMP does neither by default.
The Quality preset has the largest effect when the workflow re-encodes to a lossy intermediate, but for BMP itself the bigger lever is the resolution scaling on the next step. If you only need a thumbnail or preview, High at 720p or 1080p will produce a much smaller file than Low at the original 4K dimensions. Choose High when you need the cleanest result and rely on dimension reduction for the size win.
Enter a target (for example, 500 KB or 2 MB) and Smart Scaling estimates the dimensions and bit depth that will land near that number. Because BMP is essentially a fixed-size-per-pixel format, the math is predictable: target bytes divided by bytes-per-pixel gives you the pixel budget. The tool then picks dimensions that match your aspect ratio and stay within budget.
For photographs, yes — banding becomes visible because 256 colors cannot represent smooth gradients. For UI screenshots, icons, line art, and most flat-color graphics, 8-bit indexed (with a generated palette) looks identical to the 24-bit original at one-third the file size. If your BMP is going to be displayed at small sizes or printed at low resolution, the difference is usually invisible.
Yes. Drop a folder of BMPs and the tool processes them in the same browser session. Settings such as Quality preset and target dimensions apply to all files, so a folder of 4K screenshots can be normalized to 1920x1080 with one click.
XConvert processes files in the browser session without requiring sign-up. Very large multi-gigabyte BMPs (uncommon outside scientific imaging) may stress device memory; in that case, downscale before uploading or process in smaller batches.
For most modern workflows, yes. PNG is lossless, supports an alpha channel, and is decoded by every browser and image library shipped in the last 20 years. Per Google's WebP documentation, lossless WebP is on average 26% smaller than PNG again, so if your target supports it, BMP to WebP is the most space-efficient lossless path. Keep BMP only when a downstream tool refuses to open anything else.
Files are uploaded for processing and removed after your session ends. There is no permanent storage, no account requirement, and no watermark added to the output.