Image MIME Reference
FST-Image
FAST Search & Transfer Image
image/vnd.fst
VS
Olympus Raw Format
image/x-olympus-orf
Olympus-ORF
A complete technical comparison of FAST Search & Transfer Image and Olympus Raw Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | FST-Image | Olympus-ORF |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | ✕ No | Yes |
FAST Search & Transfer Image
image/vnd.fst
Extension
.fst
Container
Proprietary FAST Container
Compression
Proprietary
Algorithm
Unknown (Proprietary FAST encoding)
Color Depth
Unknown
Developed by
FAST Search & Transfer ASA (Arild Fuldseth)
Released
2000
Magic Bytes
Unknown (Proprietary)
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)
Browser Support Comparison
| Browser | FST-Image | Olympus-ORF |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
FST-Image
FST-Image Strengths
- Historically served as an optimized, compressed format for FAST's early multimedia and live streaming engines over constrained late-1990s bandwidth
Limitations
- Completely obsolete and non-functional in modern software ecosystems
- Undocumented, closed-source binary structure with zero support in modern image processing libraries
- Shares its file extension with several other distinct file types (such as FL Studio state files or FAST Search dictionaries), leading to easy misidentification
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
FST-Image
Use FST-Image when…
- Historical FAST Enterprise Search Indexing
- Legacy Proprietary Multimedia Streaming (late 1990s)
- Internal Media Transmission
Olympus-ORF
Use Olympus-ORF when…
- Professional Digital Photography
- Non-destructive Image Post-Processing
- High Dynamic Range (HDR) Imaging Archival