Free webp to jpg
EN
Image MIME Reference
FLIF

Free Lossless Image Format

image/flif
VS

Windows Icon (Legacy MIME)

image/x-icon
ICO

A complete technical comparison of Free Lossless Image Format 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 FLIF ICO
Transparency (Alpha) Yes Yes
Animation Support Yes ✕ No
Progressive Loading Yes ✕ No
HDR Support Yes ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
Free Lossless Image Format
image/flif
Extension
.flif
Container FLIF Bitstream
Compression Lossless (MANIAC Entropy Coding)
Algorithm
MANIAC (Meta-Adaptive Near-zero Integer Arithmetic Coding)
Color Depth 1-bit to 16-bit (Per Channel), Grayscale, RGB, RGBA, CMYK
Developed by Jon Sneyers and Pieter Wuille (Cloudinary)
Released 2015
Magic Bytes
46 4C 49 46
Full FLIF 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 FLIF ICO
Chrome Chrome
✕
✓ 1
Firefox Firefox
✕
✓ 1
Safari Safari
✕
✓ 1
Edge Edge
✕
✓ 12
IE IE (Legacy)
✕
✓
FLIF

FLIF Strengths

  • Achieves some of the highest lossless compression ratios ever developed for raster images
  • Incredible progressive decoding allows an image to be highly recognizable even after only 5% of the file has been downloaded
  • Supports animations and complex alpha channels losslessly
Limitations
  • Officially abandoned in favor of JPEG XL
  • Zero native support in web browsers or standard operating system previewers
  • Encoding speed can be significantly slower than standard PNG or WebP compression
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

FLIF
Use FLIF when…
  • Archival of Uncompressed Image Assets
  • Bandwidth-Constrained Progressive Image Loading (Historical)
  • Medical and Scientific Imaging Storage
ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons

More comparisons

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