Free webp to jpg
Image MIME Reference
Olympus-ORF

Olympus Raw Format

image/x-olympus-orf
VS

PTI Image (Personal/Vanity Tree)

image/prs.pti
PTI

A complete technical comparison of Olympus Raw Format and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature Olympus-ORF PTI
Transparency (Alpha) ✕ No ✕ No
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 →
PTI Image (Personal/Vanity Tree)
image/prs.pti
Extension
.pti
Container Proprietary
Compression Unknown / Proprietary
Algorithm
Unknown
Color Depth Unknown
Developed by Jürn Laun
Released 1999
Magic Bytes
Unknown
Full PTI reference →

Browser Support Comparison

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

PTI Strengths

  • Provided a registered MIME type namespace for a specific application's proprietary image format without conflicting with standard web types
Limitations
  • Completely undocumented and unsupported in modern ecosystems
  • Zero web browser compatibility
  • Falls into the 'vanity' tree, making it irrelevant for standard cross-platform data exchange

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
PTI
Use PTI when…
  • Legacy Application Specific Workflows
  • Proprietary Image Storage
Share this comparison