Image MIME Reference
JXL
JPEG XL
image/jxl
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of JPEG XL and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
JXL wins on browser support
Feature Support
| Feature | JXL | T.38 |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | Yes | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG XL
image/jxl
Extension
.jxl
Container
ISOBMFF / JPEG XL Codestream
Compression
Lossy (VarDCT) / Lossless (Modular)
Algorithm
VarDCT (Variable block-size DCT)Modular (Predictive coding for lossless)
Color Depth
8-bit, 10-bit, 12-bit, 16-bit, 32-bit (Float)
Developed by
Joint Photographic Experts Group (JPEG)
Released
2021
Magic Bytes
FF 0A (Codestream) / 00 00 00 0C 4A 58 4C 20 0D 0A 87 0A (Container)
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 | JXL | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✓ 17+
|
✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
JXL
JXL Strengths
- Capable of losslessly recompressing legacy JPEG files, saving ~20% space while retaining perfect byte-for-byte restorability
- Highly superior progressive decoding (Saliency-driven), allowing recognizable images to load extremely fast on slow connections
- Outperforms WebP and competes favorably with AVIF, especially at high-fidelity settings and for complex textures/photography
- Royalty-free with an open-source reference implementation (libjxl)
Limitations
- Google's removal of JXL support from Chrome severely hindered its adoption as a universal web standard
- Lack of hardware decoding chips compared to video-derived codecs like AVIF (AV1)
- File parsing logic is complex due to the split between raw codestreams and ISOBMFF containers
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
JXL
Use JXL when…
- High-End Web Delivery (via Safari/Polyfills)
- HDR Photography
- Legacy JPEG Archiving
- Digital Art & Image Storage
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers