Image MIME Reference
Radiance
Radiance HDR
image/vnd.radiance
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Radiance HDR 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 | Radiance | T.38 |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Radiance HDR
image/vnd.radiance
Extension
.hdr.pic.rgbe.xyze
Container
Radiance Information Header
Compression
Run-Length Encoding (RLE) / Uncompressed
Algorithm
Adaptive Run-Length Encoding (RLE)
Color Depth
32-bit (8-bit per channel RGB + 8-bit shared Exponent)
Developed by
Greg Ward (Lawrence Berkeley National Laboratory)
Released
1989
Magic Bytes
23 3F 52 41 44 49 41 4E 43 45
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 | Radiance | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
Radiance
Radiance Strengths
- Universally supported by almost every 3D modeling software, renderer, and game engine in existence
- RGBE encoding offers a brilliant balance between High Dynamic Range capability and small file size (compared to 32-bit float OpenEXR)
- Simple, easy-to-parse ASCII header followed by straightforward RLE binary data
Limitations
- Does not support alpha transparency (no way to store an isolated light source with a transparent background)
- The shared exponent architecture can occasionally introduce banding or color artifacts in extreme edge cases compared to true 16-bit/32-bit floating-point formats like OpenEXR
- Zero native browser support for 2D viewing
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
Radiance
Use Radiance when…
- Image-Based Lighting (IBL)
- 3D Environment Maps (HDRI Skydomes)
- Lighting Simulation
- VFX and CGI Rendering
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers