Image MIME Reference
Radiance
Radiance HDR
image/vnd.radiance
VS
Valve Texture Format
image/vnd.valve.source.texture
VTF
A complete technical comparison of Radiance HDR and Valve Texture Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | Radiance | VTF |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | Yes |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Radiance HDR
image/vnd.radiance
Extension
.hdr.pic.rgbe.xyze
Container
Radiance Information Header
Compression
Run-Length Encoding (RLE) / Uncompressed
Algorithm
Adaptive Run-Length Encoding (RLE)
Color Depth
32-bit (8-bit per channel RGB + 8-bit shared Exponent)
Developed by
Greg Ward (Lawrence Berkeley National Laboratory)
Released
1989
Magic Bytes
23 3F 52 41 44 49 41 4E 43 45
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 | Radiance | VTF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
Radiance
Radiance Strengths
- Universally supported by almost every 3D modeling software, renderer, and game engine in existence
- RGBE encoding offers a brilliant balance between High Dynamic Range capability and small file size (compared to 32-bit float OpenEXR)
- Simple, easy-to-parse ASCII header followed by straightforward RLE binary data
Limitations
- Does not support alpha transparency (no way to store an isolated light source with a transparent background)
- The shared exponent architecture can occasionally introduce banding or color artifacts in extreme edge cases compared to true 16-bit/32-bit floating-point formats like OpenEXR
- Zero native browser support for 2D viewing
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
Radiance
Use Radiance when…
- Image-Based Lighting (IBL)
- 3D Environment Maps (HDRI Skydomes)
- Lighting Simulation
- VFX and CGI Rendering
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)