Image MIME Reference
DICOM-RLE
DICOM Run-Length Encoding
image/dicom-rle
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of DICOM Run-Length Encoding 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 | DICOM-RLE | T.38 |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | Yes | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | Yes | ✕ No |
DICOM Run-Length Encoding
image/dicom-rle
Extension
.dcm.dicom
Container
DICOM (PS3.10)
Compression
Lossless (RLE)
Algorithm
Run-Length Encoding (RLE)
Color Depth
8-bit, 16-bit, 24-bit
Developed by
National Electrical Manufacturers Association (NEMA) / ACR
Released
1993
Magic Bytes
44 49 43 4D (at byte offset 128)
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 | DICOM-RLE | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
DICOM-RLE
DICOM-RLE Strengths
- Guarantees lossless preservation of critical medical data necessary for diagnostics
- Extremely robust metadata structure containing patient information, modality, and spatial geometry
- Faster to encode and decode than complex compression schemes like JPEG 2000
Limitations
- RLE compression offers very low compression ratios compared to modern codecs like JPEG-LS or JPEG 2000
- Zero support in web browsers or standard consumer image viewers
- Strict data privacy regulations (HIPAA/GDPR) make handling DICOM files complex due to embedded PHI
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
DICOM-RLE
Use DICOM-RLE when…
- Medical Imaging
- Ultrasound
- X-Rays / CT / MRI
- PACS Archives
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers