Free webp to jpg
EN
Image MIME Reference
Net-FPX

Network FlashPix

image/vnd.net-fpx
VS

Valve Texture Format

image/vnd.valve.source.texture
VTF

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

Equal browser support

Feature Support

Feature Net-FPX VTF
Transparency (Alpha) Yes Yes
Animation Support ✕ No Yes
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
Network FlashPix
image/vnd.net-fpx
Extension
.fpx
Container Microsoft OLE Structured Storage (COM)
Compression JPEG (Lossy) / Uncompressed / Single-color (Solid)
Algorithm
JPEGNone
Color Depth 8-bit (Grayscale/Indexed), 24-bit (RGB), 32-bit (CMYK/RGBA)
Developed by Digital Imaging Group (Kodak, HP, Live Picture, Microsoft)
Released 1996
Magic Bytes
D0 CF 11 E0 A1 B1 1A E1
Full Net-FPX 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 Net-FPX VTF
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
Net-FPX

Net-FPX Strengths

  • Revolutionized web imaging in the late 1990s by proving that massive gigapixel images could be navigated seamlessly over 56k dial-up modems
  • Pioneered the tile-based, multi-resolution pyramid concepts that eventually evolved into modern standards like IIIF (International Image Interoperability Framework)
Limitations
  • Completely obsolete, having been replaced by standard JPEG servers and modern tiling formats like Deep Zoom or JPEG 2000/XR
  • Relied on proprietary Java applets or ActiveX controls to render the tiles dynamically in a web browser
  • Extremely complex to parse server-side due to the heavy OLE filesystem container
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

Net-FPX
Use Net-FPX when…
  • Historical Internet Imaging Protocol (IIP) Streaming
  • Early E-Commerce Deep Zoom Implementations
  • Legacy High-Resolution Image Servers
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

Net-FPX vs ACES → VTF vs ACES → Net-FPX vs APNG → VTF vs APNG → Net-FPX vs AVCI → VTF vs AVCI → Net-FPX vs AVCS → VTF vs AVCS → Net-FPX vs AVIF → VTF vs AVIF → All comparisons →
Share this comparison