Convert BMP Files Online for Free

A BMP Is a Windows Bitmap File Built Around Device-Independent Pixel Data

A BMP file is a raster image associated with Microsoft Windows. It is commonly described as a Windows bitmap or device-independent bitmap, often shortened to DIB. Microsoft’s bitmap-storage documentation says a file using the established bitmap format has the .bmp extension. The goal of the DIB design is to record pixels with enough technical information that software can render the image without depending on the exact display device that created it.

BMP is often encountered in old Windows software, scanners, installers, game assets, and technical archives. It is not automatically uncompressed, but its common pixel-storage choices can produce much larger files than modern photo formats. That size is not proof of higher visual quality. A 24-bit BMP can hold direct colour pixel values with little container complexity; a JPEG, WebP, or AVIF can represent the same dimensions with a much smaller lossy delivery file. Keep BMP when a Windows-era program or workflow specifically requests it, and convert a copy when a modern destination needs another format.

The File Header, DIB Header, Palette, and Pixel Array Explain Why BMP Readers Need More Than an Extension

Microsoft describes the established bitmap file as a BITMAPFILEHEADER followed by a BITMAPINFOHEADER, BITMAPV4HEADER, or BITMAPV5HEADER. A colour table of RGBQUAD entries may follow the information header, followed by the bitmap data. The file header identifies the file, gives its byte size, and records the offset to the first pixel byte. The DIB header records width, height, bits per pixel, compression type, image-data size, display resolution, and colour count.

This layout yields useful diagnostic facts. A palette-based bitmap stores pixel indexes that point into RGBQUAD colour entries. Microsoft’s example notes that an 8 by 8 black-and-white bitmap has 64 one-bit pixel indexes, while a 32 by 32 image with 16 colours needs four bits per pixel. In general, Microsoft says 16-, 24-, and 32-bits-per-pixel bitmaps do not contain colour tables; the application generates an appropriate palette if it needs one. A reader must honour the header rather than guessing from the extension.

Header families also differ. Microsoft lists BITMAPCOREHEADER, BITMAPINFOHEADER, BITMAPV4HEADER, and BITMAPV5HEADER, distinguished by their Size member. CORE and V4 are described as superseded for new work but retained for compatibility. This is why a file called BMP can behave differently in a very old viewer, modern editor, or embedded application.

Six Questions That Decide Whether BMP Is the Right Output

• Does the receiving program explicitly require BMP? If yes, use its documented bit depth and compression expectations.
• Is this an archive master or a sharing copy? Preserve a known-good source and make web or email derivatives separately.
• Do transparent pixels matter? Test the target reader; not every BMP variant or old program handles alpha alike.
• Is file size important? BMP is often inefficient for web delivery and attachments.
• Is colour exactness important? Check bit depth, masks, and rendering in the actual program.
• Could a PNG, TIFF, or JPEG solve the real need better? Pick the requested downstream format rather than BMP by habit.

BMP Compression and Orientation Have Compatibility Details That Modern Image Workflows Often Hide

BMP is sometimes called “uncompressed,” but Microsoft documents run-length encoding for 8-bit BI_RLE8 bitmaps and notes that RLE bitmaps and BITMAPCOREHEADER bitmaps cannot be top-down. The DIB header can describe height and other layout details that tell a reader how rows are ordered. A decoder that assumes the wrong header or orientation can show an upside-down image, wrong colours, or an error even when the pixels themselves are intact.

The BITMAPV4HEADER and BITMAPV5HEADER extend earlier header structures. They can carry more colour and profile-related information than a simple historic bitmap, but software support varies. If a BMP must travel to a legacy program, test a small file generated with the requested header and bit depth. If it travels to a current website, convert to PNG for lossless transparency or JPEG/WebP/AVIF for an appropriately compressed photo instead of asking a browser to download a large device-oriented bitmap.

Microsoft’s documentation also notes that packed DIB profile data follows bitmap bits like file-format data. This is one reason a byte-level edit or careless format conversion can break a file that appeared simple. Work from a copy and use an image decoder rather than changing header bytes or merely renaming a file.

When a BMP Looks Upside Down, Has Wrong Colours, or Is Too Big to Send

An upside-down rendering points to row orientation or a reader that does not understand the declared DIB layout. Reopen the original in a known-compatible editor, export a tested copy, and compare a distinctive top-left detail before sending it. Do not flip the only source repeatedly; preserve it so you can distinguish a decoder issue from an intentional image orientation.

Wrong colours can come from an indexed palette, bitfield masks, or an unsupported header variant. Inspect the reported bits per pixel and test in a second program. A palette-based conversion to a 24- or 32-bit image can change how an old program displays colours, while an inaccurate mask interpretation can swap channels. If visual fidelity is critical, compare colour patches and gradients rather than only recognizing the picture’s subject.

A very large BMP is normal when it carries many direct pixel values. First check dimensions; a screenshot copied at 4K may not need that resolution for an email. Convert a copy to PNG for lossless graphics or to a carefully chosen lossy format for photos. Changing the filename from BMP to JPG does not compress it or create JPEG data; it only confuses the destination program.

BMP Alongside Current Raster Delivery Formats

Questions About Old and New Windows Bitmap Files

Is every BMP uncompressed?
No. Direct pixel storage is common, but Microsoft documents RLE compression for certain 8-bit bitmap data.

Why is a BMP much larger than the same image as JPEG?
BMP often stores direct pixel data, while JPEG uses lossy compression. Large size alone does not mean more visible detail.

Can I rename BMP to PNG or JPG?
No. A valid destination needs its own encoded structure. Use a real conversion and test the output.

Why does one program show the BMP upside down?
Header interpretation and row orientation can differ, especially with old variants. Re-export from a compatible editor and compare the result.

Should I keep an old BMP after conversion?
Yes when it is source evidence or required by an old program. Keep it beside clearly named modern derivatives and a note of the conversion method.

A reliable BMP preservation test uses more than one sample. Include a small indexed image, a 24-bit photograph, a file with transparency or masks when the destination supports it, and an image with a clear top-left marker. Open each in the named target application and compare dimensions, orientation, colours, and file size. This separates a problem in a particular header variant from a broad claim that the program “supports BMP.”

When converting a scan or technical screenshot, keep the pixel dimensions first and decide compression second. Cropping unused borders may be a better size reduction than immediately choosing a lossy JPEG. For diagrams with hard edges and text, PNG is often a safer modern derivative because it stores raster pixels losslessly and supports alpha. For photographs intended for a web page, test a suitable compressed delivery format after retaining the BMP source.

Naming helps avoid an expensive mistake. Use distinct names such as diagram-source.bmp, diagram-web.png, and diagram-email.jpg. A later editor can then identify the original device-oriented bitmap and avoid exporting a new high-quality copy from an already compressed email attachment. The file extension should describe real encoded data, not an aspirational destination.