BMP file format
|Internet media type||
|Type code||'BMP '
|Uniform Type Identifier||com.microsoft.bmp|
|Type of format||Raster graphics|
The BMP file format, also known as bitmap image file or device independent bitmap (DIB) file format or simply a bitmap, is a raster graphics image file format used to store bitmap digital images, independently of the display device (such as a graphics adapter), especially on Microsoft Windows and OS/2 operating systems.
The BMP file format is capable of storing 2D digital images of arbitrary width, height, and resolution, both monochrome and color, in various color depths, and optionally with data compression, alpha channels, and color profiles.
- 1 Device-independent bitmaps and the BMP file format
- 2 File structure
- 3 Usage of BMP format
- 4 Related formats
- 5 See also
- 6 References
- 7 External links
Device-independent bitmaps and the BMP file format
Microsoft has defined a particular representation of color bitmaps of different color depths, as an aid to exchanging bitmaps between devices and applications with a variety of internal representations. They called these device-independent bitmaps or DIBs, and the file format for them is called DIB file format or BMP image file format.
According to Microsoft support:
A device-independent bitmap (DIB) is a format used to define device-independent bitmaps in various color resolutions. The main purpose of DIBs is to allow bitmaps to be moved from one device to another (hence, the device-independent part of the name). A DIB is an external format, in contrast to a device-dependent bitmap, which appears in the system as a bitmap object (created by an application...). A DIB is normally transported in metafiles (usually using the StretchDIBits() function), BMP files, and the Clipboard (CF_DIB data format).
The following sections discuss the data stored in the BMP file or DIB in detail. This is the standard BMP file format. Some applications create bitmap image files which are not compliant with the current Microsoft documentation. Also, not all fields are used; a value of 0 will be found in these unused fields.
The bitmap image file consists of fixed-size structures (headers) as well as variable-size structures appearing in a predetermined sequence. Many different versions of some of these structures can appear in the file, due to the long evolution of this file format.
Referring to the diagram 1, the bitmap file is composed of structures in the following order:
|Bitmap File Header||No||14 Bytes||To store general information about the Bitmap Image File||Not needed after the file is loaded in memory|
(however 7 different versions exist)
|To store detailed information about the bitmap image and define the pixel format||Immediately follows the Bitmap File Header|
|Extra bit masks||Yes||3 or 4 DWORDs
(12 or 16 Bytes)
|To define the pixel format||Present only in case the DIB Header is the BITMAPINFOHEADER|
|Color Table||Semi-optional||Variable-size||To define colors used by the bitmap image data (Pixel Array)||Mandatory for color depths <= 8|
|Gap1||Yes||Variable-size||Structure alignment||An artifact of the File Offset to PixelArray in the Bitmap File Header|
|Pixel Array||No||Variable-size||To define the actual values of the pixels||The pixel format is defined by the DIB Header or Extra bit masks. Each row in the Pixel Array is padded to a multiple of 4 bytes in size|
|Gap2||Yes||Variable-size||Structure alignment||An artifact of the ICC Profile Data offset field in the DIB Header|
|ICC Color Profile||Yes||Variable-size||To define the color profile for color management||Can also contain a path to an external file containing the color profile. When loaded in memory as "non-packed DIB", it is located between the color table and gap1.|
DIBs in memory
A bitmap image file loaded into memory becomes a DIB data structure – an important component of the Windows GDI API. The in-memory DIB data structure is almost the same as the BMP file format, but it does not contain the 14-byte bitmap file header and begins with the DIB header. For DIBs loaded in memory, the color table can also consist of 16 bit entries, that constitute indexes to the currently realized palette (an additional level of indirection), instead of explicit RGB color definitions. In all cases, the pixel array must begin at a memory address that is a multiple of 4 bytes. In non-packed DIBs loaded in memory, the optional color profile data should be located immediately after the color table and before the gap1 and pixel array (unlike in diag. 1).
When the size of gap1 and gap2 is zero, the in-memory DIB data structure is customarily referred to as "packed DIB" and can be referred to by a single pointer pointing to the beginning of the DIB header. In all cases, the pixel array must begin at a memory address that is a multiple of 4 bytes. In some cases it may be necessary to adjust the number of entries in the color table in order to force the memory address of the pixel array to a multiple of 4 bytes. For "packed DIBs" loaded in memory, the optional color profile data should immediately follow the pixel array, as depicted in diag. 1 (with gap1=0 and gap2=0).
"Packed DIBs" are required by Windows clipboard API functions as well as by some Windows patterned brush and resource functions.
Bitmap file header
This block of bytes is at the start of the file and is used to identify the file. A typical application reads this block first to ensure that the file is actually a BMP file and that it is not damaged. The first two bytes of the BMP file format are the character 'B' then the character 'M' in 1-byte ASCII encoding. All of the integer values are stored in little-endian format (i.e. least-significant byte first).
|0||2 bytes||the header field used to identify the BMP & DIB file is 0x42 0x4D in hexadecimal, same as BM in ASCII. The following entries are possible:
|2||4 bytes||the size of the BMP file in bytes|
|6||2 bytes||reserved; actual value depends on the application that creates the image|
|8||2 bytes||reserved; actual value depends on the application that creates the image|
|10||4 bytes||the offset, i.e. starting address, of the byte where the bitmap image data (pixel array) can be found.|
The size value occupies 4 bytes by default. However, with the use of the 4 reserved bytes, this value can occupy 8 bytes (64 bits) while still conforming to the BMPfile header format.
DIB header (bitmap information header)
This block of bytes tells the application detailed information about the image, which will be used to display the image on the screen. The block also matches the header used internally by Windows and OS/2 and has several different variants. All of them contain a dword (32 bit) field, specifying their size, so that an application can easily determine which header is used in the image. The reason that there are different headers is that Microsoft extended the DIB format several times. The new extended headers can be used with some GDI functions instead of the older ones, providing more functionality. Since the GDI supports a function for loading bitmap files, typical Windows applications use that functionality. One consequence of this is that for such applications, the BMP formats that they support match the formats supported by the Windows version being run. See the table below for more information.
|Size||Header Name||OS support||Features Added (incremental)||in Bitmap Files Written by|
|OS/2 and also all Windows versions since Windows 3.0|
|OS/2||Adds halftoning. Adds RLE and Huffman 1D compression.|
|40||BITMAPINFOHEADER||all Windows versions since Windows 3.0||Removes RLE-24 and Huffman 1D compression. Adds 16bpp and 32bpp pixel formats. Adds optional RGB bit masks.||Adobe Photoshop|
|52||BITMAPV2INFOHEADER||Undocumented.||Removes optional RGB bit masks. Adds mandatory RGB bit masks.|
|56||BITMAPV3INFOHEADER||Undocumented.||Adds mandatory alpha channel bit mask.||Adobe Photoshop|
|108||BITMAPV4HEADER||all Windows versions since Windows 95/NT4||Adds color space type and gamma correction|
|124||BITMAPV5HEADER||Windows 98/2000 and newer||Adds ICC color profiles|
Versions after BITMAPCOREHEADER only add fields to the end of the header of the previous version. For example: BITMAPV2INFOHEADER adds fields to BITMAPINFOHEADER and BITMAPV3INFOHEADER adds fields to BITMAPV2INFOHEADER (or, BITMAPINFOHEADER is a stripped version of BITMAPV2INFOHEADER)
For compatibility reasons, most applications use the older DIB headers for saving files. With OS/2 being obsolete, for now the common format is the BITMAPINFOHEADER header. See next table for its description. All values are stored as unsigned integers, unless explicitly noted.
|14||4||the size of this header (40 bytes)|
|18||4||the bitmap width in pixels (signed integer).|
|22||4||the bitmap height in pixels (signed integer).|
|26||2||the number of color planes being used. Must be set to 1.|
|28||2||the number of bits per pixel, which is the color depth of the image. Typical values are 1, 4, 8, 16, 24 and 32.|
|30||4||the compression method being used. See the next table for a list of possible values.|
|34||4||the image size. This is the size of the raw bitmap data (see below), and should not be confused with the file size.|
|38||4||the horizontal resolution of the image. (pixel per meter, signed integer)|
|42||4||the vertical resolution of the image. (pixel per meter, signed integer)|
|46||4||the number of colors in the color palette, or 0 to default to 2n.|
|50||4||the number of important colors used, or 0 when every color is important; generally ignored.|
Note: The image size field can be 0 for BI_RGB bitmaps.
The compression method field (bytes #30-33) can have the following values:
|Value||Identified by||Compression method||Comments|
|1||BI_RLE8||RLE 8-bit/pixel||Can be used only with 8-bit/pixel bitmaps|
|2||BI_RLE4||RLE 4-bit/pixel||Can be used only with 4-bit/pixel bitmaps|
|3||BI_BITFIELDS||Bit field or Huffman 1D compression for BITMAPCOREHEADER2||Pixel format defined by bit masks or Huffman 1D compressed bitmap for BITMAPCOREHEADER2|
|4||BI_JPEG||JPEG or RLE-24 compression for BITMAPCOREHEADER2||The bitmap contains a JPEG image or RLE-24 compressed bitmap for BITMAPCOREHEADER2|
|5||BI_PNG||PNG||The bitmap contains a PNG image|
|6||BI_ALPHABITFIELDS||Bit field||This value is valid in Windows CE .NET 4.0 and later.|
Note: BI_JPEG and BI_PNG are for printer drivers and are not supported when rendering to the screen.
The OS/2 BITMAPCOREHEADER header is also popular:
|14||4||the size of this header (12 bytes)|
|18||2||the bitmap width in pixels.|
|20||2||the bitmap height in pixels.|
|22||2||the number of color planes; 1 is the only legal value|
|24||2||the number of bits per pixel. Typical values are 1, 4, 8 and 24.|
Note: OS/2 BITMAPCOREHEADER bitmaps cannot be compressed and cannot be 16 or 32 bits/pixel. All values in the OS/2 BITMAPCOREHEADER header are unsigned integers.
A 16-bit and 32-bit version of DIB with an integrated alpha channel has been introduced with the undocumented BITMAPV3INFOHEADER and with the documented BITMAPV4HEADER (since Windows 95) and is used within Windows XP logon and theme system as well as Microsoft Office (since v2000); it is supported by some image editing software, such as Adobe Photoshop since version 7 and Adobe Flash since version MX 2004 (then known as Macromedia Flash). It is also supported by GIMP, Google Chrome, MS-PowerPoint and MS-Word.
The color table (palette) occurs in the BMP image file directly after the BMP file header, the DIB header (and after optional three red, green and blue bitmasks if the BITMAPINFOHEADER header with BI_BITFIELDS option is used). Therefore, its offset is the size of the BITMAPFILEHEADER plus the size of the DIB header (plus optional 12 bytes for the three bit masks).
Note: On Windows CE the BITMAPINFOHEADER header can be used with the BI_ALPHABITFIELDS option in the biCompression member. In such case, four optional bitmasks follow the BITMAPINFOHEADER header instead of the three bitmasks mentioned above, thus the color table's offset is the size of the BITMAPFILEHEADER plus the size of the BITMAPINFOHEADER header plus the 16 bytes of the four bitmasks (red, green, blue and alpha).
The number of entries in the palette is either 2n or a smaller number specified in the header (in the OS/2 BITMAPCOREHEADER header format, only the full-size palette is supported). In most cases, each entry in the color table occupies 4 bytes, in the order blue, green, red, 0x00 (see below for exceptions). This is indexed in the BITMAPINFOHEADER under the function biBitCount.
The color table is a block of bytes (a table) listing the colors used by the image. Each pixel in an indexed color image is described by a number of bits (1, 4, or 8) which is an index of a single color described by this table. The purpose of the color palette in indexed color bitmaps is to inform the application about the actual color that each of these index values corresponds to. The purpose of the color table in non-indexed (non-palettized) bitmaps is to list the colors used by the bitmap for the purposes of optimization on devices with limited color display capability and to facilitate future conversion to different pixel formats and paletization.
The colors in the color table are usually specified in the 4-byte per entry 126.96.36.199.8 format (in RGBAX notation). The color table used with the OS/2 BITMAPCOREHEADER uses the 3-byte per entry 188.8.131.52.0 format. For DIBs loaded in memory, the color table can optionally consist of 2-byte entries - these entries constitute indexes to the currently realized palette instead of explicit RGB color definitions.
Microsoft does not disallow the presence of a valid alpha channel bit mask in BITMAPV4HEADER and BITMAPV5HEADER for 1bpp, 4bpp and 8bpp indexed color images, which indicates that the color table entries can also specify an alpha component using the 8.8.8.[0-8].[0-8] format via the RGBQUAD.rgbReserved member. However, some versions of Microsoft's documentation disallow this feature by stating that the RGBQUAD.rgbReserved member "must be zero".
As mentioned above, the color table is normally not used when the pixels are in the 16-bit per pixel (16bpp) format (and higher); there are normally no color table entries in those bitmap image files. However, the Microsoft documentation (on the MSDN web site as of Nov. 16, 2010) specifies that for 16bpp (and higher), the color table can be present to store a list of colors intended for optimization on devices with limited color display capability, while it also specifies, that in such cases, no indexed palette entries are present in this Color Table. This may seem like a contradiction if no distinction is made between the mandatory palette entries and the optional color list.
The bits representing the bitmap pixels are packed in rows. The size of each row is rounded up to a multiple of 4 bytes (a 32-bit DWORD) by padding.
For images with height > 1, multiple padded rows are stored consecutively, forming a Pixel Array.
The total number of bytes necessary to store one row of pixels can be calculated as:
- ImageWidth is expressed in pixels.
The total amount of bytes necessary to store an array of pixels in an n bits per pixel (bpp) image, with 2n colors, can be calculated by accounting for the effect of rounding up the size of each row to a multiple of a 4 bytes, as follows:
- ImageHeight is expressed in pixels. The absolute value is necessary because ImageHeight can be negative
The total bitmap image file size can be approximated as:
- for BPP ≤ 8 ( because for pixels larger than 8 bits, the palette is not mandatory )
Only images with 8 or fewer bits per pixel must account for the palette. 16bpp images (or higher), may omit the palette part from the size calculation, as follows:
- for Bits per Pixel > 8.
In the formulas above, the number 54 is the combined size of the 14 byte bitmap file header and the 40 byte popular WindowsDIB header – the BITMAPINFOHEADER (some other DIB header versions will be larger or smaller than that as described by the table above) and the expression is the size of the color palette in bytes.
This total file size formula is only an approximation, since the size of the color palette will be bytes for the OS/2 DIB header version BITMAPCOREHEADER, and some files may define only the number of colors needed by the image, potentially fewer than .
An additional size uncertainty is introduced by the optional presence of the 12 or 16 bytes needed for the extra bit masks stored immediately after the BITMAPINFOHEADER DIB header and the variable-size GAP depicted in Diag.1
Pixel array (bitmap data)
The pixel array is a block of 32-bit DWORDs, that describes the image pixel by pixel. Normally pixels are stored "upside-down" with respect to normal image raster scan order, starting in the lower left corner, going from left to right, and then row by row from the bottom to the top of the image.
Unless BITMAPCOREHEADER is used, uncompressed Windows bitmaps also can be stored from the top to bottom, when the Image Height value is negative.
In the original OS/2 DIB, the only four legal values of color depth were 1, 4, 8, and 24 bits per pixel (bpp). Contemporary DIB Headers allow pixel formats with 1, 2, 4, 8, 16, 24 and 32 bits per pixel (bpp).
Padding bytes (not necessarily 0) must be appended to the end of the rows in order to bring up the length of the rows to a multiple of four bytes. When the pixel array is loaded into memory, each row must begin at a memory address that is a multiple of 4. This address/offset restriction is mandatory only for Pixel Arrays loaded in memory. For file storage purposes, only the size of each row must be a multiple of 4 bytes while the file offset can be arbitrary.
A 24-bit bitmap with Width=1, would have 3 bytes of data per row (blue, green, red) and 1 byte of padding, while Width=2 would have 2 bytes of padding, Width=3 would have 3 bytes of padding, and Width=4 would not have any padding at all.
Bitmap image files are typically much larger than image file formats compressed with other algorithms, for the same image. For example, the 1058×1058 Wikipedia logo, which occupies about 271 kB in the lossless PNG format, takes about 3358 kB as a 24bpp BMP image file. Uncompressed formats are generally unsuitable for transferring images on the internet or other slow or capacity-limited media.
Indexed color images may be compressed with 4-bit or 8-bit RLE or Huffman 1D algorithm.
OS/2 BITMAPCOREHEADER2 24bpp images may be compressed with the 24-bit RLE algorithm.
The 16bpp and 32bpp images are always stored uncompressed.
Note that images in all color depths can be stored without compression if so desired.
In a bitmap image file on a disk or a bitmap image in memory, the pixels can be defined by a varying number of bits.
- The 1-bit per pixel (1bpp) format supports 2 distinct colors, (for example: black and white). The pixel values are stored in each bit, with the first (left-most) pixel in the most-significant bit of the first byte. Each bit is an index into a table of 2 colors. An unset bit will refer to the first color table entry, and a set bit will refer to the last (second) color table entry.
- The 2-bit per pixel (2bpp) format supports 4 distinct colors and stores 4 pixels per 1 byte, the left-most pixel being in the two most significant bits (Windows CE only). Each pixel value is a 2-bit index into a table of up to 4 colors.
- The 4-bit per pixel (4bpp) format supports 16 distinct colors and stores 2 pixels per 1 byte, the left-most pixel being in the more significant nibble. Each pixel value is a 4-bit index into a table of up to 16 colors.
- The 8-bit per pixel (8bpp) format supports 256 distinct colors and stores 1 pixel per 1 byte. Each byte is an index into a table of up to 256 colors.
- The 16-bit per pixel (16bpp) format supports 65536 distinct colors and stores 1 pixel per 2 byte WORD. Each WORD can define the alpha, red, green and blue samples of the pixel.
- The 24-bit pixel (24bpp) format supports 16,777,216 distinct colors and stores 1 pixel value per 3 bytes. Each pixel value defines the red, green and blue samples of the pixel (184.108.40.206.0 in RGBAX notation). Specifically in the order (blue, green and red, 8-bits per each sample).
- The 32-bit per pixel (32bpp) format supports 4,294,967,296 distinct colors and stores 1 pixel per 4 byte DWORD. Each DWORD can define the Alpha, Red, Green and Blue samples of the pixel.
In order to resolve the ambiguity of which bits define which samples, the DIB Headers provide certain defaults as well as specific BITFIELDS which are bit masks that define the membership of particular group of bits in a pixel to a particular channel.
The following diagram defines this mechanism:
Diag. 2 – The BITFIELDS mechanism for a 32 bit pixel depicted in RGBAX sample length notation
The sample fields defined by the BITFIELDS bit masks have to be contiguous and non-overlapping but the order of the sample fields is arbitrary. The most ubiquitous field order is: Alpha, Blue, Green, Red (MSB to LSB).
The red, green and blue bit masks are valid only when the Compression member of the DIB header is set to BI_BITFIELDS.
The alpha bit mask is valid whenever it is present in the DIB header or when the Compression member of the DIB header is set to BI_ALPHABITFIELDS (Windows CE only).
Diag.3 – The pixel format with an alpha channel in a 16 bit pixel (in RGBAX sample Length notation) actually generated by Adobe Photoshop
- The table below lists all of the possible pixel formats of a DIB (in RGBAX notation).
The BITFIELD mechanism described above allows for the definition of tens of thousands different pixel formats, however only several of them are used in practice, such as:
- All palettized formats (marked in yellow in the table above)
Following is an example of a 2×2 pixel, 24-bit bitmap (Windows DIB header BITMAPINFOHEADER) with pixel format 220.127.116.11.0 (in RGBAX notation).
||"BM"||ID field (42h, 4Dh)|
||70 Bytes||Size of the BMP file|
||54 bytes||Offset where the pixel array (bitmap data) can be found|
||40 bytes||Number of bytes in the DIB header (from this point)|
||2 pixels (left to right order)||Width of the bitmap in pixels|
||2 pixels (bottom to top order)||Height of the bitmap in pixels. Positive for bottom to top pixel order. Negative for top to bottom pixel order.|
||1 plane||Number of color planes being used|
||24 bits||Number of bits per pixel|
||0||BI_RGB, no pixel array compression used|
||16 bytes||Size of the raw data in the pixel array (including padding)|
||2,835 pixels/meter||Horizontal resolution of the image|
||2,835 pixels/meter||Vertical resolution of the image|
||0 colors||Number of colors in the palette|
||0 important colors||0 means all colors are important|
|Start of pixel array (bitmap data)|
||0 0 255||Red, Pixel (0,1)|
||255 255 255||White, Pixel (1,1)|
||0 0||Padding for 4 byte alignment (could be a value other than zero)|
||255 0 0||Blue, Pixel (0,0)|
||0 255 0||Green, Pixel (1,0)|
||0 0||Padding for 4 byte alignment (could be a value other than zero)|
Following is an example of a 4×2 pixel, 32-bit bitmap with opacity values in the alpha channel (Windows DIB Header BITMAPV4HEADER) with pixel format 18.104.22.168.0 (in RGBAX notation).
||"BM"||Magic number (unsigned integer 66, 77)|
||154 Bytes||Size of the BMP file|
||122 bytes from the start of the file||Offset where the pixel array (bitmap data) can be found|
||108 bytes||Number of bytes in the DIB header (from this point)|
||4 pixels (left to right order)||Width of the bitmap in pixels|
||2 pixels (bottom to top order)||Height of the bitmap in pixels|
||1 plane||Number of color planes being used|
||32 bits||Number of bits per pixel|
||3||BI_BITFIELDS, no pixel array compression used|
||32 bytes||Size of the raw data in the pixel array (including padding)|
||2,835 pixels/meter||Horizontal physical resolution of the image|
||2,835 pixels/meter||Vertical physical resolution of the image|
||0 colors||Number of colors in the palette|
||0 important colors||0 means all colors are important|
||00FF0000 in big-endian||Red channel bit mask (valid because BI_BITFIELDS is specified)|
||0000FF00 in big-endian||Green channel bit mask (valid because BI_BITFIELDS is specified)|
||000000FF in big-endian||Blue channel bit mask (valid because BI_BITFIELDS is specified)|
||FF000000 in big-endian||Alpha channel bit mask|
||LCS_WINDOWS_COLOR_SPACE||Type of Color Space|
||CIEXYZTRIPLE Color Space endpoints||Unused when LCS_WINDOWS_COLOR_SPACE is specified|
||0 Red Gamma||Unused when LCS_WINDOWS_COLOR_SPACE is specified|
||0 Green Gamma||Unused when LCS_WINDOWS_COLOR_SPACE is specified|
||0 Blue Gamma||Unused when LCS_WINDOWS_COLOR_SPACE is specified|
|Start of the Pixel Array (the bitmap Data)|
||255 0 0 127||Blue (Alpha: 127), Pixel (0,1)|
||0 255 0 127||Green (Alpha: 127), Pixel (1,1)|
||0 0 255 127||Red (Alpha: 127), Pixel (2,1)|
||255 255 255 127||White (Alpha: 127), Pixel (3,1)|
||255 0 0 255||Blue (Alpha: 255), Pixel (0,0)|
||0 255 0 255||Green (Alpha: 255), Pixel (1,0)|
||0 0 255 255||Red (Alpha: 255), Pixel (2,0)|
||255 255 255 255||White (Alpha: 255), Pixel (3,0)|
Note that the bitmap data starts with the lower left hand corner of the image.
Usage of BMP format
The simplicity of the BMP file format, and its widespread familiarity in Windows and elsewhere, as well as the fact that this format is relatively well documented and free of patents, makes it a very common format that image processing programs from many operating systems can read and write.
Many older graphical user interfaces used bitmaps in their built-in graphics subsystems; for example, the Microsoft Windows and OS/2 platforms' GDI subsystem, where the specific format used is the Windows and OS/2 bitmap file format, usually named with the file extension of
While most BMP files have a relatively large file size due to lack of any compression (or generally low-ratio run-length encoding on palletized images), many BMP files can be considerably compressed with lossless data compression algorithms such as ZIP because they contain redundant data. Some formats, such as RAR, even include routines specifically targeted at efficient compression of such data.
The X Window System uses a similar XBM format for black-and-white images, and XPM (pixelmap) for color images. There are also a variety of "raw" formats, which saves raw data with no other information. The Portable Pixmap (PPM) and Truevision TGA formats also exist, but are less often used – or only for special purposes; for example, TGA can contain transparency information.
Numerous other bitmap file formats are in existence, though most are not widely used.
- "DIBs and Their Uses". Microsoft Help and Support. 2005-02-11.
- MSDN - BITMAPINFOHEADER: BI_ALPHABITFIELDS in biCompression member
- MSDN Bitmap Header Types
- MSDN BITMAPINFO Structure
- Feng Yuan - Windows graphics programming: Win32 GDI and DirectDraw: Packed Device-Independent Bitmap (CreateDIBPatternBrush, CreateDIBPatternBrushPt, FindResource, LoadResource, LockResource)
- "JPEG and PNG Extensions for Specific Bitmap Functions and Structures".
- "GFF Format Summary: OS/2 Bitmap".
- MSDN - BITMAPV4HEADER: The member bV4AlphaMask
- MSDN - RGBQUAD: rgbReserved member
- see note under biClrUsed MSDN BITMAPINFOHEADER
- MSDN - BITMAPINFOHEADER: The member biBitCount
- MSDN: Windows CE - BITMAPINFOHEADER Structure
- Julian Smart, Stefan Csomor, and Kevin Hock (2006). Cross-Platform GUI Programming with Wxwidgets. Prentice Hall. ISBN 0-13-147381-6.
- "List of bitmap file types". Search File-Extensions.org.
- Bitmap Format, at sourceforge.net
- Bitmap File Structure, at digicamsoft.com
- An introduction to DIBs (Device Independent Bitmaps), at herdsoft.com
- BMP test images, at wvnet.edu
- A simple bitmap loader C++ class, at kalytta.com
- libbmp24 at github. portable and simple C++ open source project. bitmap image library.
- The BMP File Format, Part 1 By David Charlap at Dr. Dobb's journal of software tools (drdobbs.com), March 1995
- Microsoft Windows Bitmap File Format Summary, at fileformat.info
- Microsoft bitmap v2 and v3 formats, archived at netghost.narod.ru
- OS/2 bitmap formats, archived at netghost.narod.ru