Image MIME Reference
VTF
Valve Texture Format
image/vnd.valve.source.texture
VS
Wireless Bitmap
image/vnd.wap.wbmp
WBMP
A complete technical comparison of Valve Texture Format and Wireless Bitmap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | VTF | WBMP |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | Yes | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
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
Wireless Bitmap
image/vnd.wap.wbmp
Extension
.wbmp
Container
WBMP Type 0
Compression
Uncompressed
Algorithm
None
Color Depth
1-bit (Monochrome)
Developed by
WAP Forum (Now Open Mobile Alliance)
Released
1999
Magic Bytes
00 00
Browser Support Comparison
| Browser | VTF | WBMP |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
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
WBMP
WBMP Strengths
- Extremely low processing overhead made it perfectly suited for the ultra-low-power CPUs of late 1990s mobile devices
- Tightly integrated into the WML (Wireless Markup Language) stack, enabling the first functional mobile internet experiences
Limitations
- Completely obsolete and lacks support in modern operating systems and browsers
- Limited entirely to 1-bit black and white (0 for black, 1 for white) with zero support for grayscale, color, or transparency
- The lack of a strong file header signature makes automated MIME type detection highly unreliable
When to choose which format
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)
WBMP
Use WBMP when…
- Legacy WML (Wireless Markup Language) Mobile Sites
- Early Mobile Phone Icons and Operator Logos
- Historical WAP Archival