Free webp to jpg
EN
Image MIME Reference
FreeHand

Macromedia FreeHand Document

image/x-freehand
VS

Windows Icon (Legacy MIME)

image/x-icon
ICO

A complete technical comparison of Macromedia FreeHand Document 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 FreeHand ICO
Transparency (Alpha) Yes Yes
Animation Support Yes ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile Yes ✕ No
Macromedia FreeHand Document
image/x-freehand
Extension
.fh.fh4.fh5.fh7.fh8.fh9.fh10.fh11.ft11
Container Proprietary Binary (Aldus Graphic Document)
Compression Uncompressed / Deflate (in later versions)
Algorithm
NoneDeflate (Optional in later versions)
Color Depth Vector Data (RGB/CMYK)
Developed by Altsys / Aldus / Macromedia
Released 1988
Magic Bytes
41 47 44 31 to 41 47 44 34
Full FreeHand 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 FreeHand ICO
Chrome Chrome
✕
✓ 1
Firefox Firefox
✕
✓ 1
Safari Safari
✕
✓ 1
Edge Edge
✕
✓ 12
IE IE (Legacy)
✕
✓
FreeHand

FreeHand Strengths

  • Historically one of the most powerful and intuitive vector editors on the market, praised for multi-page support long before Adobe Illustrator implemented it
  • Files are generally compact and self-contained
Limitations
  • Completely abandoned proprietary format; Adobe actively blocked native import in modern versions of Illustrator
  • No support in modern web browsers; must be converted to SVG
  • Versioning fragmentation means parsers must account for wildly different binary structures depending on the specific .fhX extension used
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

FreeHand
Use FreeHand when…
  • Legacy Graphic Design Portfolios
  • Historical Desktop Publishing Archival
  • Old Corporate Logo Vectors
ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons

More comparisons

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