Free webp to jpg
EN
Image MIME Reference
EDMICS-RLC

Fuji Xerox EDMICS-RLC

image/vnd.fujixerox.edmics-rlc
VS

Khronos Texture

image/ktx
KTX

A complete technical comparison of Fuji Xerox EDMICS-RLC and Khronos Texture — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature EDMICS-RLC KTX
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
Fuji Xerox EDMICS-RLC
image/vnd.fujixerox.edmics-rlc
Extension
.rlc.edm
Container Fuji Xerox EDMICS Wrapper
Compression Run-Length Coding (RLC / RLE)
Algorithm
Run-Length Coding (RLC)
Color Depth 1-bit (Monochrome), 8-bit (Grayscale)
Developed by Fuji Xerox Co., Ltd.
Released 1990s
Magic Bytes
Unknown (Proprietary Container)
Full EDMICS-RLC 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 EDMICS-RLC KTX
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
EDMICS-RLC

EDMICS-RLC Strengths

  • Simple, computationally inexpensive Run-Length Coding enabled rapid compression and decompression on low-power legacy hardware
  • Deeply integrated into Fuji Xerox enterprise hardware for seamless, automated scan-to-archive workflows
Limitations
  • Completely proprietary and closed-source, making modern archival extraction and migration extremely difficult
  • No support in modern image processing libraries like ImageMagick, libvips, or standard viewers without bespoke decoding tools
  • RLC compression is far less efficient than modern algorithms like PNG (Deflate) for complex documents
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

EDMICS-RLC
Use EDMICS-RLC when…
  • Fuji Xerox EDMICS Enterprise Systems
  • Archival of Scanned Engineering Documents
  • Legacy Corporate Scanning Pipelines
KTX
Use KTX when…
  • Real-time 3D Graphics
  • WebGL / WebGPU Applications
  • Mobile Games
  • Virtual/Augmented Reality (VR/AR)

More comparisons

EDMICS-RLC vs ACES → KTX vs ACES → EDMICS-RLC vs APNG → KTX vs APNG → EDMICS-RLC vs AVCI → KTX vs AVCI → EDMICS-RLC vs AVCS → KTX vs AVCS → EDMICS-RLC vs AVIF → KTX vs AVIF → All comparisons →
Share this comparison