BMP

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
m
m (→‎Various)
 
(32 intermediate revisions by 9 users not shown)
Line 3: Line 3:
 
|subcat=Graphics
 
|subcat=Graphics
 
|extensions={{ext|bmp}}, {{ext|rle}}, {{ext|dib}}, others
 
|extensions={{ext|bmp}}, {{ext|rle}}, {{ext|dib}}, others
 +
|mimetypes={{mimetype|image/bmp}}
 
|locfdd={{LoCFDD|fdd000189}}
 
|locfdd={{LoCFDD|fdd000189}}
 
|pronom={{PRONOM|fmt/116}}, others
 
|pronom={{PRONOM|fmt/116}}, others
 +
|wikidata={{wikidata|Q192869}}
 +
|kaitai struct=bmp
 
|released=1987
 
|released=1987
 
}}
 
}}
Line 11: Line 14:
 
Though seemingly a simple format, it is complicated by its many different versions, lack of an official specification, lack of any version control process, and ambiguities and contradictions in the documentation.
 
Though seemingly a simple format, it is complicated by its many different versions, lack of an official specification, lack of any version control process, and ambiguities and contradictions in the documentation.
  
 +
== Discussion ==
 +
The term ''DIB'' can mean several different things:
 +
* A synonym for BMP file format.
 +
* An in-memory DIB object, with no file header. The header data and the bitmap data do not have to be stored contiguously. Some Win32 API functions use this format.
 +
* A "packed DIB" memory object or file component, with no file header. The header data and the bitmap data are stored contiguously. This is a standard [[Windows clipboard|clipboard format]], for example.
 +
* A "packed DIB" stored in a file by itself.
 +
 +
A number of Windows-centric formats contain some nonstandard modified or compressed form of BMP/DIB, intended to be reconstructed as a DIB at runtime.
 +
 +
== Format details ==
 +
 +
=== Compression ===
 
Images are usually uncompressed, but [[Run-length encoding|RLE]] compression can be used under some conditions. [[JPEG]], [[PNG]], and [[Modified Huffman|Huffman 1D]] compression are also theoretically possible, but rarely supported.
 
Images are usually uncompressed, but [[Run-length encoding|RLE]] compression can be used under some conditions. [[JPEG]], [[PNG]], and [[Modified Huffman|Huffman 1D]] compression are also theoretically possible, but rarely supported.
 +
 +
=== File structure ===
 +
A BMP file starts with a 14-byte "BITMAPFILEHEADER" structure.
 +
 +
Immediately after that is another header which we'll refer to as the "info header", though some versions of it are named "core header" instead. There are a number of different versions and sub-versions of it. It starts with 4-byte integer indicating its size, which ''mostly'' reveals its version.
 +
 +
The pixel data is pointed to by a field in BITMAPFILEHEADER. There can be other data segments, e.g. for a color palette, before (and, rarely, after) the pixel data.
 +
 +
Pixel data is usually stored from bottom up (but is top-down if the header indicates a negative height). If uncompressed, each row is padded to a multiple of 4 bytes.
  
 
== Identifiers ==
 
== Identifiers ==
Line 19: Line 43:
  
 
== Identification ==
 
== Identification ==
−
BMP files start with bytes <code>'B' 'M'</code>.
+
BMP files start with the ASCII signature "{{magic|BM}}".
 +
 
 +
The bytes at the beginning of the file match one of these two patterns:
 +
 
 +
42 4d ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 00 00 0c 00
 +
00 00 ?? ?? ?? ?? 01 00 ?? 00
 +
 
 +
or
 +
 
 +
42 4d ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 00 00 ?? 00
 +
00 00 ?? ?? ?? ?? ?? ?? ?? ?? 01 00 ?? 00
  
−
That's not a very distinctive signature, but it's hard to give any definite rules beyond that. The bytes at offset 6 to 9 are usually all zero, but a few OS/2 BMP files have nonzero "hotspot coordinates" at that location.
+
The "reserved" bytes at offset 6 to 9 are usually all zero, but a few OS/2 BMP files have nonzero "hotspot coordinates" there.
  
−
See also [[VBM (VDC BitMap)]], which has a similar signature.
+
Compare to [[VBM (VDC BitMap)]], an obscure format with a similar signature.
  
 
== Well-known versions ==
 
== Well-known versions ==
−
BMP files use a common 14-byte file header, named BITMAPFILEHEADER. Following that is the "Info header", which begins with a 4-byte integer indicating its size. The Info header size (mostly) reveals the version of BMP that the file uses.
 
  
 
=== Windows BMP v2 ===
 
=== Windows BMP v2 ===
Line 43: Line 76:
  
 
Windows CE also extended it, for example to allow 2 bits/pixel (see [[Pocket PC Bitmap]]), but its extensions were not migrated to the BMP v4 and v5 formats.
 
Windows CE also extended it, for example to allow 2 bits/pixel (see [[Pocket PC Bitmap]]), but its extensions were not migrated to the BMP v4 and v5 formats.
 +
 +
Microsoft's GDI+ reportedly supports BMP images with 64 bits/pixel[https://docs.microsoft.com/en-us/windows/win32/gdiplus/-gdiplus-types-of-bitmaps-about], but no technical documentation of this extension has been located.
  
 
It is apparently possible for OS/2 BMP 2.0 format to masquerade as Windows BMP v3. The upshot is that if the compression type is 3 and the bit depth is 1, or the compression type is 4 and the bit depth is 24, then the file should be treated as OS/2 BMP 2.0.
 
It is apparently possible for OS/2 BMP 2.0 format to masquerade as Windows BMP v3. The upshot is that if the compression type is 3 and the bit depth is 1, or the compression type is 4 and the bit depth is 24, then the file should be treated as OS/2 BMP 2.0.
Line 76: Line 111:
  
 
=== OS/2 BMP 2.0 ===
 
=== OS/2 BMP 2.0 ===
−
* Info header size: 16–64 (16, 40, 48, and 64 may be most common)
+
* Info header size: 16–64 (16, 24, 40, 48, and 64 may be most common)
 
* Info header name: BITMAPCOREHEADER2 or OS22XBITMAPHEADER
 
* Info header name: BITMAPCOREHEADER2 or OS22XBITMAPHEADER
 
* PRONOM: {{PRONOM|x-fmt/270}}
 
* PRONOM: {{PRONOM|x-fmt/270}}
Line 92: Line 127:
 
* Info header name: BITMAPV2INFOHEADER
 
* Info header name: BITMAPV2INFOHEADER
  
−
No details known.
+
Uncertain; possibly an abbreviated V4/V5 header.
  
 
=== BITMAPV3INFOHEADER ===
 
=== BITMAPV3INFOHEADER ===
Line 98: Line 133:
 
* Info header name: BITMAPV3INFOHEADER
 
* Info header name: BITMAPV3INFOHEADER
  
−
No details known.
+
Uncertain; possibly an abbreviated V4/V5 header.
 +
 
 +
=== Packed DIB file ===
 +
Same as the common BMP formats, but omits the 14-byte ''file header''.
 +
 
 +
=== OS/2 Bitmap Array ===
 +
Sometimes, an [[OS/2 Bitmap Array]] file containing one or more bitmaps is considered to be a kind of BMP file. Such a file begins with an extra 14-byte header, with signature "<code>BA</code>". (But note that deleting this header is not quite enough to get a valid BMP file.)
  
 
== Symbol definitions ==
 
== Symbol definitions ==
Line 155: Line 196:
  
 
== Specifications ==
 
== Specifications ==
−
* BMP (as "DeviceIndependentBitmap") is defined in the [http://msdn.microsoft.com/en-us/library/cc215212.aspx Windows Metafile Specification]
+
* Most of the format (but not the BITMAPFILEHEADER) is defined in the [https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-wmf/4813e7fd-52d0-4f42-965f-228c8b7488d2 Windows Metafile Specification] (as "DeviceIndependentBitmap")
−
* [http://msdn.microsoft.com/en-us/library/dd183374%28v=vs.85%29.aspx BITMAPFILEHEADER]
+
* Defined in the [https://www.aelius.com/njh/wavemetatools/doc/riffmci.pdf RIFF specification] (as Device Independent Bitmap File Format)
−
* [http://msdn.microsoft.com/en-us/library/dd183372%28v=vs.85%29.aspx BITMAPCOREHEADER]
+
* [https://docs.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-bitmapfileheader BITMAPFILEHEADER]
−
* [http://msdn.microsoft.com/en-us/library/dd183376%28v=vs.85%29.aspx BITMAPINFOHEADER]
+
* [https://docs.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-bitmapcoreheader BITMAPCOREHEADER]
−
* [http://msdn.microsoft.com/en-us/library/aa452885.aspx BITMAPINFOHEADER (Windows CE 5.0)]
+
* [https://docs.microsoft.com/en-us/previous-versions/dd183376(v=vs.85) BITMAPINFOHEADER]
−
* [http://msdn.microsoft.com/en-us/library/dd183380%28v=vs.85%29.aspx BITMAPV4HEADER]
+
* [https://docs.microsoft.com/en-us/previous-versions/windows/embedded/aa452885(v=msdn.10) BITMAPINFOHEADER (Windows CE 5.0)]
−
* [http://msdn.microsoft.com/en-us/library/dd183381%28v=vs.85%29.aspx BITMAPV5HEADER]
+
* [https://docs.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-bitmapv4header BITMAPV4HEADER]
 +
* [https://docs.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-bitmapv5header BITMAPV5HEADER]
 
* [http://www.digicamsoft.com/bmp/bmp.html Another site with format descriptions]
 
* [http://www.digicamsoft.com/bmp/bmp.html Another site with format descriptions]
 
* [http://www.fileformat.info/format/os2bmp/spec/902d5c253f2a43ada39c2b81034f27fd/view.htm OS/2 Presentation Manager Programming Reference Guide, Vol III]
 
* [http://www.fileformat.info/format/os2bmp/spec/902d5c253f2a43ada39c2b81034f27fd/view.htm OS/2 Presentation Manager Programming Reference Guide, Vol III]
 +
* [http://whatis.rest7.com/how-to-open-bmp-file Specification of BMP headers]
 +
* [http://zig.tgschultz.com/bmp_file_format.txt BMP format information by T. Schultz]
  
 
== Metaformat files ==
 
== Metaformat files ==
  
 
* {{Synalysis|bitmap}}
 
* {{Synalysis|bitmap}}
 +
 +
== Software ==
 +
BMP is widely supported by graphics software, including web browsers. Software listed here has been arbitrarily selected.
 +
* [[Netpbm]]: bmptopnm, ppmtobmp
 +
* [[ImageMagick]]
 +
* [[XnView]]
 +
* [[Tom's Viewer]]
 +
* {{Reggae}}
  
 
== Sample files ==
 
== Sample files ==
 
=== Windows BMP v2 ===
 
=== Windows BMP v2 ===
 
This format is fairly common, but examples of it can be hard to spot amidst all the BMPv3 files.
 
This format is fairly common, but examples of it can be hard to spot amidst all the BMPv3 files.
−
* [http://samples.libav.org/image-samples/money-2-%28os2%29.bmp money-2-(os2).bmp], [http://samples.libav.org/image-samples/money-16-%28os2%29.bmp money-16-(os2).bmp], [http://samples.libav.org/image-samples/money-256-%28os2%29.bmp money-256-(os2).bmp], [http://samples.libav.org/image-samples/money-24bit-os2.bmp money-24bit-os2.bmp]
+
* [https://samples.libav.org/image-samples/money-2-%28os2%29.bmp money-2-(os2).bmp], [https://samples.libav.org/image-samples/money-16-%28os2%29.bmp money-16-(os2).bmp], [https://samples.libav.org/image-samples/money-256-%28os2%29.bmp money-256-(os2).bmp], [https://samples.libav.org/image-samples/money-24bit-os2.bmp money-24bit-os2.bmp]
−
* http://cd.textfiles.com/hobbesos29709/disk2/MULTIMED/BMP/ → BMPS*.ZIP, OS2ORBIT.ZIP, REALMERL.BMP
+
* {{CdTextfilesURL|hobbesos29709/disk2/MULTIMED/BMP/}} → BMPS*.ZIP, OS2ORBIT.ZIP, REALMERL.BMP
  
 
=== Windows BMP v3 ===
 
=== Windows BMP v3 ===
−
* http://cd.textfiles.com/mmplatinum/IMAGES/BMP/
+
* {{CdTextfilesURL|mmplatinum/IMAGES/BMP/}}
−
* http://cd.textfiles.com/monstmedia/WIN/ICONS/
+
* {{CdTextfilesURL|monstmedia/WIN/ICONS/}}
−
* http://cd.textfiles.com/maxx/tothemaxww/BMPMISC/
+
* {{CdTextfilesURL|maxx/tothemaxww/BMPMISC/}}
  
 
=== OS/2 BMP 2.0 ===
 
=== OS/2 BMP 2.0 ===
 
* [http://kimludvigsen.dk/os2/os2/graphx/teamlog2.zip teamlog2.zip] → TEAMcol.bmp, teamcol2.bmp
 
* [http://kimludvigsen.dk/os2/os2/graphx/teamlog2.zip teamlog2.zip] → TEAMcol.bmp, teamcol2.bmp
−
* [http://samples.libav.org/image-samples/bmp-files/test4os2v2.bmp test4os2v2.bmp]
+
* [https://samples.libav.org/image-samples/bmp-files/test4os2v2.bmp test4os2v2.bmp]
−
* [http://cd.textfiles.com/hobbesos29709/disk2/MULTIMED/BMP/CARDBMPS.ZIP CARDBMPS.ZIP] - Most of the files are OS/2 BMP 2.0
+
* {{CdTextfiles|hobbesos29709/disk2/MULTIMED/BMP/CARDBMPS.ZIP|CARDBMPS.ZIP}} - Most of the files are OS/2 BMP 2.0
−
* [http://cd.textfiles.com/hobbesos29709/disk1/GAMES/MAKMAN10.ZIP MAKMAN10.ZIP] - Some of the files are files OS/2 BMP 2.0
+
* {{CdTextfiles|hobbesos29709/disk1/GAMES/MAKMAN10.ZIP|MAKMAN10.ZIP}} - Some of the files are files OS/2 BMP 2.0
−
* [http://cd.textfiles.com/monstmedia/IMAGES/JUR_OS2.BMP JUR_OS2.BMP]
+
* {{CdTextfiles|monstmedia/IMAGES/JUR_OS2.BMP|JUR_OS2.BMP}}
−
* http://cd.textfiles.com/pier/pier09/cdrom/036/ → os2bmp*.zip
+
* {{CdTextfilesURL|pier/pier09/cdrom/036/}} → os2bmp*.zip
  
 
=== Various ===
 
=== Various ===
 
* [http://wvnvms.wvnet.edu/vmswww/bmp.html Example BMP images (all Windows v3 except as indicated)]
 
* [http://wvnvms.wvnet.edu/vmswww/bmp.html Example BMP images (all Windows v3 except as indicated)]
−
* [http://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html BMP Suite Image List]
+
* [https://archive.org/details/OS2BBS OS/2 BBS Files Archive] → 13-Bitmap.zip - Lots of OS/2 BMP 1.0 & 2.0 files
 +
* [https://entropymine.com/jason/bmpsuite/bmpsuite/html/bmpsuite.html BMP Suite Image List]
 +
* {{DexvertSamples|image/bmp}}
  
 
== See also ==
 
== See also ==
 
* [[CUR]]
 
* [[CUR]]
 
* [[ICO]]
 
* [[ICO]]
 +
* [[KQP]]
 
* [[OS/2 bitmap family]]
 
* [[OS/2 bitmap family]]
 
* [[OS/2 Bitmap Array]]
 
* [[OS/2 Bitmap Array]]
 
* [[packPNM]]
 
* [[packPNM]]
 +
* [[Pegasus PIC]]
 
* [[Pocket PC Bitmap]]
 
* [[Pocket PC Bitmap]]
 
* [[Poser Bump Map]]
 
* [[Poser Bump Map]]
Line 203: Line 259:
 
* [[Windows DDB]]
 
* [[Windows DDB]]
 
* [[Winzle Puzzle]]
 
* [[Winzle Puzzle]]
 +
* BMP is sometimes used as a base format for [[steganography]] and similar things. For examples, see:
 +
** [[Data Hiding/Embedding#BMP]]
 +
** [[Encryption#Obfuscation]]
 +
** [[Encryption#Steganography]]
  
−
== Resources ==
+
== Links ==
 
* [[Wikipedia:BMP file format|Wikipedia: BMP file format]]
 
* [[Wikipedia:BMP file format|Wikipedia: BMP file format]]
 
* {{EGFF|bmp|Microsoft Windows Bitmap File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]
 
* {{EGFF|bmp|Microsoft Windows Bitmap File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]
 
* {{EGFF|os2bmp|OS/2 Bitmap File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]
 
* {{EGFF|os2bmp|OS/2 Bitmap File Format Summary}}, from the [[Encyclopedia of Graphics File Formats]]
 
* [http://coptr.digipres.org/Bad_Peggy Bad Peggy: scans images for problems]
 
* [http://coptr.digipres.org/Bad_Peggy Bad Peggy: scans images for problems]
 +
* [https://web.archive.org/web/20190919034602/http://forensicswiki.org/wiki/BMP ForensicsWiki entry] (not much useful info except for a link to an iOS tool for reading metadata)
 +
* [https://github.com/corkami/pics/blob/master/binary/BMP.png Graphic documenting format]
  
 
[[Category:Microsoft]]
 
[[Category:Microsoft]]
 +
[[Category:Windows]]
 
[[Category:OS/2]]
 
[[Category:OS/2]]

Latest revision as of 04:20, 28 December 2023

File Format
Name BMP
Ontology
Extension(s) .bmp, .rle, .dib, others
MIME Type(s) image/bmp
LoCFDD fdd000189
PRONOM fmt/116, others
Wikidata ID Q192869
Kaitai Struct Spec bmp.ksy
Released 1987

BMP is a family of raster image file formats primarily used on Microsoft Windows and OS/2 operating systems. The format is sometimes known as Device-Independent Bitmap (DIB), since, when loaded into memory using Windows software, the image is held as a DIB structure.

Though seemingly a simple format, it is complicated by its many different versions, lack of an official specification, lack of any version control process, and ambiguities and contradictions in the documentation.

Contents

[edit] Discussion

The term DIB can mean several different things:

  • A synonym for BMP file format.
  • An in-memory DIB object, with no file header. The header data and the bitmap data do not have to be stored contiguously. Some Win32 API functions use this format.
  • A "packed DIB" memory object or file component, with no file header. The header data and the bitmap data are stored contiguously. This is a standard clipboard format, for example.
  • A "packed DIB" stored in a file by itself.

A number of Windows-centric formats contain some nonstandard modified or compressed form of BMP/DIB, intended to be reconstructed as a DIB at runtime.

[edit] Format details

[edit] Compression

Images are usually uncompressed, but RLE compression can be used under some conditions. JPEG, PNG, and Huffman 1D compression are also theoretically possible, but rarely supported.

[edit] File structure

A BMP file starts with a 14-byte "BITMAPFILEHEADER" structure.

Immediately after that is another header which we'll refer to as the "info header", though some versions of it are named "core header" instead. There are a number of different versions and sub-versions of it. It starts with 4-byte integer indicating its size, which mostly reveals its version.

The pixel data is pointed to by a field in BITMAPFILEHEADER. There can be other data segments, e.g. for a color palette, before (and, rarely, after) the pixel data.

Pixel data is usually stored from bottom up (but is top-down if the header indicates a negative height). If uncompressed, each row is padded to a multiple of 4 bytes.

[edit] Identifiers

No MIME type has been officially registered. Strings found in practice are: image/bmp; image/x-bmp; image/x-ms-bmp

The usual filename extension is .bmp. Extensions .rle (for RLE-compressed images) and .dib (which sometimes indicates that the file lacks a file header) are also sometimes seen. Many other extensions have been used by various applications.

[edit] Identification

BMP files start with the ASCII signature "BM".

The bytes at the beginning of the file match one of these two patterns: 

42 4d ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 00 00 0c 00 
00 00 ?? ?? ?? ?? 01 00 ?? 00

or 

42 4d ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? 00 00 ?? 00 
00 00 ?? ?? ?? ?? ?? ?? ?? ?? 01 00 ?? 00

The "reserved" bytes at offset 6 to 9 are usually all zero, but a few OS/2 BMP files have nonzero "hotspot coordinates" there.

Compare to VBM (VDC BitMap), an obscure format with a similar signature.

[edit] Well-known versions

[edit] Windows BMP v2

  • Info header size: 12
  • Info header name: BITMAPCOREHEADER
  • PRONOM: fmt/115

See also OS/2 BMP 1.0, below.

[edit] Windows BMP v3

  • Info header size: 40
  • Info header name: BITMAPINFOHEADER
  • PRONOM: fmt/116, fmt/117

This is by far the most widely used version of BMP. It was introduced with Windows 3.x. Windows NT extended it to support 16 and 32 bits/pixel.

Windows CE also extended it, for example to allow 2 bits/pixel (see Pocket PC Bitmap), but its extensions were not migrated to the BMP v4 and v5 formats.

Microsoft's GDI+ reportedly supports BMP images with 64 bits/pixel[1], but no technical documentation of this extension has been located.

It is apparently possible for OS/2 BMP 2.0 format to masquerade as Windows BMP v3. The upshot is that if the compression type is 3 and the bit depth is 1, or the compression type is 4 and the bit depth is 24, then the file should be treated as OS/2 BMP 2.0.

[edit] Windows BMP v4

  • Info header size: 108
  • Info header name: BITMAPV4HEADER
  • PRONOM: fmt/118

Introduced with Windows 95. Adds support for transparency and colorimetry.

[edit] Windows BMP v5

  • Info header size: 124
  • Info header name: BITMAPV5HEADER
  • PRONOM: fmt/119

Introduced with Windows 98. Adds support for ICC profiles.

[edit] Other versions

[edit] Windows BMP v1

Also called DDB, this is the bitmap file format used by Windows 1.0. It's not really a BMP format. Refer to Windows DDB.

[edit] OS/2 BMP 1.0

See also the OS/2 BMP disambiguation page.
  • Info header size: 12
  • Info header name: BITMAPCOREHEADER or OS21XBITMAPHEADER
  • PRONOM: x-fmt/25 (deprecated), fmt/115

For practical purposes, OS/2 BMP 1.0 is identical to Windows BMP v2. But there can be at least one small difference: In OS/2 formats, the "Size" field at offset 2 (variously named "cbSize", "FileSize", or "bfSize") is sometimes set to the size of the headers, instead of the size of the file. For v1, that means it will be 26 (14+12). For v2, it can range from 30 to 78.

[edit] OS/2 BMP 2.0

  • Info header size: 16–64 (16, 24, 40, 48, and 64 may be most common)
  • Info header name: BITMAPCOREHEADER2 or OS22XBITMAPHEADER
  • PRONOM: x-fmt/270

OS/2 BMP 2.0 defines several file subtypes; here we are describing only the "Bitmap" subtype (files with a signature of "BM"). For other subtypes, see OS/2 bitmap family.

The header size can be reduced from its full size of 64 bytes. Omitted fields are assumed to have a value of zero.

The fields in the first 40 bytes of the header are (nearly) identical to those in Windows BMP v3, v4, and v5. The remaining fields are different.

OS/2 BMP 2.0 supports compression types "Huffman 1D" and "RLE24", unlike any other version of BMP.

[edit] BITMAPV2INFOHEADER

  • Info header size: 52
  • Info header name: BITMAPV2INFOHEADER

Uncertain; possibly an abbreviated V4/V5 header.

[edit] BITMAPV3INFOHEADER

  • Info header size: 56
  • Info header name: BITMAPV3INFOHEADER

Uncertain; possibly an abbreviated V4/V5 header.

[edit] Packed DIB file

Same as the common BMP formats, but omits the 14-byte file header.

[edit] OS/2 Bitmap Array

Sometimes, an OS/2 Bitmap Array file containing one or more bitmaps is considered to be a kind of BMP file. Such a file begins with an extra 14-byte header, with signature "BA". (But note that deleting this header is not quite enough to get a valid BMP file.)

[edit] Symbol definitions

Here are the definitions, from the Windows SDKs, of some of the symbols used in the BMP documentation.

All integers use little-endian byte order.

Symbol Definition
WORD unsigned 16-bit integer
DWORD unsigned 32-bit integer
LONG signed 32-bit integer
BI_RGB 0
BI_RLE8 1
BI_RLE4 2
BI_BITFIELDS 3
(Huffman 1D) 3
BI_JPEG 4
(24-bit RLE) 4
BI_PNG 5
BI_ALPHABITFIELDS 6
BI_SRCPREROTATE 0x8000 (?)
LCS_CALIBRATED_RGB 0
LCS_sRGB 'sRGB' = 0x73524742
LCS_WINDOWS_COLOR_SPACE 'Win ' = 0x57696e20
PROFILE_LINKED 'LINK' = 0x4c494e4b
PROFILE_EMBEDDED 'MBED' = 0x4d424544
LCS_GM_BUSINESS 1
LCS_GM_GRAPHICS 2
LCS_GM_IMAGES 4
LCS_GM_ABS_COLORIMETRIC 8

[edit] Specifications

[edit] Metaformat files

[edit] Software

BMP is widely supported by graphics software, including web browsers. Software listed here has been arbitrarily selected.

[edit] Sample files

[edit] Windows BMP v2

This format is fairly common, but examples of it can be hard to spot amidst all the BMPv3 files.

[edit] Windows BMP v3

[edit] OS/2 BMP 2.0

[edit] Various

[edit] See also

[edit] Links

Retrieved from "http://fileformats.archiveteam.org/index.php?title=BMP&oldid=47266"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox