Image MIME Reference
HTJ2K-Codestream
High-Throughput JPEG 2000 Codestream
image/jphc
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of High-Throughput JPEG 2000 Codestream and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | HTJ2K-Codestream | PTI |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
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
PTI Image (Personal/Vanity Tree)
image/prs.pti
Extension
.pti
Container
Proprietary
Compression
Unknown / Proprietary
Algorithm
Unknown
Color Depth
Unknown
Developed by
Jürn Laun
Released
1999
Magic Bytes
Unknown
Browser Support Comparison
| Browser | HTJ2K-Codestream | PTI |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
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
PTI
PTI Strengths
- Provided a registered MIME type namespace for a specific application's proprietary image format without conflicting with standard web types
Limitations
- Completely undocumented and unsupported in modern ecosystems
- Zero web browser compatibility
- Falls into the 'vanity' tree, making it irrelevant for standard cross-platform data exchange
When to choose which format
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage