Image MIME Reference
CGM
Computer Graphics Metafile
image/cgm
VS
Adobe Digital Negative
image/x-adobe-dng
DNG
A complete technical comparison of Computer Graphics Metafile and Adobe Digital Negative — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | CGM | DNG |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | Yes | Yes |
Computer Graphics Metafile
image/cgm
Extension
.cgm
Container
CGM
Compression
Uncompressed / Binary / Character / Clear Text
Algorithm
Deflate (in some WebCGM profiles)
Color Depth
8-bit, 16-bit, 24-bit, 32-bit
Developed by
ISO / IEC
Released
1987
Magic Bytes
00 20 (Binary) / 42 45 47 49 4E 20 4D 45 54 41 46 49 4C 45 (Clear Text)
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
Browser Support Comparison
| Browser | CGM | DNG |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
CGM
CGM Strengths
- Strictly standardized by ISO, ensuring long-term archiving and cross-platform compatibility in engineering
- Excellent support for rich metadata, hyperlinks, and technical hotspots via the WebCGM profile
- Can store complex 2D geometry, rasters, and text in a single lightweight file
Limitations
- Multiple encoding schemes (Binary, Character, Clear Text) make parser development difficult
- Zero native support in modern web browsers without third-party plugins
- Largely replaced by SVG for general-purpose 2D vector graphics on the web
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
CGM
Use CGM when…
- Technical Illustrations
- Aerospace & Defense (S1000D)
- CAD/CAM
- Geophysics
DNG
Use DNG when…
- Digital Photography Archival
- Mobile Raw Capture (iOS ProRAW / Android Camera2 API)
- Cross-Platform Raw Editing Workflows