Free webp to jpg
Image MIME Reference
CMU-Raster

CMU Window Manager Raster

image/x-cmu-raster
VS

Adobe Digital Negative

image/x-adobe-dng
DNG

A complete technical comparison of CMU Window Manager Raster and Adobe Digital Negative — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature CMU-Raster DNG
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
CMU Window Manager Raster
image/x-cmu-raster
Extension
.ras
Container CMU Window Manager Bitmap
Compression Uncompressed
Algorithm
None
Color Depth 1-bit (Monochrome), 8-bit (Indexed/Grayscale)
Developed by Carnegie Mellon University (CMU)
Released 1980s
Magic Bytes
F1 00 40 BB
Full CMU-Raster reference →
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 →

Browser Support Comparison

Browser CMU-Raster DNG
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
CMU-Raster

CMU-Raster Strengths

  • Incredibly simple, uncompressed binary structure that was easy for early, memory-constrained UNIX workstations to parse and render
Limitations
  • Completely obsolete and unsupported outside of niche historical command-line tools like Netpbm
  • The shared '.ras' file extension causes frequent file misidentification and system conflicts
  • Lacks all modern imaging features, including metadata, compression, and alpha channel transparency
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

When to choose which format

CMU-Raster
Use CMU-Raster when…
  • Historical UNIX / Andrew Project Archival
  • Legacy Academic Computing Research
DNG
Use DNG when…
  • Digital Photography Archival
  • Mobile Raw Capture (iOS ProRAW / Android Camera2 API)
  • Cross-Platform Raw Editing Workflows
Share this comparison