Image MIME Reference
IEF
Image Exchange Format
image/ief
VS
Tencent TAP Image
image/vnd.tencent.tap
Tencent-TAP
A complete technical comparison of Image Exchange Format and Tencent TAP Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | IEF | 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 |
Image Exchange Format
image/ief
Extension
.ief
Container
TIFF Class B (TIFF-B)
Compression
Lossless (MH, MR, MMR) / Uncompressed
Algorithm
MHMRMMRUncompressed
Color Depth
1-bit (Monochrome)
Developed by
IETF Network Fax Working Group
Released
1992
Magic Bytes
49 49 2A 00 (Little-endian) / 4D 4D 00 2A (Big-endian)
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 | IEF | Tencent-TAP |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
IEF
IEF Strengths
- Provided a standard method for exchanging bi-level fax images during the early days of the Internet
- Supported multi-page documents
- Leveraged the highly resilient and well-documented TIFF container
Limitations
- Completely obsolete and unsupported in modern computing environments
- Strictly limited to 1-bit monochrome data, lacking color or grayscale capabilities
- Magic bytes overlap completely with standard TIFF, making specific filetype detection difficult without parsing internal tags
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
IEF
Use IEF when…
- Legacy Fax Transmissions
- Early Internet Gateways
- Archival
Tencent-TAP
Use Tencent-TAP when…
- Internal Tencent Ecosystem Applications
- Proprietary Mobile or Gaming Assets