Image MIME Reference
HSJ2
JPEG 2000 Image Sequence (Obsolete)
image/hsj2
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of JPEG 2000 Image Sequence (Obsolete) 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 | HSJ2 | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | Yes | ✕ No |
| Progressive Loading | Yes | Yes |
| HDR Support | Yes | Yes |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG 2000 Image Sequence (Obsolete)
image/hsj2
Extension
.hsj2
Container
HEIF / ISOBMFF (ISO/IEC 15444-16 Obsolete)
Compression
Lossy / Lossless
Algorithm
Motion JPEG 2000 (ISO/IEC 15444-3)
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 68 73 6A 32
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 | HSJ2 | HTJ2K-Codestream |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
HSJ2
HSJ2 Strengths
- Historically attempted to combine Motion JPEG 2000 sequences with the flexible metadata capabilities of the HEIF container
- Supported mathematically lossless compression and scalable wavelet decoding
Limitations
- Officially deprecated by the standardization body (ISO/IEC JTC 1)
- Completely superseded by image/hej2k, rendering hsj2 files obsolete for any new development or archiving
- Zero web browser compatibility and negligible modern software support
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
HSJ2
Use HSJ2 when…
- Legacy Archival
- Deprecated Workflows
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems