Image MIME Reference
HTJ2K-Codestream
High-Throughput JPEG 2000 Codestream
image/jphc
VS
Microsoft Document Imaging
image/vnd.ms-modi
MODI
A complete technical comparison of High-Throughput JPEG 2000 Codestream and Microsoft Document Imaging — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-Codestream | MODI |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
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
Microsoft Document Imaging
image/vnd.ms-modi
Extension
.mdi
Container
TIFF Variant
Compression
LZW / Proprietary MS Compression
Algorithm
LZW (Modified)
Color Depth
1-bit (Monochrome), 8-bit (Grayscale), 24-bit (RGB)
Developed by
Microsoft Corporation
Released
2001
Magic Bytes
49 49 2A 00
Browser Support Comparison
| Browser | HTJ2K-Codestream | MODI |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
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
MODI
MODI Strengths
- Historically provided an excellent all-in-one scanned document format with built-in OCR and annotations before PDF editing became universally accessible
- Tightly integrated with Microsoft Office and SharePoint workflows in the early 2000s
Limitations
- Completely proprietary and obsolete; Microsoft abandoned it in favor of standard TIFF and PDF
- Causes widespread identification conflicts since its file signature is identical to a standard TIFF
- Extremely difficult to open on modern operating systems without relying on third-party conversion utilities
When to choose which format
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems
MODI
Use MODI when…
- Legacy Scanned Document Archival
- Microsoft Office XP/2003/2007 Workflows
- Embedded OCR Text Storage