Free webp to jpg
EN
Image MIME Reference
TGA

Truevision TGA (Legacy MIME Alias)

image/x-tga
VS

Valve Texture Format

image/vnd.valve.source.texture
VTF

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

Equal browser support

Feature Support

Feature TGA VTF
Transparency (Alpha) Yes Yes
Animation Support ✕ No Yes
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
Truevision TGA (Legacy MIME Alias)
image/x-tga
Extension
.tga.icb.vda.vst
Container Truevision TGA Footer/Header
Compression Uncompressed / Run-Length Encoding (RLE)
Algorithm
NoneRLE
Color Depth 8-bit (Grayscale or Indexed), 16-bit (High Color), 24-bit (True Color), 32-bit (True Color with Alpha Channel)
Developed by Truevision Inc.
Released 1984
Magic Bytes
54 52 55 45 56 49 53 49 4F 4E 2D 58 46 49 4C 45 2E 00 (At the end of the file)
Full TGA reference →
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 →

Browser Support Comparison

Browser TGA VTF
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
TGA

TGA Strengths

  • Incredibly simple byte layout allows developers to write custom loaders and exporters in a few dozen lines of code, bypassing the need for heavy external libraries
  • Native support for 8-bit alpha channels ensures flawless transparency masking for real-time 3D rendering
  • Fast, predictable RLE decoding requires almost no CPU overhead compared to DEFLATE (PNG) or DCT (JPEG)
Limitations
  • RLE compression is relatively weak by modern standards, resulting in large file sizes
  • Lacks a standard magic byte header at the beginning of the file, making file-sniffing unreliable for older v1.0 files
  • Zero support in web browsers; must be converted to PNG or WebP for web delivery
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

TGA
Use TGA when…
  • Video Game 3D Textures and Materials
  • 3D Rendering and Animation Sequences
  • Legacy Video Production Workflows
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)

More comparisons

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