Image MIME Reference
JPX
JPEG 2000 Part 2 (Extended)
image/jpx
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of JPEG 2000 Part 2 (Extended) 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 | JPX | 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 2000 Part 2 (Extended)
image/jpx
Extension
.jpx.jpf
Container
ISOBMFF / JPX (ISO/IEC 15444-2)
Compression
Lossy / Lossless
Algorithm
Discrete Wavelet Transform (DWT)
Color Depth
8-bit, 16-bit, 32-bit, 38-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2002
Magic Bytes
00 00 00 0C 6A 50 20 20 0D 0A 87 0A ... 66 74 79 70 6A 70 78 20
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 | JPX | PTI |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
JPX
JPX Strengths
- Removes the color space limitations of baseline JP2, adding native support for CMYK, CIE Lab, and custom vendor color spaces
- Supports multiple codestreams in a single file, allowing for rich compositing and animation
- Enables fragmented files where image data and metadata can reside in separate physical files via data references
Limitations
- Extremely complex specification makes full software implementation rare, leading to compatibility issues
- Zero web browser support, rendering it unsuitable for public internet distribution
- Often overkill for standard imaging tasks where baseline JP2 or modern alternatives like AVIF suffice
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
JPX
Use JPX when…
- Prepress & Commercial Printing (CMYK)
- Geospatial Data
- Archival Preservation
- Medical Imaging
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage