Image MIME Reference
BMP
Windows Bitmap (Legacy Windows MIME Alias)
image/x-windows-bmp
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Windows Bitmap (Legacy Windows MIME Alias) and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
BMP wins on browser support
Feature Support
| Feature | BMP | T.38 |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | Yes | ✕ No |
Windows Bitmap (Legacy Windows MIME Alias)
image/x-windows-bmp
Extension
.bmp.dib
Container
DIB (Device-Independent Bitmap)
Compression
Uncompressed / Run-Length Encoding (RLE)
Algorithm
NoneRLE4RLE8
Color Depth
1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 16-bit (High Color), 24-bit (True Color), 32-bit (True Color with Alpha)
Developed by
Microsoft Corporation
Released
1985
Magic Bytes
42 4D
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 | BMP | T.38 |
|---|---|---|
Chrome
|
✓ 1
|
✕ |
Firefox
|
✓ 1
|
✕ |
Safari
|
✓ 1
|
✕ |
Edge
|
✓ 12
|
✕ |
IE (Legacy)
|
✓
|
✕ |
BMP
BMP Strengths
- Universally supported by all major operating systems and modern web browsers
- Maintains perfect, lossless fidelity because pixel data is stored without lossy compression artifacts
Limitations
- Massive file size overhead due to a lack of modern compression algorithms
- Legacy MIME strings like 'image/x-windows-bmp' can trigger validation warnings in strict security or API environments if unhandled
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
BMP
Use BMP when…
- Legacy Windows Desktop Registry Associations
- Older Enterprise Intranet Applications
- Windows Graphics Archival
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers