Image MIME Reference
JPEG-XS-Codestream
JPEG XS Codestream
image/jxsc
VS
Khronos Texture
image/ktx
KTX
A complete technical comparison of JPEG XS Codestream and Khronos Texture — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | JPEG-XS-Codestream | KTX |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
JPEG XS Codestream
image/jxsc
Extension
.jxsc.jxs
Container
None (Raw Codestream)
Compression
Lossy (Visually Lossless) / Mathematically Lossless
Algorithm
JPEG XS (ISO/IEC 21122-1)
Color Depth
8-bit, 10-bit, 12-bit, 14-bit, 16-bit
Developed by
Joint Photographic Experts Group (JPEG) / intoPIX
Released
2019
Magic Bytes
FF 10
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 | JPEG-XS-Codestream | KTX |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
JPEG-XS-Codestream
JPEG-XS-Codestream Strengths
- Eliminates container overhead, maximizing parsing speed and minimizing latency to fractions of a millisecond
- Highly optimized for direct hardware implementation in FPGAs and ASICs
- Perfect for continuous data streaming over IP networks without needing to establish file headers
Limitations
- Lacks standard container metadata (EXIF, XMP, ICC profiles), meaning color space and orientation data must be handled externally or out-of-band
- Zero support in web browsers or standard consumer operating systems
- Often requires specialized broadcast hardware or custom software libraries to decode
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
JPEG-XS-Codestream
Use JPEG-XS-Codestream when…
- Hardware Decoding Pipelines (FPGA/ASIC)
- Live Broadcast Infrastructure
- Video over IP Transport
- Embedded Camera Systems
KTX
Use KTX when…
- Real-time 3D Graphics
- WebGL / WebGPU Applications
- Mobile Games
- Virtual/Augmented Reality (VR/AR)