Image MIME Reference
HTJ2K-Codestream
High-Throughput JPEG 2000 Codestream
image/jphc
VS
Tencent TAP Image
image/vnd.tencent.tap
Tencent-TAP
A complete technical comparison of High-Throughput JPEG 2000 Codestream and Tencent TAP Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-Codestream | Tencent-TAP |
|---|---|---|
| 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
Tencent TAP Image
image/vnd.tencent.tap
Extension
.tap
Container
Proprietary Tencent Container
Compression
Unknown (Proprietary)
Algorithm
Unknown
Color Depth
Unknown
Developed by
Tencent (Registered by Ni Hui)
Released
2014
Magic Bytes
Unknown (Proprietary)
Browser Support Comparison
| Browser | HTJ2K-Codestream | Tencent-TAP |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
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
Tencent-TAP
Tencent-TAP Strengths
- Officially registered with IANA, ensuring a unique MIME type identifier for internal Tencent network routing and content negotiation
Limitations
- Completely undocumented and closed-source, making it impossible to decode or parse outside of Tencent's software
- Shares its file extension (.tap) with numerous other established legacy formats, leading to frequent automated file misidentification by Node/Python libraries
When to choose which format
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems
Tencent-TAP
Use Tencent-TAP when…
- Internal Tencent Ecosystem Applications
- Proprietary Mobile or Gaming Assets