Image MIME Reference
Alias-PIX
Alias PIX Image
image/x-alias-pix
VS
Khronos Texture 2.0
image/ktx2
KTX2
A complete technical comparison of Alias PIX Image and Khronos Texture 2.0 — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | Alias-PIX | KTX2 |
|---|---|---|
| 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 |
Alias PIX Image
image/x-alias-pix
Extension
.pix.als.alias.img
Container
Alias PIX Header
Compression
Run-Length Encoding (RLE)
Algorithm
RLE
Color Depth
24-bit (RGB), 8-bit (Matte/Grayscale variant)
Developed by
Alias Research (Later Alias|Wavefront / Autodesk)
Released
Early 1990s
Magic Bytes
No explicit magic bytes (Relies on 10-byte integer header)
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
Browser Support Comparison
| Browser | Alias-PIX | KTX2 |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
Alias-PIX
Alias-PIX Strengths
- The highly simplified structure made it incredibly fast to encode and decode on early 1990s SGI hardware
- Lossless Run-Length Encoding (RLE) saved disk space without degrading the quality of final 3D renders
Limitations
- Completely obsolete, having been replaced by more robust formats like TIFF, TGA, and EXR in modern 3D pipelines
- The lack of a distinct magic byte signature makes reliable automated file detection almost impossible
- Does not support integrated alpha channels, instead requiring cumbersome, separate 'Matte' files to denote transparency
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
When to choose which format
Alias-PIX
Use Alias-PIX when…
- Legacy Alias PowerAnimator Textures
- 1990s SGI Workstation Render Outputs
- Historical 3D Graphics Archival
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)