Image MIME Reference
DNG
Adobe Digital Negative
image/x-adobe-dng
VS
Portable Graymap
image/x-portable-graymap
PGM
A complete technical comparison of Adobe Digital Negative and Portable Graymap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | DNG | PGM |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | Yes |
| 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
Portable Graymap
image/x-portable-graymap
Extension
.pgm
Container
Netpbm
Compression
Uncompressed
Algorithm
None
Color Depth
8-bit (Grayscale), 16-bit (Grayscale)
Developed by
Jef Poskanzer (Netpbm Project)
Released
1988
Magic Bytes
50 32 (ASCII) or 50 35 (Binary)
Browser Support Comparison
| Browser | DNG | PGM |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
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
PGM
PGM Strengths
- Extremely simple format allows custom parsers to be written from scratch in minimal time
- Supports 16-bit precision, making it highly valuable for scientific, medical, and height-map data where 8-bit precision is insufficient
- ASCII encoding ('P2') allows manual editing and visual inspection of pixel values directly within a text editor
Limitations
- Strictly limited to grayscale; cannot display color
- Lack of compression results in massive file sizes, making it entirely impractical for web delivery or consumer storage
- Does not support alpha transparency or modern metadata structures
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
PGM
Use PGM when…
- Computer Vision and Machine Learning Pre-processing
- Scientific and Medical Image Processing
- Unix/Linux Command-Line Image Pipelines