Image MIME Reference
JPEG-XS-Codestream
JPEG XS Codestream
image/jxsc
VS
Tencent TAP Image
image/vnd.tencent.tap
Tencent-TAP
A complete technical comparison of JPEG XS 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 | JPEG-XS-Codestream | Tencent-TAP |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
JPEG XS Codestream
image/jxsc
Extension
.jxsc.jxs
Container
None (Raw Codestream)
Compression
Lossy (Visually Lossless) / Mathematically Lossless
Algorithm
JPEG XS (ISO/IEC 21122-1)
Color Depth
8-bit, 10-bit, 12-bit, 14-bit, 16-bit
Developed by
Joint Photographic Experts Group (JPEG) / intoPIX
Released
2019
Magic Bytes
FF 10
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 | JPEG-XS-Codestream | Tencent-TAP |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
JPEG-XS-Codestream
JPEG-XS-Codestream Strengths
- Eliminates container overhead, maximizing parsing speed and minimizing latency to fractions of a millisecond
- Highly optimized for direct hardware implementation in FPGAs and ASICs
- Perfect for continuous data streaming over IP networks without needing to establish file headers
Limitations
- Lacks standard container metadata (EXIF, XMP, ICC profiles), meaning color space and orientation data must be handled externally or out-of-band
- Zero support in web browsers or standard consumer operating systems
- Often requires specialized broadcast hardware or custom software libraries to decode
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
JPEG-XS-Codestream
Use JPEG-XS-Codestream when…
- Hardware Decoding Pipelines (FPGA/ASIC)
- Live Broadcast Infrastructure
- Video over IP Transport
- Embedded Camera Systems
Tencent-TAP
Use Tencent-TAP when…
- Internal Tencent Ecosystem Applications
- Proprietary Mobile or Gaming Assets