Image MIME Reference
PCX
PiCture eXchange
image/x-pcx
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of PiCture eXchange 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 | PCX | 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 |
PiCture eXchange
image/x-pcx
Extension
.pcx
Container
ZSoft Proprietary Header (128 bytes)
Compression
Run-Length Encoding (RLE)
Algorithm
ZSoft RLE
Color Depth
1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 24-bit (True Color)
Developed by
ZSoft Corporation
Released
1985
Magic Bytes
0A (followed by version, e.g., 0A 05 01 08)
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 | PCX | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
PCX
PCX Strengths
- Incredibly simple RLE algorithm makes it very fast to decode, which was historically vital for early 3D video game engines
- Retains crisp, lossless pixel data suitable for pixel art and interface assets
- Well-documented and highly supported by older desktop publishing and image editing software
Limitations
- Extremely inefficient compression by modern standards, producing large file sizes compared to PNG
- Lacks modern imaging features such as alpha channel transparency, EXIF metadata, and color profiles
- Zero support in web browsers; must be converted to PNG for web use
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
PCX
Use PCX when…
- MS-DOS and Early Windows Graphics
- 1990s Video Game Assets (Textures, UI)
- Retro Computing Archival
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers