Free webp to jpg
EN
Image MIME Reference
DICOM-RLE

DICOM Run-Length Encoding

image/dicom-rle
VS

Khronos Texture

image/ktx
KTX

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

Equal browser support

Feature Support

Feature DICOM-RLE KTX
Transparency (Alpha) ✕ No Yes
Animation Support Yes ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes Yes
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 →
Khronos Texture
image/ktx
Extension
.ktx
Container KTX (Khronos Texture 1.1)
Compression Uncompressed / GPU Compressed (ASTC, ETC, BCn, PVRTC)
Algorithm
ASTCETC1 / ETC2BCn (DXT)PVRTCBasis Universal (in KTX2)
Color Depth 8-bit, 16-bit, 32-bit (Integer/Float)
Developed by Khronos Group
Released 2010
Magic Bytes
AB 4B 54 58 20 31 31 BB 0D 0A 1A 0A
Full KTX reference →

Browser Support Comparison

Browser DICOM-RLE KTX
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
KTX

KTX Strengths

  • Enables direct-to-GPU texture uploading, drastically reducing load times and CPU overhead in 3D applications
  • Supports complex texture types natively (mipmaps, cubemaps, 3D volumes, texture arrays)
  • Standardized across major Khronos APIs (OpenGL, Vulkan, WebGL) unlike vendor-specific formats like DDS
Limitations
  • Requires custom JavaScript loaders to parse and display on the web
  • Zero native support in consumer image viewers or 2D photo editing software
  • Format fragmentation: a KTX file containing an ASTC payload will fail to render on hardware that only supports BCn compression (KTX2 and Basis Universal solve this)

When to choose which format

DICOM-RLE
Use DICOM-RLE when…
  • Medical Imaging
  • Ultrasound
  • X-Rays / CT / MRI
  • PACS Archives
KTX
Use KTX when…
  • Real-time 3D Graphics
  • WebGL / WebGPU Applications
  • Mobile Games
  • Virtual/Augmented Reality (VR/AR)

More comparisons

DICOM-RLE vs ACES → KTX vs ACES → DICOM-RLE vs APNG → KTX vs APNG → DICOM-RLE vs AVCI → KTX vs AVCI → DICOM-RLE vs AVCS → KTX vs AVCS → DICOM-RLE vs AVIF → KTX vs AVIF → All comparisons →
Share this comparison