Image MIME Reference
SGI
Silicon Graphics Image
image/sgi
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Silicon Graphics Image 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 | SGI | 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 |
Silicon Graphics Image
image/sgi
Extension
.sgi.rgb.rgba.bw.int.inta
Container
SGI Image Format
Compression
Uncompressed / Lossless (Run-Length Encoding)
Algorithm
RLENone
Color Depth
8-bit, 16-bit (Per Channel)
Developed by
Paul Haeberli (Silicon Graphics)
Released
1990
Magic Bytes
01 DA
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 | SGI | T.38 |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
SGI
SGI Strengths
- Pioneered multi-channel and 16-bit per channel imaging capabilities required for high-end 1990s visual effects
- Extremely robust and simple header structure
- Reliable Run-Length Encoding provided solid lossless compression for flat-shaded 3D renders
Limitations
- Completely obsolete for modern web and application development
- Zero native web browser compatibility
- Largely replaced by TIFF and OpenEXR in modern professional VFX and 3D pipelines
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
SGI
Use SGI when…
- Legacy 3D Animation & VFX
- Silicon Graphics IRIX Workflows
- Historical CGI Archiving
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers