Image MIME Reference
IEF
Image Exchange Format
image/ief
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Image Exchange Format and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | IEF | T.38 |
|---|---|---|
| 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)
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)
Browser Support Comparison
| Browser | IEF | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
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
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
When to choose which format
IEF
Use IEF when…
- Legacy Fax Transmissions
- Early Internet Gateways
- Archival
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers