XBM Format Guide

Available Conversions

Convert to XBM

About XBM Format

XBM (X BitMap) is a monochrome bitmap image format created in 1985 by MIT and the X Consortium for the X Window System (X11), the standard graphical display framework for Unix and Linux systems. Unlike virtually all other image formats, XBM files are stored as plain C source code containing static arrays of unsigned character data that define bitmap pixel patterns. Each file declares width and height constants using #define preprocessor directives, followed by a static array of hexadecimal byte values representing the pixel data in row-major order, where each bit corresponds to a single pixel (1 = foreground, 0 = background). This unique text-based representation means XBM files can be directly #included in C and C++ programs and compiled as part of the application binary, eliminating the need for runtime file parsing or external image loading libraries. The format is strictly 1-bit monochrome, supporting only two colors (typically black and white), with no grayscale, color channels, or alpha transparency. XBM files use the .xbm file extension and have no magic number or binary header, as they are valid C source code that begins with #define statements.

History of XBM

The XBM format was introduced in 1985 as part of the X Window System (X11) developed at MIT's Project Athena, a joint project between MIT, Digital Equipment Corporation (DEC), and IBM to create a platform-independent graphical windowing system for networked computing. The format was designed to provide a simple, portable way to define bitmap patterns for window manager icons, mouse cursors, background tile patterns, and toolbar button graphics used throughout X11 desktop environments and applications. Because Unix systems of the 1980s had limited graphical editing tools and X11 applications were written primarily in C, the decision to store bitmaps as C source code was both practical and elegant: developers could create and modify icons using any text editor, and the bitmaps would be compiled directly into the application without requiring separate file I/O routines or image parsing libraries. The format became deeply embedded in the X11 ecosystem, with tools like bitmap(1) providing a simple GUI editor for creating and modifying XBM files, and xsetroot using XBM patterns for desktop backgrounds. Major X11 toolkits including Xt (X Toolkit Intrinsics), Motif, and later Gtk+ and Qt all provided native XBM loading support. When the XPM (X PixMap) format was introduced in 1989 by Groupe Bull, it extended the XBM concept to support color images using a similar C source code representation, but XBM remained the standard for monochrome bitmaps. The format continued to be used throughout the 1990s and 2000s in X11 window managers, desktop environments like CDE (Common Desktop Environment), and embedded Linux systems. Today, XBM files are still encountered in legacy X11 applications, retro computing projects, embedded systems with monochrome displays, and educational contexts where the human-readable format serves as an excellent introduction to bitmap image representation.

Key Features and Uses

XBM files use a distinctive text-based structure that is valid C source code. A typical XBM file begins with two #define lines specifying the image width and height in pixels, optionally followed by #define lines for a hotspot position (x_hot and y_hot) when the bitmap is used as a cursor. The pixel data is stored in a static array of unsigned char values written in hexadecimal notation (e.g., 0xff, 0x00), where each byte contains 8 pixels with the least significant bit (LSB) representing the leftmost pixel in that group. Rows are padded to byte boundaries, so a 12-pixel-wide image uses 2 bytes per row with the upper 4 bits of the second byte unused. The foreground color (bit value 1) and background color (bit value 0) are determined by the application at display time, not stored in the file, which means the same XBM bitmap can be rendered in any two-color combination. This 1-bit-per-pixel encoding produces extremely compact data for small icons: a typical 16x16 cursor requires only 32 bytes of pixel data. The C source code format also makes XBM files trivially diffable in version control systems, as changes to individual pixels appear as modified hexadecimal values in specific array positions. XBM files can be read and written by Pillow (Python), ImageMagick, GIMP, XnView, and the X11 bitmap editor, and are natively supported by all X Window System implementations including X.Org and XFree86.

Common Applications

XBM files have historically been used for X Window System icons, mouse cursors, bitmap patterns, and user interface elements in Unix and Linux graphical applications. In X11 window managers such as twm, fvwm, Openbox, and IceWM, XBM bitmaps define window titlebar buttons (close, minimize, maximize), menu icons, and window decoration patterns. The xsetroot utility uses XBM files to set desktop background tile patterns, and the xterm terminal emulator supports custom XBM icons. Mouse cursors in X11 are traditionally defined using pairs of XBM files: one for the cursor shape and one for the cursor mask, which together specify which pixels are visible and their foreground/background colors. In embedded systems and microcontroller projects, XBM format is popular for storing monochrome graphics for OLED and LCD displays because the C array format can be directly included in firmware source code without any image decoding library, making it ideal for resource-constrained devices like Arduino, ESP32, and Raspberry Pi Pico projects. The format is also used in retro computing and pixel art communities, where the 1-bit limitation is embraced as an artistic constraint. Converting XBM files to modern formats like PNG or BMP is common when migrating legacy X11 applications to modern toolkits, extracting icons from vintage Unix software, or preparing monochrome bitmap assets for web display. Converting images to XBM format is useful when creating custom X11 cursors and icons, preparing monochrome graphics for embedded displays, or generating C-includable bitmap data for firmware development.

Advantages and Disadvantages