Image MIME Reference
JPEG-XR
JPEG XR (HD Photo)
image/vnd.ms-photo
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of JPEG XR (HD Photo) 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 | JPEG-XR | 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 |
JPEG XR (HD Photo)
image/vnd.ms-photo
Extension
.jxr.wdp.hdp
Container
TIFF-like Image File Directory (IFD)
Compression
Lossy (Lapped Bi-orthogonal Transform) / Lossless
Algorithm
Lapped Bi-orthogonal Transform (LBT)
Color Depth
8-bit (Grayscale, RGB, CMYK), 16-bit, 32-bit Floating Point (HDR)
Developed by
Microsoft Corporation (later Joint Photographic Experts Group)
Released
2006
Magic Bytes
49 49 BC 01
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 | JPEG-XR | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✓
|
✕ |
JPEG-XR
JPEG-XR Strengths
- Excellent support for 16-bit and 32-bit floating-point HDR images without massive file size bloat
- Native support for alpha transparency, which standard JPEG fundamentally lacks
- Computational complexity for decoding/encoding is relatively low, making it hardware-friendly
Limitations
- Suffered a complete failure of adoption in the web browser market outside of Microsoft's ecosystem
- Fully superseded by modern, open formats like WebP, AVIF, and JPEG XL which offer better compression and universal browser support
- Multiple file extensions (.wdp, .hdp, .jxr) and MIME types cause confusion and parsing fragmentation
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
JPEG-XR
Use JPEG-XR when…
- Legacy Windows Desktop Backgrounds
- XPS (XML Paper Specification) Documents
- Early High Dynamic Range (HDR) Photography
- DirectX Textures
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers