Free webp to jpg
EN
Image MIME Reference
VTF

Valve Texture Format

image/vnd.valve.source.texture
VS

X Bitmap (Legacy MIME Alias)

image/x-xbm
XBM

A complete technical comparison of Valve Texture Format and X Bitmap (Legacy MIME Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature VTF XBM
Transparency (Alpha) Yes Yes
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
Full VTF reference →
X Bitmap (Legacy MIME Alias)
image/x-xbm
Extension
.xbm
Container C Source Code Header (.h)
Compression Uncompressed (Source Code)
Algorithm
None
Color Depth 1-bit (Monochrome)
Developed by MIT / X Consortium (X Window System)
Released 1988
Magic Bytes
23 64 65 66 69 6e 65 (ASCII '#define')
Full XBM reference →

Browser Support Comparison

Browser VTF XBM
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕
✓
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
XBM

XBM Strengths

  • Can be compiled directly into C or C++ source code without needing an external file loader or binary asset manager
  • Human-readable structure allows developers to inspect, edit, or hand-craft tiny icons directly within a text editor
  • Extremely predictable and lightweight for 1-bit hardware displays and embedded systems
Limitations
  • Strictly limited to 1-bit monochrome (black and white) graphics with no gray or color support
  • Text-based C syntax creates massive file bloat compared to binary 1-bit formats like PBM
  • Completely deprecated in modern web browsers and desktop GUI frameworks

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)
XBM
Use XBM when…
  • X Window System (X11) Cursors and Icons
  • Embedded C/C++ Firmware UI Assets
  • Early 1990s Unix Web Graphics

More comparisons

VTF vs ACES → XBM vs ACES → VTF vs APNG → XBM vs APNG → VTF vs AVCI → XBM vs AVCI → VTF vs AVCS → XBM vs AVCS → VTF vs AVIF → XBM vs AVIF → All comparisons →
Share this comparison