Free webp to jpg
Image MIME Reference
DICOM-RLE

DICOM Run-Length Encoding

image/dicom-rle
VS

BlockFact Image

image/vnd.blockfact.facti
FACTI

A complete technical comparison of DICOM Run-Length Encoding and BlockFact Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature DICOM-RLE FACTI
Transparency (Alpha) ✕ No Yes
Animation Support Yes ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes Yes
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 →
BlockFact Image
image/vnd.blockfact.facti
Extension
.facti
Container BlockFact Authenticated Container
Compression Container (Inherits payload compression, e.g., JPEG/PNG)
Algorithm
None (Pass-through to embedded payload)
Color Depth Inherited from payload
Developed by BlockFact
Released 2025
Magic Bytes
Unknown (Proprietary Container)
Full FACTI reference →

Browser Support Comparison

Browser DICOM-RLE FACTI
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
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
FACTI

FACTI Strengths

  • Provides undeniable, mathematically verifiable proof of a photo's origin (time, location, and device) via the StarkNet blockchain [1.3.1]
  • Privacy-first design utilizes zero-knowledge proofs (Groth16), meaning the actual image is never uploaded to a central server or blockchain
  • Invisible watermarking ensures that even if the image is screenshotted or cropped, tampering can be detected
Limitations
  • Lacks native rendering support in web browsers and standard image viewers, requiring specialized software to view
  • Requires blockchain registration at the moment of capture, making it incompatible with existing legacy photos
  • The proprietary nature of the container limits integration to environments supporting the BlockFact SDK

When to choose which format

DICOM-RLE
Use DICOM-RLE when…
  • Medical Imaging
  • Ultrasound
  • X-Rays / CT / MRI
  • PACS Archives
FACTI
Use FACTI when…
  • Journalism and Media Authentication
  • Legal and Insurance Evidence
  • AI Deepfake Prevention
  • Content Provenance and Authorship
Share this comparison