Free webp to jpg
EN
Image MIME Reference
AZV

AirZip Accelerator Image

image/vnd.airzip.accelerator.azv
VS

Windows Icon (Legacy MIME)

image/x-icon
ICO

A complete technical comparison of AirZip Accelerator Image and Windows Icon (Legacy MIME) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

ICO wins on browser support

Feature Support

Feature AZV ICO
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No ✕ No
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 →
Windows Icon (Legacy MIME)
image/x-icon
Extension
.ico
Container ICO Directory Structure
Compression Uncompressed (DIB/BMP) / Deflate (Embedded PNG)
Algorithm
NoneDeflate (via PNG)
Color Depth 1-bit, 4-bit, 8-bit, 24-bit (True Color), 32-bit (RGBA)
Developed by Microsoft Corporation
Released 1985
Magic Bytes
00 00 01 00
Full ICO reference →

Browser Support Comparison

Browser AZV ICO
Chrome Chrome
✕
✓ 1
Firefox Firefox
✕
✓ 1
Safari Safari
✕
✓ 1
Edge Edge
✕
✓ 12
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
ICO

ICO Strengths

  • Universally supported by every web browser in existence for website favicons
  • Packs multiple resolutions into a single file, eliminating the need to serve different files for the taskbar vs. the desktop
  • Modern support for embedded PNGs (since Windows Vista) allows for excellent 32-bit transparency (alpha channels) and drastically reduced file sizes
Limitations
  • Internal file structure is convoluted due to decades of legacy cruft, such as the requirement for BMP data to lack a standard file header but double the height property for an archaic XOR/AND mask
  • Larger file size compared to a single optimized PNG or SVG, as it literally stores the same image multiple times at different scales
  • The MIME type landscape is highly fragmented (x-icon vs. vnd.microsoft.icon), causing occasional caching or strict-MIME validation errors on restrictive servers

When to choose which format

AZV
Use AZV when…
  • Dial-up Web Acceleration
  • Bandwidth Optimization (Historical)
  • Legacy Proxy Servers
ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons

More comparisons

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