Free webp to jpg
Image MIME Reference
KTX2

Khronos Texture 2.0

image/ktx2
VS

PiCture eXchange

image/x-pcx
PCX

A complete technical comparison of Khronos Texture 2.0 and PiCture eXchange — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature KTX2 PCX
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
Khronos Texture 2.0
image/ktx2
Extension
.ktx2
Container KTX 2.0
Compression Basis Universal (ETC1S / UASTC) / Zstandard (zstd) Supercompression / Uncompressed
Algorithm
ETC1SUASTCZstandard (zstd)Raw GPU Formats (ASTC, BCn)
Color Depth 8-bit, 16-bit, 32-bit (Float)
Developed by Khronos Group
Released 2021
Magic Bytes
AB 4B 54 58 20 32 30 BB 0D 0A 1A 0A
Full KTX2 reference →
PiCture eXchange
image/x-pcx
Extension
.pcx
Container ZSoft Proprietary Header (128 bytes)
Compression Run-Length Encoding (RLE)
Algorithm
ZSoft RLE
Color Depth 1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 24-bit (True Color)
Developed by ZSoft Corporation
Released 1985
Magic Bytes
0A (followed by version, e.g., 0A 05 01 08)
Full PCX reference →

Browser Support Comparison

Browser KTX2 PCX
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
KTX2

KTX2 Strengths

  • Universal hardware compatibility: write once, transcode anywhere to the target GPU's preferred format (ASTC, BC7, PVRTC, etc.)
  • Drastically reduces transmission size over networks thanks to Basis Universal and Zstandard supercompression
  • Seamless integration with the glTF ecosystem for optimized 3D asset delivery
Limitations
  • Requires WebAssembly (Wasm) decoders and JavaScript loaders for web viewing, increasing initial application payload slightly
  • Encoding textures into high-quality Basis Universal UASTC can be computationally intensive and slow
  • Zero support in traditional 2D image viewers or native OS previews
PCX

PCX Strengths

  • Incredibly simple RLE algorithm makes it very fast to decode, which was historically vital for early 3D video game engines
  • Retains crisp, lossless pixel data suitable for pixel art and interface assets
  • Well-documented and highly supported by older desktop publishing and image editing software
Limitations
  • Extremely inefficient compression by modern standards, producing large file sizes compared to PNG
  • Lacks modern imaging features such as alpha channel transparency, EXIF metadata, and color profiles
  • Zero support in web browsers; must be converted to PNG for web use

When to choose which format

KTX2
Use KTX2 when…
  • glTF 3D Models (KHR_texture_basisu)
  • WebGPU and WebGL Applications
  • Game Engines (Unity, Unreal, Godot)
  • Augmented and Virtual Reality (AR/VR)
PCX
Use PCX when…
  • MS-DOS and Early Windows Graphics
  • 1990s Video Game Assets (Textures, UI)
  • Retro Computing Archival
Share this comparison