Image MIME Reference
PCO-B16
PCO B16 Image
image/vnd.pco.b16
VS
Valve Texture Format
image/vnd.valve.source.texture
VTF
A complete technical comparison of PCO B16 Image and Valve Texture Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | PCO-B16 | 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 |
PCO B16 Image
image/vnd.pco.b16
Extension
.b16
Container
PCO B16 Binary Container
Compression
Uncompressed (Raw Sensor Data)
Algorithm
None
Color Depth
16-bit (Monochrome or Bayer Raw Color)
Developed by
PCO AG (Excelitas PCO GmbH)
Released
Early 2000s
Magic Bytes
50 43 4F 2D
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 | PCO-B16 | VTF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
PCO-B16
PCO-B16 Strengths
- Preserves exact, uncompressed 16-bit raw sensor data, which is critically important for accurate scientific measurements, fluorescence microscopy, and photometry
- The simple, linear struct header is highly predictable and easy to parse in custom Python, MATLAB, or C++ scripts for researchers building bespoke pipelines
Limitations
- Generates massive file sizes due to the complete lack of image compression [1.3.1]
- Completely unsupported by standard operating systems, web browsers, and consumer image editing suites
- Strictly tied to the hardware and software ecosystems of a single camera manufacturer
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
PCO-B16
Use PCO-B16 when…
- Microscopy and Life Sciences
- High-Speed Camera Recording
- Machine Vision and Industrial Inspection
- Scientific Photometry
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)