Image MIME Reference
Olympus-ORF
Olympus Raw Format
image/x-olympus-orf
VS
Portable Bitmap
image/x-portable-bitmap
PBM
A complete technical comparison of Olympus Raw Format and Portable Bitmap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | Olympus-ORF | PBM |
|---|---|---|
| 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)
Portable Bitmap
image/x-portable-bitmap
Extension
.pbm
Container
Netpbm
Compression
Uncompressed
Algorithm
None
Color Depth
1-bit (Monochrome)
Developed by
Jef Poskanzer (Netpbm Project)
Released
1988
Magic Bytes
50 31 (ASCII) or 50 34 (Binary)
Browser Support Comparison
| Browser | Olympus-ORF | PBM |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
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
PBM
PBM Strengths
- Absolute structural simplicity allows parsers to be written from scratch with just a few lines of code
- ASCII encoding allows manual editing and debugging directly within a standard text editor
- Serves as a flawless, lossless intermediary for 1-bit raster data like scanned documents or barcodes
Limitations
- Strictly limited to 1-bit monochrome images; cannot natively display shades of gray or color
- Lack of compression results in extremely large file sizes, particularly when using the ASCII 'P1' encoding
- No support for alpha transparency or modern metadata standards like EXIF
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
PBM
Use PBM when…
- Optical Character Recognition (OCR) Pre-processing
- Unix/Linux Command-Line Image Pipelines
- Academic Image Processing Teaching