Free webp to jpg
EN
Image MIME Reference
AZV

AirZip Accelerator Image

image/vnd.airzip.accelerator.azv
VS

DirectDraw Surface

image/vnd.ms-dds
DDS

A complete technical comparison of AirZip Accelerator Image and DirectDraw Surface — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature AZV DDS
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
AirZip Accelerator Image
image/vnd.airzip.accelerator.azv
Extension
.azv
Container Proprietary AirZip Container
Compression Lossy (Proprietary) / Lossless (Proprietary)
Algorithm
AirZip Proprietary Compression
Color Depth 8-bit (Indexed), 24-bit (RGB)
Developed by AirZip, Inc.
Released 1999
Magic Bytes
Unknown (Proprietary)
Full AZV reference →
DirectDraw Surface
image/vnd.ms-dds
Extension
.dds
Container DirectDraw Surface
Compression Block Compression (BC1-BC7) / DXTC / S3TC / Uncompressed (RGBA, Floating-Point)
Algorithm
DXT1-DXT5BC1-BC7ASTC / ETC2 (Extended)
Color Depth 8-bit, 16-bit, 24-bit, 32-bit (RGBA), 16-bit/32-bit Floating Point (HDR)
Developed by Microsoft Corporation
Released 1999
Magic Bytes
44 44 53 20
Full DDS reference →

Browser Support Comparison

Browser AZV DDS
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
AZV

AZV Strengths

  • Historically allowed internet users to browse the web up to 5x faster over 56k dial-up modems by drastically reducing image payload sizes
  • Officially registered in the IANA vendor tree, preventing MIME type conflicts on early web proxy servers
Limitations
  • Completely obsolete in the modern broadband era
  • Closed-source and proprietary, meaning no modern image manipulation libraries (like ImageMagick or libvips) can decode it
  • Zero support in standard web browsers
DDS

DDS Strengths

  • Massively reduces VRAM footprint and memory bandwidth usage because the GPU decodes the block compression in hardware
  • Encapsulates complex texture arrays, volume textures, cubemaps, and entire mipmap chains within a single, highly structured file
  • Supports high-dynamic-range (HDR) floating-point data for modern physically based rendering (PBR)
Limitations
  • Block compression algorithms (like DXT) are lossy and can introduce ugly blocky artifacts, especially in smooth gradients or normal maps if not tuned properly
  • Files are generally larger on the physical hard drive than highly compressed formats like PNG or WebP
  • Zero support in web browsers or standard consumer image viewers

When to choose which format

AZV
Use AZV when…
  • Dial-up Web Acceleration
  • Bandwidth Optimization (Historical)
  • Legacy Proxy Servers
DDS
Use DDS when…
  • Real-Time 3D Game Textures
  • DirectX and Vulkan Rendering Pipelines
  • Skyboxes and Environment Cubemaps
  • Volume Textures (3D Textures)

More comparisons

AZV vs ACES → DDS vs ACES → AZV vs APNG → DDS vs APNG → AZV vs AVCI → DDS vs AVCI → AZV vs AVCS → DDS vs AVCS → AZV vs AVIF → DDS vs AVIF → All comparisons →
Share this comparison