Image MIME Reference
KTX2
Khronos Texture 2.0
image/ktx2
VS
Olympus Raw Format
image/x-olympus-orf
Olympus-ORF
A complete technical comparison of Khronos Texture 2.0 and Olympus Raw Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | KTX2 | Olympus-ORF |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | Yes |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | ✕ No | Yes |
Khronos Texture 2.0
image/ktx2
Extension
.ktx2
Container
KTX 2.0
Compression
Basis Universal (ETC1S / UASTC) / Zstandard (zstd) Supercompression / Uncompressed
Algorithm
ETC1SUASTCZstandard (zstd)Raw GPU Formats (ASTC, BCn)
Color Depth
8-bit, 16-bit, 32-bit (Float)
Developed by
Khronos Group
Released
2021
Magic Bytes
AB 4B 54 58 20 32 30 BB 0D 0A 1A 0A
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 | KTX2 | Olympus-ORF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
KTX2
KTX2 Strengths
- Universal hardware compatibility: write once, transcode anywhere to the target GPU's preferred format (ASTC, BC7, PVRTC, etc.)
- Drastically reduces transmission size over networks thanks to Basis Universal and Zstandard supercompression
- Seamless integration with the glTF ecosystem for optimized 3D asset delivery
Limitations
- Requires WebAssembly (Wasm) decoders and JavaScript loaders for web viewing, increasing initial application payload slightly
- Encoding textures into high-quality Basis Universal UASTC can be computationally intensive and slow
- Zero support in traditional 2D image viewers or native OS previews
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
KTX2
Use KTX2 when…
- glTF 3D Models (KHR_texture_basisu)
- WebGPU and WebGL Applications
- Game Engines (Unity, Unreal, Godot)
- Augmented and Virtual Reality (AR/VR)
Olympus-ORF
Use Olympus-ORF when…
- Professional Digital Photography
- Non-destructive Image Post-Processing
- High Dynamic Range (HDR) Imaging Archival