Image MIME Reference
FST-Image
FAST Search & Transfer Image
image/vnd.fst
VS
Khronos Texture
image/ktx
KTX
A complete technical comparison of FAST Search & Transfer Image and Khronos Texture — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | FST-Image | 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 |
FAST Search & Transfer Image
image/vnd.fst
Extension
.fst
Container
Proprietary FAST Container
Compression
Proprietary
Algorithm
Unknown (Proprietary FAST encoding)
Color Depth
Unknown
Developed by
FAST Search & Transfer ASA (Arild Fuldseth)
Released
2000
Magic Bytes
Unknown (Proprietary)
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 | FST-Image | KTX |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
FST-Image
FST-Image Strengths
- Historically served as an optimized, compressed format for FAST's early multimedia and live streaming engines over constrained late-1990s bandwidth
Limitations
- Completely obsolete and non-functional in modern software ecosystems
- Undocumented, closed-source binary structure with zero support in modern image processing libraries
- Shares its file extension with several other distinct file types (such as FL Studio state files or FAST Search dictionaries), leading to easy misidentification
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
FST-Image
Use FST-Image when…
- Historical FAST Enterprise Search Indexing
- Legacy Proprietary Multimedia Streaming (late 1990s)
- Internal Media Transmission
KTX
Use KTX when…
- Real-time 3D Graphics
- WebGL / WebGPU Applications
- Mobile Games
- Virtual/Augmented Reality (VR/AR)