Free webp to jpg
EN
Image MIME Reference
Canon-CRW

Canon Raw Format

image/x-canon-crw
VS

Valve Texture Format

image/vnd.valve.source.texture
VTF

A complete technical comparison of Canon Raw Format and Valve Texture Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature Canon-CRW VTF
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No Yes
Progressive Loading ✕ No ✕ No
HDR Support Yes Yes
EXIF Metadata Yes ✕ No
ICC Color Profile ✕ No ✕ No
Canon Raw Format
image/x-canon-crw
Extension
.crw
Container CIFF (Camera Image File Format)
Compression Lossless JPEG (ITU-T81)
Algorithm
Lossless JPEG
Color Depth 10-bit (Per Channel), 12-bit (Per Channel)
Developed by Canon Inc.
Released 1998
Magic Bytes
49 49 1A 00 00 00 (Header) / 48 45 41 50 43 43 44 52 (HEAPCCDR signature near end)
Full Canon-CRW 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 Canon-CRW VTF
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
Canon-CRW

Canon-CRW Strengths

  • Preserves original raw sensor data from foundational early digital SLR cameras, allowing for modern noise reduction and demosaicing algorithms to extract better images than software could in 2003
  • Files are remarkably small (often 6-8 MB) compared to modern 40MB+ raw files due to the lower megapixel count of early sensors
Limitations
  • Completely obsolete and utilizes the idiosyncratic CIFF structure rather than the modern, standardized TIFF/EP structure
  • Cannot be natively viewed in web browsers or standard operating system image viewers without specialized codecs
  • Less robust metadata support compared to modern CR2 or CR3 formats
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

Canon-CRW
Use Canon-CRW when…
  • Historical Digital Photography (2000-2004)
  • Non-destructive Image Post-Processing
  • Raw Imaging Archival
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

Canon-CRW vs ACES → VTF vs ACES → Canon-CRW vs APNG → VTF vs APNG → Canon-CRW vs AVCI → VTF vs AVCI → Canon-CRW vs AVCS → VTF vs AVCS → Canon-CRW vs AVIF → VTF vs AVIF → All comparisons →
Share this comparison