Image MIME Reference
HTJ2K-(JPH)
High-Throughput JPEG 2000 Image
image/jph
VS
Pentax Electronic File
image/x-pentax-pef
Pentax-PEF
A complete technical comparison of High-Throughput JPEG 2000 Image and Pentax Electronic File — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-(JPH) | Pentax-PEF |
|---|---|---|
| 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
Pentax Electronic File
image/x-pentax-pef
Extension
.pef
Container
TIFF-based (Proprietary)
Compression
Uncompressed / Proprietary Lossless
Algorithm
NonePentax Proprietary Lossless
Color Depth
12-bit (Per Channel), 14-bit (Per Channel)
Developed by
Pentax (now Ricoh Imaging Company, Ltd.)
Released
2003
Magic Bytes
49 49 2A 00 (Little-endian) or 4D 4D 00 2A (Big-endian)
Browser Support Comparison
| Browser | HTJ2K-(JPH) | Pentax-PEF |
|---|---|---|
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
Pentax-PEF
Pentax-PEF Strengths
- Retains absolute maximum sensor data, enabling massive shadow recovery and highlight protection compared to compressed in-camera JPEGs
- White balance and sharpening are saved as metadata instructions rather than 'baked in', meaning they can be perfectly adjusted in post-production
- Utilizes the standard TIFF container structure, making it relatively straightforward for open-source software like LibRaw to parse
Limitations
- Proprietary format requires continuous updates to third-party processing software whenever Pentax releases a new camera model (unlike the open DNG format)
- Produces very large file sizes compared to standard web formats
- 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
Pentax-PEF
Use Pentax-PEF when…
- Professional Digital Photography
- Non-destructive Image Post-Processing
- Pentax Camera Archival