Image MIME Reference
HTJ2K-(JPH)
High-Throughput JPEG 2000 Image
image/jph
VS
Olympus Raw Format
image/x-olympus-orf
Olympus-ORF
A complete technical comparison of High-Throughput JPEG 2000 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 | HTJ2K-(JPH) | Olympus-ORF |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | Yes |
| EXIF Metadata | Yes | Yes |
| ICC Color Profile | Yes | Yes |
High-Throughput JPEG 2000 Image
image/jph
Extension
.jph
Container
JPH (ISO/IEC 15444-15)
Compression
Lossy / Lossless
Algorithm
High-Throughput JPEG 2000 (HTJ2K)
Color Depth
8-bit, 16-bit, 32-bit, 38-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2019
Magic Bytes
00 00 00 0C 6A 50 20 20 0D 0A 87 0A ... 66 74 79 70 6A 70 68 20
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 | HTJ2K-(JPH) | Olympus-ORF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
HTJ2K-(JPH)
HTJ2K-(JPH) Strengths
- Delivers orders of magnitude faster encoding and decoding than standard JPEG 2000 by utilizing a new, parallelizable block coder
- Supports mathematically lossless and lossy compression within the same codestream architecture
- Allows for resolution scalability, progressive decoding, and region-of-interest extraction without needing to decode the entire image
Limitations
- Zero native web browser support, requiring specialized libraries, API conversions, or WebAssembly (like OpenJPH.js) for web deployment
- Lack of broad consumer awareness, keeping it confined to professional, medical, and scientific workflows
- Requires more advanced software ecosystems to decode than ubiquitous formats like JPEG or WebP
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
HTJ2K-(JPH)
Use HTJ2K-(JPH) when…
- Medical Imaging (DICOM)
- Geospatial Data
- Digital Cinema
- Professional Archiving
Olympus-ORF
Use Olympus-ORF when…
- Professional Digital Photography
- Non-destructive Image Post-Processing
- High Dynamic Range (HDR) Imaging Archival