Image MIME Reference
PNM
Portable Anymap
image/x-portable-anymap
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Portable Anymap 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 | PNM | 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 |
Portable Anymap
image/x-portable-anymap
Extension
.pnm
Container
Netpbm
Compression
Uncompressed
Algorithm
None
Color Depth
1-bit (PBM), 8-bit to 16-bit (PGM), 24-bit to 48-bit (PPM)
Developed by
Jef Poskanzer (Netpbm Project)
Released
1988
Magic Bytes
50 31, 50 32, 50 33, 50 34, 50 35, or 50 36
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 | PNM | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
PNM
PNM Strengths
- Unparalleled simplicity: parsers and writers for PNM files can be written from scratch in C or Python in just a few minutes without relying on external libraries
- Serves as an excellent foundational teaching tool for computer science students learning about image arrays and raster graphics
- Flawlessly pipes through Unix command-line utilities for robust automated image processing (via the Netpbm suite)
Limitations
- Zero compression natively results in astronomical file sizes, making it entirely impractical for web delivery or consumer storage
- No support for standard metadata formats like EXIF, XMP, or ICC color profiles
- No native alpha channel support in the classic PNM specification (though the newer PAM format 'P7' addresses this)
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
PNM
Use PNM when…
- Unix/Linux Command-Line Image Processing (Netpbm suite)
- Academic Computer Vision Research
- Intermediary Format for Image Format Conversion
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers