Image MIME Reference
DNG
Adobe Digital Negative
image/x-adobe-dng
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of Adobe Digital Negative and High-Throughput JPEG 2000 Codestream — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | DNG | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | Yes |
| 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
High-Throughput JPEG 2000 Codestream
image/jphc
Extension
.jhc
Container
None (Raw Codestream)
Compression
Lossy / Lossless
Algorithm
High-Throughput JPEG 2000 (HTJ2K)
Color Depth
8-bit, 16-bit, 32-bit, 38-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2019
Magic Bytes
FF 4F FF 51
Browser Support Comparison
| Browser | DNG | HTJ2K-Codestream |
|---|---|---|
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
HTJ2K-Codestream
HTJ2K-Codestream Strengths
- Extremely fast encoding and decoding capabilities due to the parallelizable block coder
- Minimal file overhead since it lacks container headers and metadata
- Ideal for streaming applications or embedded systems where parsing a full container is unnecessary
Limitations
- Lacks standard metadata support (like EXIF, XMP, or ICC color profiles) since there is no container structure
- Zero native web browser compatibility
- Difficult to distinguish from standard JPEG 2000 codestreams without deeply parsing the internal marker segments
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
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems