Image MIME Reference
JXL
JPEG XL
image/jxl
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of JPEG XL and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
JXL wins on browser support
Feature Support
| Feature | JXL | PTI |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | Yes | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG XL
image/jxl
Extension
.jxl
Container
ISOBMFF / JPEG XL Codestream
Compression
Lossy (VarDCT) / Lossless (Modular)
Algorithm
VarDCT (Variable block-size DCT)Modular (Predictive coding for lossless)
Color Depth
8-bit, 10-bit, 12-bit, 16-bit, 32-bit (Float)
Developed by
Joint Photographic Experts Group (JPEG)
Released
2021
Magic Bytes
FF 0A (Codestream) / 00 00 00 0C 4A 58 4C 20 0D 0A 87 0A (Container)
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 | JXL | PTI |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✓ 17+
|
✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
JXL
JXL Strengths
- Capable of losslessly recompressing legacy JPEG files, saving ~20% space while retaining perfect byte-for-byte restorability
- Highly superior progressive decoding (Saliency-driven), allowing recognizable images to load extremely fast on slow connections
- Outperforms WebP and competes favorably with AVIF, especially at high-fidelity settings and for complex textures/photography
- Royalty-free with an open-source reference implementation (libjxl)
Limitations
- Google's removal of JXL support from Chrome severely hindered its adoption as a universal web standard
- Lack of hardware decoding chips compared to video-derived codecs like AVIF (AV1)
- File parsing logic is complex due to the split between raw codestreams and ISOBMFF containers
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
JXL
Use JXL when…
- High-End Web Delivery (via Safari/Polyfills)
- HDR Photography
- Legacy JPEG Archiving
- Digital Art & Image Storage
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage