Image MIME Reference
CNS-INF2
Comverse Network Systems INF2 Image
image/vnd.cns.inf2
VS
Olympus Raw Format
image/x-olympus-orf
Olympus-ORF
A complete technical comparison of Comverse Network Systems INF2 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 | CNS-INF2 | 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 |
Comverse Network Systems INF2 Image
image/vnd.cns.inf2
Extension
.inf2
Container
Proprietary Comverse Container
Compression
Proprietary
Algorithm
Unknown (Proprietary Telecom Encoding)
Color Depth
Unknown
Developed by
Comverse Network Systems (Ann McLaughlin)
Released
1999
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 | CNS-INF2 | Olympus-ORF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
CNS-INF2
CNS-INF2 Strengths
- Historically allowed Comverse to standardize media transmission internally across their global telecom messaging platforms
Limitations
- Completely obsolete and non-functional outside of decommissioned telecom infrastructure
- Undocumented, closed-source binary structure
- Zero support in modern image processing libraries like ImageMagick, libvips, or FFmpeg
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
CNS-INF2
Use CNS-INF2 when…
- Legacy Telecom Infrastructure
- Historical Comverse Unified Messaging Systems
- Proprietary Server-to-Server Media Exchange
Olympus-ORF
Use Olympus-ORF when…
- Professional Digital Photography
- Non-destructive Image Post-Processing
- High Dynamic Range (HDR) Imaging Archival