Free webp to jpg
Image MIME Reference
DICOM-RLE

DICOM Run-Length Encoding

image/dicom-rle
VS

Progressive JPEG (Legacy IE Alias)

image/pjpeg
PJPEG

A complete technical comparison of DICOM Run-Length Encoding and Progressive JPEG (Legacy IE Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

PJPEG wins on browser support

Feature Support

Feature DICOM-RLE PJPEG
Transparency (Alpha) ✕ No ✕ No
Animation Support Yes ✕ No
Progressive Loading ✕ No Yes
HDR Support Yes ✕ No
EXIF Metadata ✕ No Yes
ICC Color Profile Yes Yes
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)
Full DICOM-RLE reference →
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)
Full PJPEG reference →

Browser Support Comparison

Browser DICOM-RLE PJPEG
Chrome Chrome
✓ All
Firefox Firefox
✓ All
Safari Safari
✓ All
Edge Edge
✓ All
IE 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
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

When to choose which format

DICOM-RLE
Use DICOM-RLE when…
  • Medical Imaging
  • Ultrasound
  • X-Rays / CT / MRI
  • PACS Archives
PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
Share this comparison