Image MIME Reference
Alias-PIX
Alias PIX Image
image/x-alias-pix
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Alias PIX 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 | Alias-PIX | 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 |
Alias PIX Image
image/x-alias-pix
Extension
.pix.als.alias.img
Container
Alias PIX Header
Compression
Run-Length Encoding (RLE)
Algorithm
RLE
Color Depth
24-bit (RGB), 8-bit (Matte/Grayscale variant)
Developed by
Alias Research (Later Alias|Wavefront / Autodesk)
Released
Early 1990s
Magic Bytes
No explicit magic bytes (Relies on 10-byte integer header)
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 | Alias-PIX | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
Alias-PIX
Alias-PIX Strengths
- The highly simplified structure made it incredibly fast to encode and decode on early 1990s SGI hardware
- Lossless Run-Length Encoding (RLE) saved disk space without degrading the quality of final 3D renders
Limitations
- Completely obsolete, having been replaced by more robust formats like TIFF, TGA, and EXR in modern 3D pipelines
- The lack of a distinct magic byte signature makes reliable automated file detection almost impossible
- Does not support integrated alpha channels, instead requiring cumbersome, separate 'Matte' files to denote transparency
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
Alias-PIX
Use Alias-PIX when…
- Legacy Alias PowerAnimator Textures
- 1990s SGI Workstation Render Outputs
- Historical 3D 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