Image MIME Reference
FPX
FlashPix
image/vnd.fpx
VS
Khronos Texture
image/ktx
KTX
A complete technical comparison of FlashPix and Khronos Texture — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | FPX | KTX |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
FlashPix
image/vnd.fpx
Extension
.fpx
Container
Microsoft OLE Structured Storage (COM)
Compression
JPEG (Lossy) / Uncompressed / Single-color (Solid)
Algorithm
JPEGNone
Color Depth
8-bit (Grayscale/Indexed), 24-bit (RGB), 32-bit (CMYK/RGBA)
Developed by
Eastman Kodak, Microsoft, Hewlett-Packard, Live Picture
Released
1996
Magic Bytes
D0 CF 11 E0 A1 B1 1A E1
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
Browser Support Comparison
| Browser | FPX | KTX |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
FPX
FPX Strengths
- Allowed early, low-RAM computers to view and edit massive, high-resolution digital photos instantly by only loading the needed tiles and resolutions
- Pioneered the multi-resolution pyramid and tiling concepts heavily used today in modern deep-zoom and web mapping applications (like Google Maps)
Limitations
- Completely obsolete and unsupported by modern web browsers or operating systems
- Uses the complex, proprietary Microsoft OLE container format, making it incredibly difficult to parse or extract data from without dedicated legacy libraries
- Prone to being misidentified by MIME sniffers as an old Microsoft Office document
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
FPX
Use FPX when…
- Legacy Digital Photography
- Kodak Picture CDs (Historical)
- Early High-Resolution Image Viewers
KTX
Use KTX when…
- Real-time 3D Graphics
- WebGL / WebGPU Applications
- Mobile Games
- Virtual/Augmented Reality (VR/AR)