Image MIME Reference
AZV
AirZip Accelerator Image
image/vnd.airzip.accelerator.azv
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of AirZip Accelerator Image and High-Throughput JPEG 2000 Codestream — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | AZV | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | Yes |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
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 Codestream
image/jphc
Extension
.jhc
Container
None (Raw Codestream)
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
FF 4F FF 51
Browser Support Comparison
| Browser | AZV | HTJ2K-Codestream |
|---|---|---|
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-Codestream
HTJ2K-Codestream Strengths
- Extremely fast encoding and decoding capabilities due to the parallelizable block coder
- Minimal file overhead since it lacks container headers and metadata
- Ideal for streaming applications or embedded systems where parsing a full container is unnecessary
Limitations
- Lacks standard metadata support (like EXIF, XMP, or ICC color profiles) since there is no container structure
- Zero native web browser compatibility
- Difficult to distinguish from standard JPEG 2000 codestreams without deeply parsing the internal marker segments
When to choose which format
AZV
Use AZV when…
- Dial-up Web Acceleration
- Bandwidth Optimization (Historical)
- Legacy Proxy Servers
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems