Image MIME Reference
PCX
PiCture eXchange
image/x-pcx
VS
Valve Texture Format
image/vnd.valve.source.texture
VTF
A complete technical comparison of PiCture eXchange and Valve Texture Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | PCX | VTF |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | Yes |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
PiCture eXchange
image/x-pcx
Extension
.pcx
Container
ZSoft Proprietary Header (128 bytes)
Compression
Run-Length Encoding (RLE)
Algorithm
ZSoft RLE
Color Depth
1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 24-bit (True Color)
Developed by
ZSoft Corporation
Released
1985
Magic Bytes
0A (followed by version, e.g., 0A 05 01 08)
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 | PCX | VTF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
PCX
PCX Strengths
- Incredibly simple RLE algorithm makes it very fast to decode, which was historically vital for early 3D video game engines
- Retains crisp, lossless pixel data suitable for pixel art and interface assets
- Well-documented and highly supported by older desktop publishing and image editing software
Limitations
- Extremely inefficient compression by modern standards, producing large file sizes compared to PNG
- Lacks modern imaging features such as alpha channel transparency, EXIF metadata, and color profiles
- Zero support in web browsers; must be converted to PNG for web use
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
PCX
Use PCX when…
- MS-DOS and Early Windows Graphics
- 1990s Video Game Assets (Textures, UI)
- Retro Computing 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)