Free webp to jpg
EN
Image MIME Reference
ICO

Windows Icon (Legacy MIME)

image/x-icon
VS

Image Exchange Format

image/ief
IEF

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

ICO wins on browser support

Feature Support

Feature ICO IEF
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
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 →
Image Exchange Format
image/ief
Extension
.ief
Container TIFF Class B (TIFF-B)
Compression Lossless (MH, MR, MMR) / Uncompressed
Algorithm
MHMRMMRUncompressed
Color Depth 1-bit (Monochrome)
Developed by IETF Network Fax Working Group
Released 1992
Magic Bytes
49 49 2A 00 (Little-endian) / 4D 4D 00 2A (Big-endian)
Full IEF reference →

Browser Support Comparison

Browser ICO IEF
Chrome Chrome
✓ 1
 ✕
Firefox Firefox
✓ 1
 ✕
Safari Safari
✓ 1
 ✕
Edge Edge
✓ 12
 ✕
IE IE (Legacy)
✓
 ✕
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
IEF

IEF Strengths

  • Provided a standard method for exchanging bi-level fax images during the early days of the Internet
  • Supported multi-page documents
  • Leveraged the highly resilient and well-documented TIFF container
Limitations
  • Completely obsolete and unsupported in modern computing environments
  • Strictly limited to 1-bit monochrome data, lacking color or grayscale capabilities
  • Magic bytes overlap completely with standard TIFF, making specific filetype detection difficult without parsing internal tags

When to choose which format

ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons
IEF
Use IEF when…
  • Legacy Fax Transmissions
  • Early Internet Gateways
  • Archival

More comparisons

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