Image MIME Reference
HTJ2K-(JPH)
High-Throughput JPEG 2000 Image
image/jph
VS
X Pixmap
image/x-xpixmap
XPM
A complete technical comparison of High-Throughput JPEG 2000 Image and X Pixmap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-(JPH) | XPM |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
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
X Pixmap
image/x-xpixmap
Extension
.xpm
Container
C Source Code Header (.c / .h)
Compression
Uncompressed (Source Code)
Algorithm
None
Color Depth
Indexed Color (Custom Palette with RGB and Alpha 'None')
Developed by
Daniel Dardailler and Colas Nahaboo (Bull / X Consortium)
Released
1989
Magic Bytes
2F 2A 20 58 50 4D 20 2A 2F (ASCII '/* XPM */')
Browser Support Comparison
| Browser | HTJ2K-(JPH) | XPM |
|---|---|---|
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
XPM
XPM Strengths
- Can be compiled directly into C or C++ source code without requiring an external asset loading mechanism
- Human-readable palette mapping allows developers to inspect, modify, or hand-craft icons directly within a text editor
- Native support for color palettes and transparency via the 'None' keyword
Limitations
- Extremely inefficient storage structure for large images, resulting in massive file bloat compared to binary formats like PNG
- Completely obsolete and unsupported in modern web browsers
- Parsing overhead requires compiling or interpreting text-based color tables at runtime
When to choose which format
HTJ2K-(JPH)
Use HTJ2K-(JPH) when…
- Medical Imaging (DICOM)
- Geospatial Data
- Digital Cinema
- Professional Archiving
XPM
Use XPM when…
- X Window System (X11) Application Icons and Cursors
- Embedded C/C++ Firmware Color UI Assets
- Early Linux Desktop Environment Themes