Image MIME Reference
PNG
Portable Network Graphics (Legacy MIME)
image/x-png
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Portable Network Graphics (Legacy MIME) and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
PNG wins on browser support
Feature Support
| Feature | PNG | T.38 |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
Portable Network Graphics (Legacy MIME)
image/x-png
Extension
.png
Container
PNG Chunk Structure (IHDR, IDAT, IEND)
Compression
Deflate (Lossless)
Algorithm
Deflate (LZ77)
Color Depth
1-bit to 16-bit (Grayscale), 8-bit (Indexed Palette), 24-bit (True Color), 32-bit (True Color with Alpha), 48-bit (High Color), 64-bit (High Color with Alpha)
Developed by
PNG Development Group
Released
1996
Magic Bytes
89 50 4E 47 0D 0A 1A 0A
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 | PNG | T.38 |
|---|---|---|
Chrome
|
✓ 1
|
✕ |
Firefox
|
✓ 1
|
✕ |
Safari
|
✓ 1
|
✕ |
Edge
|
✓ 12
|
✕ |
IE (Legacy)
|
✓
|
✕ |
PNG
PNG Strengths
- The underlying format provides flawless, lossless compression and perfect 8-bit alpha channel transparency
- Universally supported by every modern operating system, image editor, and web browser
Limitations
- The 'image/x-png' string is an obsolete vendor quirk that forces backend developers to write redundant normalization logic in file upload scripts
- If left unnormalized, strict MIME validators or content security policies on modern systems may incorrectly reject valid PNG files
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
PNG
Use PNG when…
- Legacy Internet Explorer File Uploads
- Older ASP/PHP Web Applications
- Lossless Web Graphics
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers