Free webp to jpg
EN
Image MIME Reference
Olympus-ORF

Olympus Raw Format

image/x-olympus-orf
VS

X Pixmap

image/x-xpixmap
XPM

A complete technical comparison of Olympus Raw Format and X Pixmap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature Olympus-ORF XPM
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
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 →
X Pixmap
image/x-xpixmap
Extension
.xpm
Container C Source Code Header (.c / .h)
Compression Uncompressed (Source Code)
Algorithm
None
Color Depth Indexed Color (Custom Palette with RGB and Alpha 'None')
Developed by Daniel Dardailler and Colas Nahaboo (Bull / X Consortium)
Released 1989
Magic Bytes
2F 2A 20 58 50 4D 20 2A 2F (ASCII '/* XPM */')
Full XPM reference →

Browser Support Comparison

Browser Olympus-ORF XPM
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕
✓
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
XPM

XPM Strengths

  • Can be compiled directly into C or C++ source code without requiring an external asset loading mechanism
  • Human-readable palette mapping allows developers to inspect, modify, or hand-craft icons directly within a text editor
  • Native support for color palettes and transparency via the 'None' keyword
Limitations
  • Extremely inefficient storage structure for large images, resulting in massive file bloat compared to binary formats like PNG
  • Completely obsolete and unsupported in modern web browsers
  • Parsing overhead requires compiling or interpreting text-based color tables at runtime

When to choose which format

Olympus-ORF
Use Olympus-ORF when…
  • Professional Digital Photography
  • Non-destructive Image Post-Processing
  • High Dynamic Range (HDR) Imaging Archival
XPM
Use XPM when…
  • X Window System (X11) Application Icons and Cursors
  • Embedded C/C++ Firmware Color UI Assets
  • Early Linux Desktop Environment Themes

More comparisons

Olympus-ORF vs ACES → XPM vs ACES → Olympus-ORF vs APNG → XPM vs APNG → Olympus-ORF vs AVCI → XPM vs AVCI → Olympus-ORF vs AVCS → XPM vs AVCS → Olympus-ORF vs AVIF → XPM vs AVIF → All comparisons →
Share this comparison