{"id":3266,"date":"2026-08-08T02:04:42","date_gmt":"2026-08-07T23:04:42","guid":{"rendered":"https:\/\/picajet.com\/articles\/formats\/bmp\/"},"modified":"2026-08-08T03:51:27","modified_gmt":"2026-08-08T00:51:27","slug":"bmp","status":"publish","type":"format","link":"https:\/\/picajet.com\/articles\/formats\/bmp\/","title":{"rendered":"BMP"},"content":{"rendered":"<p class=\"wp-block-paragraph\">BMP solved a narrow, early problem: Microsoft and IBM needed a simple, guaranteed-decodable raster format baked directly into the Windows GDI and OS\/2 Presentation Manager, so any application could read and write bitmaps without licensing a codec. The original 12-byte header shipped with Windows 2.0 in 1987 and was reused in OS\/2 1.1 the following year; the larger BITMAPINFOHEADER most BMP files use today \u2014 with 16\/32-bit color and optional RLE compression \u2014 arrived with Windows 3.0 in 1990.<\/p><p class=\"wp-block-paragraph\">BMP predates every modern metadata standard \u2014 EXIF didn&#8217;t exist until 1994, XMP until 2001 \u2014 which is exactly why it never gained real support for either. In a DAM, BMP typically appears only as a legacy ingest artifact: old scans, screen captures, or output from older scientific or industrial imaging equipment. Thumbnailing is trivial since there&#8217;s no compression to decode, but there is effectively nothing to extract from the file itself for search indexing.<\/p><p class=\"wp-block-paragraph\">The practical DAM policy is straightforward: normalize any incoming BMP to TIFF or PNG immediately on ingest. This both shrinks the file (BMP&#8217;s default uncompressed storage is wasteful) and gives the asset a real chance at carrying metadata going forward, since BMP&#8217;s rare ICC-capable header variant (BITMAPV5HEADER) is almost never actually used by the software producing BMP files in the wild.<\/p>","protected":false},"excerpt":{"rendered":"<p>An uncompressed (or lightly RLE-compressed) Windows-native raster format with no meaningful metadata support, retained mainly for legacy compatibility.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Should a DAM use BMP as a master or preservation format?","answer":"No. Uncompressed BMP wastes storage with no compensating benefit \u2014 it has no meaningful metadata capacity and essentially no color-management adoption in practice. Convert incoming BMPs to TIFF on ingest."},{"question":"Does BMP support EXIF, IPTC, or XMP metadata?","answer":"No. There is no EXIF, IPTC, or XMP support at all in BMP; ICC profile embedding exists only in the rarely-used BITMAPV5HEADER variant, and ExifTool lists BMP as read-only, confirming it cannot meaningfully carry DAM metadata."},{"question":"Why does BMP lack modern metadata support?","answer":"BMP predates every modern metadata standard \u2014 EXIF didn't exist until 1994 and XMP until 2001 \u2014 which is exactly why the format never gained real support for either."},{"question":"Is a BMP file compressed?","answer":"BMP is stored uncompressed by default. Optional 4-bit or 8-bit RLE compression is available only for palette (indexed) images; 16-, 24-, and 32-bit true-color images are always uncompressed or bitfield-encoded."},{"question":"Where does BMP typically show up in a DAM today?","answer":"Almost always as a legacy ingest artifact \u2014 old scans, screen captures, or output from older scientific or industrial imaging equipment \u2014 rather than as a format anyone chooses deliberately."},{"question":"What bit depths does BMP support?","answer":"1, 4, 8, 16, 24, and 32 bits per pixel."},{"question":"What's the recommended DAM ingest policy for BMP files?","answer":"Normalize any incoming BMP to TIFF or PNG immediately on ingest. This shrinks the file and gives the asset a real chance at carrying metadata going forward."},{"question":"Is BMP widely compatible across platforms?","answer":"Yes \u2014 native support has been built into Windows GDI since Windows 3.0, and all major browsers and cross-platform tools (GIMP, Photoshop, IrfanView, ImageMagick) read and write it without issue."}],"checked_date":"2026-08-07","sources":[{"statement":"The original BMP header shipped with Windows 2.0 (1987); OS\/2 1.1 reused it in 1988; the modern BITMAPINFOHEADER arrived with Windows 3.0 in 1990.","source_name":"The Evolution of BMP (Bitmap) Image Formats","url":"https:\/\/www.lsoft.net\/posts\/bmp-image-formats\/","checked":"2026-08-07"},{"statement":"BMP supports optional 4-bit and 8-bit RLE compression for palette images only; true-color images are stored uncompressed or with bitfields.","source_name":"Microsoft Windows Bitmap File Format Summary","url":"https:\/\/www.fileformat.info\/format\/bmp\/egff.htm","checked":"2026-08-07"},{"statement":"ExifTool supports BMP as a read-only format with no metadata write capability.","source_name":"ExifTool supported file types","url":"https:\/\/exiftool.org\/#supported","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"","seo_description":"","noindex":false,"ext":"bmp","full_name":"Windows Bitmap (Device-Independent Bitmap)","vendor_name":"Microsoft Corporation (co-developed with IBM for OS\/2)","introduced":"1987 (Windows 2.0 original header); formalized with BITMAPINFOHEADER in Windows 3.0, 1990","container_notes":"BMP is stored uncompressed by default, with optional 4-bit or 8-bit RLE compression available only for palette (indexed) images; 16-, 24-, and 32-bit true-color images are always uncompressed or bitfield-encoded. It supports 1, 4, 8, 16, 24, and 32 bits per pixel. There is no EXIF, IPTC, or XMP support at all; ICC profile embedding exists only in the rarely-used BITMAPV5HEADER variant, and ExifTool lists BMP as read-only for metadata, confirming it cannot meaningfully carry DAM metadata.","open_with":[{"platform":"macOS","how":"Preview (native)"},{"platform":"Windows","how":"Photos app and Paint (native, built into GDI since Windows 3.0)"},{"platform":"Web browsers","how":"All major browsers render BMP natively via"},{"platform":"Cross-platform","how":"GIMP, Photoshop, IrfanView, ImageMagick all read\/write BMP"}],"archive_advice":"Do not use as a DAM master or preservation format. Uncompressed BMP wastes storage with no compensating benefit \u2014 no meaningful metadata capacity and essentially no color-management adoption in practice. Convert incoming BMPs to TIFF (lossless, with real metadata support) on ingest.","related":[],"tool_link":""},"silo":[23],"class_list":["post-3266","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":1,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3266\/revisions"}],"predecessor-version":[{"id":3683,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/3266\/revisions\/3683"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=3266"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=3266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}