This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| DIB (Device Independent Bitmap) | |
|---|---|
| Name | Device Independent Bitmap |
| Extension | .bmp, .dib |
| Mime | image/bmp |
| Owner | Microsoft |
| Released | 1980s |
| Genre | Raster graphics file format |
| Containerfor | Bitmap images |
DIB (Device Independent Bitmap) is a raster graphics file format specification used to store bitmap digital images, developed to enable consistent image representation across different hardware and software environments. It defines pixel storage, color depth, palettes, and optional compression to allow interchange among systems and applications. DIB underpins several widely used file extensions and APIs, and has influenced imaging support in major operating systems, frameworks, and multimedia applications.
The DIB specification originated with Microsoft and IBM efforts to standardize bitmap storage for the Windows family and related environments, enabling interoperability between Windows NT, MS-DOS, OS/2, and later Windows 95 and Windows 98 iterations. It serves as the basis for the BMP file format used by programs such as Microsoft Paint, Adobe Photoshop, GIMP, and image-handling libraries in Qt, GTK, and Java toolkits. Vendors like Intel, NVIDIA, AMD and device manufacturers for printers and displays have relied on DIB semantics for driver development and raster output in environments including Microsoft DirectX, OpenGL, and X Window System integrations.
A DIB encodes an image using a header that specifies dimensions, bit count, compression type, and color usage, followed by a palette table and pixel array. Headers derive from structures used in Windows API definitions, aligning with data types found in Win32 API and WINDDI specifications implemented by vendors such as Hewlett-Packard and Canon Inc.. The layout is consumed by applications like Microsoft Office suites, LibreOffice, CorelDRAW, and system components such as Windows Shell thumbnailing. Variants of the header, including BITMAPINFOHEADER and BITMAPV*, are referenced in documentation for Visual Studio compilers, GCC ports on MinGW, and cross-platform toolchains maintained by contributors from Red Hat, Debian, and OpenBSD projects.
DIB supports multiple color depths (1, 4, 8, 16, 24, 32 bits per pixel) and palette-driven modes; palettes are often represented as arrays of RGBQUAD entries compatible with Microsoft Visual C++, Borland graphics libraries, and imaging filters used by Adobe Systems products. High-color and true-color modes map to color models used by sRGB, Adobe RGB, and hardware color spaces documented by IEC standards; color management integrations appear in ICC profile workflows, imaging pipelines in Apple Inc. macOS components, and enterprise solutions by IBM and Sun Microsystems. Palette manipulation and dithering techniques have been implemented in tools like ImageMagick, IrfanView, and Paint.NET.
Although many DIB images are uncompressed, the format accommodates compression methods such as BI_RGB (uncompressed), BI_RLE8, BI_RLE4, and BI_BITFIELDS for mask-based color channel definitions. These variants are referenced in driver and codec specifications for Microsoft DirectShow, FFmpeg, and Windows Media frameworks, and affect interoperability with encoders developed by Xiph.Org Foundation and proprietary solutions from Apple QuickTime or RealNetworks. Some extensions allow alpha channels and premultiplied alpha handling that intersect with formats used by Portable Network Graphics and compositing in Adobe After Effects and Blender pipelines.
DIBs are natively supported by the Windows GDI and GDI+ graphics subsystems, accessible through APIs in Win32, .NET Framework, and UWP (Universal Windows Platform). Cross-platform libraries such as libpng-adjacent image handlers, SDL, and wxWidgets include translation layers between DIBs and platform-native bitmaps used by X.Org Server or Wayland. Device drivers for printers and displays from Epson, Brother Industries, and Samsung Electronics implement conversions to and from DIB structures when integrating with APIs like Printer Command Language or PCL-based workflows.
DIB-based files are used in desktop publishing tools such as Microsoft Publisher, Scribus, and multimedia authoring suites like Adobe Premiere Pro for frame-level raster assets. Their simple, low-overhead structure makes them suitable for screenshots, icons, and intermediate image processing in pipelines for OpenCV and machine vision systems in research institutions including MIT, Stanford University, and ETH Zurich. Limitations include large file sizes for high-resolution true-color images, lack of advanced metadata support found in JPEG EXIF or TIFF tag systems, and weaker compression compared to JPEG or HEIF—constraints noted by organizations including ISO and IETF when evaluating imaging standards.
The DIB concept emerged during the 1980s as part of Microsoft and IBM collaborations to unify bitmap semantics for PC DOS and MS-DOS utilities and the early Windows 1.0 through Windows 3.1x era. Subsequent refinements accompanied releases of Windows NT, integration into OLE object embedding, and adoption by graphics software vendors including Aldus, Corel Corporation, and Adobe Systems. Over time, contributions and de facto standards from projects such as Wine, ReactOS, and open-source imaging libraries expanded platform support and interoperability, while academic and industry publications from IEEE conferences analyzed color handling, compression trade-offs, and archival implications for digital preservation in cultural institutions like the Library of Congress.
Category:Raster graphics file formats