Image MIME Reference
ICO
Windows Icon (Legacy MIME)
image/x-icon
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Windows Icon (Legacy MIME) and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
ICO wins on browser support
Feature Support
| Feature | ICO | 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 | ✕ No | ✕ No |
Windows Icon (Legacy MIME)
image/x-icon
Extension
.ico
Container
ICO Directory Structure
Compression
Uncompressed (DIB/BMP) / Deflate (Embedded PNG)
Algorithm
NoneDeflate (via PNG)
Color Depth
1-bit, 4-bit, 8-bit, 24-bit (True Color), 32-bit (RGBA)
Developed by
Microsoft Corporation
Released
1985
Magic Bytes
00 00 01 00
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 | ICO | T.38 |
|---|---|---|
Chrome
|
✓ 1
|
✕ |
Firefox
|
✓ 1
|
✕ |
Safari
|
✓ 1
|
✕ |
Edge
|
✓ 12
|
✕ |
IE (Legacy)
|
✓
|
✕ |
ICO
ICO Strengths
- Universally supported by every web browser in existence for website favicons
- Packs multiple resolutions into a single file, eliminating the need to serve different files for the taskbar vs. the desktop
- Modern support for embedded PNGs (since Windows Vista) allows for excellent 32-bit transparency (alpha channels) and drastically reduced file sizes
Limitations
- Internal file structure is convoluted due to decades of legacy cruft, such as the requirement for BMP data to lack a standard file header but double the height property for an archaic XOR/AND mask
- Larger file size compared to a single optimized PNG or SVG, as it literally stores the same image multiple times at different scales
- The MIME type landscape is highly fragmented (x-icon vs. vnd.microsoft.icon), causing occasional caching or strict-MIME validation errors on restrictive servers
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
ICO
Use ICO when…
- Website Favicons (favicon.ico)
- Windows Application Executable Icons (.exe)
- Desktop Shortcut Icons
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers