Image MIME Reference
KTX
Khronos Texture
image/ktx
VS
PiCture eXchange
image/x-pcx
PCX
A complete technical comparison of Khronos Texture and PiCture eXchange — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | KTX | 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
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
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)
Browser Support Comparison
| Browser | KTX | PCX |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
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)
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
KTX
Use KTX when…
- Real-time 3D Graphics
- WebGL / WebGPU Applications
- Mobile Games
- Virtual/Augmented Reality (VR/AR)
PCX
Use PCX when…
- MS-DOS and Early Windows Graphics
- 1990s Video Game Assets (Textures, UI)
- Retro Computing Archival