Free webp to jpg
Image MIME Reference
Net-FPX

Network FlashPix

image/vnd.net-fpx
VS

Olympus Raw Format

image/x-olympus-orf
Olympus-ORF

A complete technical comparison of Network FlashPix and Olympus Raw Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature Net-FPX Olympus-ORF
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
EXIF Metadata Yes Yes
ICC Color Profile Yes Yes
Network FlashPix
image/vnd.net-fpx
Extension
.fpx
Container Microsoft OLE Structured Storage (COM)
Compression JPEG (Lossy) / Uncompressed / Single-color (Solid)
Algorithm
JPEGNone
Color Depth 8-bit (Grayscale/Indexed), 24-bit (RGB), 32-bit (CMYK/RGBA)
Developed by Digital Imaging Group (Kodak, HP, Live Picture, Microsoft)
Released 1996
Magic Bytes
D0 CF 11 E0 A1 B1 1A E1
Full Net-FPX reference →
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 →

Browser Support Comparison

Browser Net-FPX Olympus-ORF
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
Net-FPX

Net-FPX Strengths

  • Revolutionized web imaging in the late 1990s by proving that massive gigapixel images could be navigated seamlessly over 56k dial-up modems
  • Pioneered the tile-based, multi-resolution pyramid concepts that eventually evolved into modern standards like IIIF (International Image Interoperability Framework)
Limitations
  • Completely obsolete, having been replaced by standard JPEG servers and modern tiling formats like Deep Zoom or JPEG 2000/XR
  • Relied on proprietary Java applets or ActiveX controls to render the tiles dynamically in a web browser
  • Extremely complex to parse server-side due to the heavy OLE filesystem container
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

Net-FPX
Use Net-FPX when…
  • Historical Internet Imaging Protocol (IIP) Streaming
  • Early E-Commerce Deep Zoom Implementations
  • Legacy High-Resolution Image Servers
Olympus-ORF
Use Olympus-ORF when…
  • Professional Digital Photography
  • Non-destructive Image Post-Processing
  • High Dynamic Range (HDR) Imaging Archival
Share this comparison