Free webp to jpg
EN
Image MIME Reference
NAPLPS

North American Presentation Level Protocol Syntax

image/naplps
VS

Olympus Raw Format

image/x-olympus-orf
Olympus-ORF

A complete technical comparison of North American Presentation Level Protocol Syntax and Olympus Raw Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature NAPLPS Olympus-ORF
Transparency (Alpha) ✕ No ✕ No
Animation Support Yes ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
North American Presentation Level Protocol Syntax
image/naplps
Extension
.nap.naplps
Container NAPLPS Byte Stream
Compression Uncompressed (Tokenized ASCII Commands)
Algorithm
None (Coordinate encoding)
Color Depth 16-color palette (Indexed from larger color spaces)
Developed by ANSI / CSA (Based on Canadian CRC's Telidon)
Released 1983
Magic Bytes
1B (Variable / ESC sequences)
Full NAPLPS 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 NAPLPS Olympus-ORF
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
NAPLPS

NAPLPS Strengths

  • Extremely bandwidth-efficient, enabling colorful graphical interfaces over early 300 baud dial-up connections
  • Resolution-independent vector scaling allowed the exact same file to be displayed accurately on varied early PC monitors and television sets
Limitations
  • Completely obsolete and unsupported by modern web technologies
  • Relies heavily on stateful parsing and terminal emulators rather than straightforward file decoding
  • Easily misidentified by MIME sniffers as plain text or generic binary streams due to the lack of a standardized file header
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

NAPLPS
Use NAPLPS when…
  • 1980s Videotex Services
  • Prodigy Online Service Graphics
  • Historical BBS Terminal Graphics
  • Legacy Teletext Broadcasts
Olympus-ORF
Use Olympus-ORF when…
  • Professional Digital Photography
  • Non-destructive Image Post-Processing
  • High Dynamic Range (HDR) Imaging Archival

More comparisons

NAPLPS vs ACES → Olympus-ORF vs ACES → NAPLPS vs APNG → Olympus-ORF vs APNG → NAPLPS vs AVCI → Olympus-ORF vs AVCI → NAPLPS vs AVCS → Olympus-ORF vs AVCS → NAPLPS vs AVIF → Olympus-ORF vs AVIF → All comparisons →
Share this comparison