Free webp to jpg
Image MIME Reference
ICO

Windows Icon (Legacy MIME)

image/x-icon
VS

Olympus Raw Format

image/x-olympus-orf
Olympus-ORF

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

ICO wins on browser support

Feature Support

Feature ICO Olympus-ORF
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
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 →
Olympus Raw Format
image/x-olympus-orf
Extension
.orf
Container TIFF-based (with proprietary variants)
Compression Uncompressed / Proprietary Lossless
Algorithm
NoneOlympus Proprietary Lossless
Color Depth 12-bit (Per Channel)
Developed by Olympus Corporation (Now OM Digital Solutions)
Released 2000
Magic Bytes
49 49 52 4F (IIRO) or 4D 4D 4F 52 (MMOR) or 49 49 53 52 (IIRS)
Full Olympus-ORF reference →

Browser Support Comparison

Browser ICO Olympus-ORF
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
Olympus-ORF

Olympus-ORF Strengths

  • Retains maximum sensor data, allowing extreme recovery of highlights and shadows that would be permanently lost in a JPEG
  • White balance, sharpening, and color profiling are saved as metadata instructions, meaning they can be completely altered in post-production
  • Unique magic byte signatures make programmatic file sniffing highly reliable compared to other camera manufacturers' TIFF-spoofing headers
Limitations
  • Proprietary format means it requires constant updates to raw processing engines every time a new camera model is released
  • Produces very large file sizes (often 15MB to 30MB+ per image depending on sensor resolution)
  • Cannot be directly embedded into web pages or used in standard HTML/CSS contexts

When to choose which format

ICO
Use ICO when…
  • Website Favicons (favicon.ico)
  • Windows Application Executable Icons (.exe)
  • Desktop Shortcut Icons
Olympus-ORF
Use Olympus-ORF when…
  • Professional Digital Photography
  • Non-destructive Image Post-Processing
  • High Dynamic Range (HDR) Imaging Archival
Share this comparison