Free webp to jpg
Image MIME Reference
DNG

Adobe Digital Negative

image/x-adobe-dng
VS

X Bitmap (Legacy MIME Alias)

image/x-xbm
XBM

A complete technical comparison of Adobe Digital Negative and X Bitmap (Legacy MIME Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature DNG XBM
Transparency (Alpha) Yes Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
Adobe Digital Negative
image/x-adobe-dng
Extension
.dng
Container TIFF/EP
Compression Lossless JPEG / Deflate / Lossy JPEG (DNG 1.4+)
Algorithm
Lossless JPEG (Standard)Lossy JPEG (Compression option)Uncompressed
Color Depth 12-bit, 14-bit, 16-bit, 32-bit (Floating Point HDR)
Developed by Adobe Systems
Released 2004
Magic Bytes
49 49 2A 00 or 4D 4D 00 2A
Full DNG reference →
X Bitmap (Legacy MIME Alias)
image/x-xbm
Extension
.xbm
Container C Source Code Header (.h)
Compression Uncompressed (Source Code)
Algorithm
None
Color Depth 1-bit (Monochrome)
Developed by MIT / X Consortium (X Window System)
Released 1988
Magic Bytes
23 64 65 66 69 6e 65 (ASCII '#define')
Full XBM reference →

Browser Support Comparison

Browser DNG XBM
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
DNG

DNG Strengths

  • Openly documented specification guarantees long-term archival accessibility, freeing photographers from proprietary manufacturer lock-in
  • Lossless compression algorithms often result in files 15-20% smaller than uncompressed proprietary raw formats
  • Natively supported by modern smartphone operating systems (iOS and Android) for high-end mobile photography
Limitations
  • Conversion from proprietary raw to DNG takes processing time and can strip specific, proprietary manufacturer metadata (like active D-Lighting or in-camera lens corrections)
  • File sizes are massive compared to standard JPEGs or HEIC files
  • Cannot be rendered natively in web browsers without server-side processing or WebAssembly decoders
XBM

XBM Strengths

  • Can be compiled directly into C or C++ source code without needing an external file loader or binary asset manager
  • Human-readable structure allows developers to inspect, edit, or hand-craft tiny icons directly within a text editor
  • Extremely predictable and lightweight for 1-bit hardware displays and embedded systems
Limitations
  • Strictly limited to 1-bit monochrome (black and white) graphics with no gray or color support
  • Text-based C syntax creates massive file bloat compared to binary 1-bit formats like PBM
  • Completely deprecated in modern web browsers and desktop GUI frameworks

When to choose which format

DNG
Use DNG when…
  • Digital Photography Archival
  • Mobile Raw Capture (iOS ProRAW / Android Camera2 API)
  • Cross-Platform Raw Editing Workflows
XBM
Use XBM when…
  • X Window System (X11) Cursors and Icons
  • Embedded C/C++ Firmware UI Assets
  • Early 1990s Unix Web Graphics
Share this comparison