Free webp to jpg
Image MIME Reference
DICOM-RLE

DICOM Run-Length Encoding

image/dicom-rle
VS

Windows Icon (Legacy MIME)

image/x-icon
ICO

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

ICO wins on browser support

Feature Support

Feature DICOM-RLE ICO
Transparency (Alpha) ✕ No Yes
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)
Full DICOM-RLE reference →
Windows Icon (Legacy MIME)
image/x-icon
Extension
.ico
Container ICO Directory Structure
Compression Uncompressed (DIB/BMP) / Deflate (Embedded PNG)
Algorithm
NoneDeflate (via PNG)
Color Depth 1-bit, 4-bit, 8-bit, 24-bit (True Color), 32-bit (RGBA)
Developed by Microsoft Corporation
Released 1985
Magic Bytes
00 00 01 00
Full ICO reference →

Browser Support Comparison

Browser DICOM-RLE ICO
Chrome Chrome
✓ 1
Firefox Firefox
✓ 1
Safari Safari
✓ 1
Edge Edge
✓ 12
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
ICO

ICO Strengths

  • Universally supported by every web browser in existence for website favicons
  • Packs multiple resolutions into a single file, eliminating the need to serve different files for the taskbar vs. the desktop
  • Modern support for embedded PNGs (since Windows Vista) allows for excellent 32-bit transparency (alpha channels) and drastically reduced file sizes
Limitations
  • Internal file structure is convoluted due to decades of legacy cruft, such as the requirement for BMP data to lack a standard file header but double the height property for an archaic XOR/AND mask
  • Larger file size compared to a single optimized PNG or SVG, as it literally stores the same image multiple times at different scales
  • The MIME type landscape is highly fragmented (x-icon vs. vnd.microsoft.icon), causing occasional caching or strict-MIME validation errors on restrictive servers

When to choose which format

DICOM-RLE
Use DICOM-RLE when…
  • Medical Imaging
  • Ultrasound
  • X-Rays / CT / MRI
  • PACS Archives
ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons
Share this comparison