Free webp to jpg
Image MIME Reference
Alias-PIX

Alias PIX Image

image/x-alias-pix
VS

Windows Icon (Legacy MIME)

image/x-icon
ICO

A complete technical comparison of Alias PIX 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 Alias-PIX ICO
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
Alias PIX Image
image/x-alias-pix
Extension
.pix.als.alias.img
Container Alias PIX Header
Compression Run-Length Encoding (RLE)
Algorithm
RLE
Color Depth 24-bit (RGB), 8-bit (Matte/Grayscale variant)
Developed by Alias Research (Later Alias|Wavefront / Autodesk)
Released Early 1990s
Magic Bytes
No explicit magic bytes (Relies on 10-byte integer header)
Full Alias-PIX 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 Alias-PIX ICO
Chrome Chrome
✓ 1
Firefox Firefox
✓ 1
Safari Safari
✓ 1
Edge Edge
✓ 12
IE IE (Legacy)
Alias-PIX

Alias-PIX Strengths

  • The highly simplified structure made it incredibly fast to encode and decode on early 1990s SGI hardware
  • Lossless Run-Length Encoding (RLE) saved disk space without degrading the quality of final 3D renders
Limitations
  • Completely obsolete, having been replaced by more robust formats like TIFF, TGA, and EXR in modern 3D pipelines
  • The lack of a distinct magic byte signature makes reliable automated file detection almost impossible
  • Does not support integrated alpha channels, instead requiring cumbersome, separate 'Matte' files to denote transparency
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

Alias-PIX
Use Alias-PIX when…
  • Legacy Alias PowerAnimator Textures
  • 1990s SGI Workstation Render Outputs
  • Historical 3D Graphics Archival
ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons
Share this comparison