Image MIME Reference
HTJ2K-(JPH)
High-Throughput JPEG 2000 Image
image/jph
VS
JPEG Network Graphics
image/x-jng
JNG
A complete technical comparison of High-Throughput JPEG 2000 Image and JPEG Network Graphics — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-(JPH) | JNG |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | Yes |
| HDR Support | Yes | ✕ No |
| 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
JPEG Network Graphics
image/x-jng
Extension
.jng
Container
PNG-style Chunk Structure (JHDR, JDAT, IDAT, IEND)
Compression
Lossy (JPEG/DCT for color) / Lossless (Deflate for alpha mask)
Algorithm
JPEG (Discrete Cosine Transform)Deflate (LZ77)
Color Depth
8-bit, 12-bit, 24-bit (RGB), 32-bit (RGBA)
Developed by
MNG Development Group (Glenn Randers-Pehrson et al.)
Released
2001
Magic Bytes
8B 4A 4E 47 0D 0A 1A 0A
Browser Support Comparison
| Browser | HTJ2K-(JPH) | JNG |
|---|---|---|
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
JNG
JNG Strengths
- Solved a massive technical hurdle in the early 2000s by combining high-compression lossy photographic data with crisp, 8-bit alpha transparency
- Utilized the highly robust, extensible chunk-based architecture of the PNG format
- Provided an excellent, bandwidth-saving alternative to massive 32-bit transparent PNGs for web design
Limitations
- Failed to achieve critical mass; browser vendors largely abandoned the MNG/JNG standard due to implementation complexity
- Completely obsolete today, having been superseded by natively supported, superior formats like WebP, AVIF, and HEIC
- Decoding requires a hybrid engine that can parse PNG chunks while simultaneously decoding a JPEG stream and a Deflate stream, complicating software support
When to choose which format
HTJ2K-(JPH)
Use HTJ2K-(JPH) when…
- Medical Imaging (DICOM)
- Geospatial Data
- Digital Cinema
- Professional Archiving
JNG
Use JNG when…
- Embedded frames in MNG animations
- Historical web graphics requiring lossy compression with transparency