Image MIME Reference
PJPEG
Progressive JPEG (Legacy IE Alias)
image/pjpeg
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Progressive JPEG (Legacy IE Alias) and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
PJPEG wins on browser support
Feature Support
| Feature | PJPEG | T.38 |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
Progressive JPEG (Legacy IE Alias)
image/pjpeg
Extension
.jpeg.jpg.pjpeg.pjp.jfif
Container
JPEG (ISO/IEC 10918-1)
Compression
Lossy (DCT)
Algorithm
Discrete Cosine Transform (DCT)
Color Depth
8-bit, 12-bit
Developed by
Joint Photographic Experts Group / Microsoft (Alias)
Released
1992
Magic Bytes
FF D8 FF E0 (JFIF) / FF D8 FF E1 (Exif)
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 | PJPEG | T.38 |
|---|---|---|
Chrome
|
✓ All
|
✕ |
Firefox
|
✓ All
|
✕ |
Safari
|
✓ All
|
✕ |
Edge
|
✓ All
|
✕ |
IE (Legacy)
|
✓
|
✕ |
PJPEG
PJPEG Strengths
- Progressive JPEGs (which this MIME type attempted to describe) provide excellent perceived loading speeds on slow connections by rendering a low-resolution preview first
- Files sent with this MIME type are fully backwards compatible with any standard JPEG decoder
Limitations
- It is a non-standard MIME type that violates IANA specifications
- Causes strict file upload validation scripts to fail if not explicitly whitelisted or mapped
- Creates unnecessary confusion, as the official image/jpeg MIME type already fully encompasses progressive encoding
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
PJPEG
Use PJPEG when…
- Legacy Internet Explorer File Uploads
- Progressive Image Rendering (Historical context)
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers