BMP

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Sample files)
(add ForensicsWiki entry link (no useful details to add))
 
Line 259: Line 259:
 
* {{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]
 +
 +
== Links ==
 +
* [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)
  
 
[[Category:Microsoft]]
 
[[Category:Microsoft]]
 
[[Category:Windows]]
 
[[Category:Windows]]
 
[[Category:OS/2]]
 
[[Category:OS/2]]

Latest revision as of 01:06, 26 October 2020

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. 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.

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] Resources

[edit] Links

  • ForensicsWiki entry (not much useful info except for a link to an iOS tool for reading metadata)
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox