Image MIME Reference
AZV
AirZip Accelerator Image
image/vnd.airzip.accelerator.azv
VS
High-Throughput JPEG 2000 Image
image/jph
HTJ2K-(JPH)
A complete technical comparison of AirZip Accelerator Image and High-Throughput JPEG 2000 Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | AZV | HTJ2K-(JPH) |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | Yes |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | ✕ No | Yes |
AirZip Accelerator Image
image/vnd.airzip.accelerator.azv
Extension
.azv
Container
Proprietary AirZip Container
Compression
Lossy (Proprietary) / Lossless (Proprietary)
Algorithm
AirZip Proprietary Compression
Color Depth
8-bit (Indexed), 24-bit (RGB)
Developed by
AirZip, Inc.
Released
1999
Magic Bytes
Unknown (Proprietary)
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
Browser Support Comparison
| Browser | AZV | HTJ2K-(JPH) |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
AZV
AZV Strengths
- Historically allowed internet users to browse the web up to 5x faster over 56k dial-up modems by drastically reducing image payload sizes
- Officially registered in the IANA vendor tree, preventing MIME type conflicts on early web proxy servers
Limitations
- Completely obsolete in the modern broadband era
- Closed-source and proprietary, meaning no modern image manipulation libraries (like ImageMagick or libvips) can decode it
- Zero support in standard web browsers
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
When to choose which format
AZV
Use AZV when…
- Dial-up Web Acceleration
- Bandwidth Optimization (Historical)
- Legacy Proxy Servers
HTJ2K-(JPH)
Use HTJ2K-(JPH) when…
- Medical Imaging (DICOM)
- Geospatial Data
- Digital Cinema
- Professional Archiving