Image MIME Reference
T.38
T.38 Fax over IP (FoIP)
image/t38
VS
Tencent TAP Image
image/vnd.tencent.tap
Tencent-TAP
A complete technical comparison of T.38 Fax over IP (FoIP) and Tencent TAP Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | T.38 | Tencent-TAP |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
T.38 Fax over IP (FoIP)
image/t38
Extension
.t38
Container
UDPTL or TCP (Network Transport)
Compression
Lossless (MH, MR, MMR / T.4, T.6)
Algorithm
MH (Modified Huffman)MR (Modified Read)MMR (Modified Modified Read)
Color Depth
1-bit (Monochrome B&W)
Developed by
ITU-T (International Telecommunication Union)
Released
1998
Magic Bytes
None (Network Stream)
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 | T.38 | Tencent-TAP |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
T.38
T.38 Strengths
- Designed specifically to overcome the timing and packet-loss issues that plague traditional fax over standard VoIP audio codecs (like G.711)
- Reduces bandwidth requirements by transmitting fax protocol data rather than uncompressed audio tones
- Universally supported by enterprise SIP trunks and Session Border Controllers (SBCs) for FoIP
Limitations
- Not an actual image file format, causing confusion due to its 'image/' MIME classification
- Extremely complex to implement correctly over lossy UDP networks (relies on UDPTL redundancy mechanisms)
- Zero support in web browsers or standard image viewing software
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
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers
Tencent-TAP
Use Tencent-TAP when…
- Internal Tencent Ecosystem Applications
- Proprietary Mobile or Gaming Assets