Image MIME Reference
JPEG-XS-Codestream
JPEG XS Codestream
image/jxsc
VS
Valve Texture Format
image/vnd.valve.source.texture
VTF
A complete technical comparison of JPEG XS Codestream and Valve Texture Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | JPEG-XS-Codestream | VTF |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | Yes |
| 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
Valve Texture Format
image/vnd.valve.source.texture
Extension
.vtf
Container
Valve Texture Format Header
Compression
DXTC (DXT1, DXT3, DXT5) / Uncompressed (BGRA8888, RGB888, etc.)
Algorithm
DXT1-DXT5None
Color Depth
8-bit, 24-bit (RGB), 32-bit (RGBA), 16-bit Floating Point (HDR)
Developed by
Valve Corporation
Released
2004
Magic Bytes
56 54 46 00
Browser Support Comparison
| Browser | JPEG-XS-Codestream | VTF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
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
VTF
VTF Strengths
- Extremely fast loading within the Source Engine because the block-compressed data goes directly into the GPU's VRAM without CPU decompression overhead
- Bundles mipmaps, volumetric slices, cubemap faces, and animation frames entirely within a single file
- Openly documented by the Valve Developer Community, leading to a massive ecosystem of third-party modding tools
Limitations
- Strictly tied to the Source Engine ecosystem; entirely useless in standard web or print contexts
- No native support in standard image editors without hunting down and installing specialized plugins
- Block compression algorithms (DXT) are lossy and can cause visible artifacting, especially on normal maps or smooth gradients
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
VTF
Use VTF when…
- Source Engine Game Textures
- Custom Maps and Modding (Garry's Mod, CS:GO)
- Animated In-Game Decals and Sprays
- Environment Cubemaps (Skyboxes)