Image MIME Reference
HEJ2K
JPEG 2000 Image (HEIF Container)
image/hej2k
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of JPEG 2000 Image (HEIF Container) 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 | HEJ2K | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | Yes |
| HDR Support | Yes | Yes |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG 2000 Image (HEIF Container)
image/hej2k
Extension
.hej2
Container
HEIF / ISOBMFF (ISO/IEC 15444-16)
Compression
Lossy / Lossless
Algorithm
JPEG 2000HTJ2K
Color Depth
8-bit, 10-bit, 12-bit, 16-bit
Developed by
ISO/IEC JTC 1 / ITU-T
Released
2019
Magic Bytes
XX XX XX XX 66 74 79 70 6A 32 6B 69
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 | HEJ2K | HTJ2K-Codestream |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
HEJ2K
HEJ2K Strengths
- Brings the extensive capabilities of the HEIF container (like EXIF/XMP, thumbnails, and depth maps) to JPEG 2000
- Supports mathematically lossless compression via wavelet transformation
- High scalability and progressive decoding out of the box
Limitations
- Extremely limited software support outside of niche industries
- Zero native compatibility with web browsers
- High computational complexity compared to simpler formats like JPEG or PNG
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
HEJ2K
Use HEJ2K when…
- Medical Imaging
- Geospatial Data
- Scientific Archiving
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems