Image MIME Reference
Olympus-ORF
Olympus Raw Format
image/x-olympus-orf
VS
Progressive JPEG (Legacy IE Alias)
image/pjpeg
PJPEG
A complete technical comparison of Olympus Raw Format and Progressive JPEG (Legacy IE Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
PJPEG wins on browser support
Feature Support
| Feature | Olympus-ORF | PJPEG |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | Yes |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | Yes |
| ICC Color Profile | Yes | Yes |
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)
Progressive JPEG (Legacy IE Alias)
image/pjpeg
Extension
.jpeg.jpg.pjpeg.pjp.jfif
Container
JPEG (ISO/IEC 10918-1)
Compression
Lossy (DCT)
Algorithm
Discrete Cosine Transform (DCT)
Color Depth
8-bit, 12-bit
Developed by
Joint Photographic Experts Group / Microsoft (Alias)
Released
1992
Magic Bytes
FF D8 FF E0 (JFIF) / FF D8 FF E1 (Exif)
Browser Support Comparison
| Browser | Olympus-ORF | PJPEG |
|---|---|---|
Chrome
|
✕ |
✓ All
|
Firefox
|
✕ |
✓ All
|
Safari
|
✕ |
✓ All
|
Edge
|
✕ |
✓ All
|
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
PJPEG
PJPEG Strengths
- Progressive JPEGs (which this MIME type attempted to describe) provide excellent perceived loading speeds on slow connections by rendering a low-resolution preview first
- Files sent with this MIME type are fully backwards compatible with any standard JPEG decoder
Limitations
- It is a non-standard MIME type that violates IANA specifications
- Causes strict file upload validation scripts to fail if not explicitly whitelisted or mapped
- Creates unnecessary confusion, as the official image/jpeg MIME type already fully encompasses progressive encoding
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
PJPEG
Use PJPEG when…
- Legacy Internet Explorer File Uploads
- Progressive Image Rendering (Historical context)