Image MIME Reference
J2C
JPEG 2000 Codestream
image/j2c
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of 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 | J2C | 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 |
JPEG 2000 Codestream
image/j2c
Extension
.j2c.j2k.jpc
Container
None (Raw Bitstream)
Compression
JPEG 2000 (Discrete Wavelet Transform) / Lossless / Lossy
Algorithm
Discrete Wavelet Transform (DWT)
Color Depth
8-bit, 10-bit, 12-bit, 16-bit (Per Channel)
Developed by
Joint Photographic Experts Group (JPEG)
Released
2000
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 | J2C | PTI |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
J2C
J2C Strengths
- Provides state-of-the-art wavelet compression for high-end professional workflows (Digital Cinema)
- Allows for highly efficient progressive decoding (by resolution or quality layer) natively within the stream
- Supports lossless mathematical compression and high bit-depths (up to 16-bit per channel) natively
Limitations
- Lacks a standard container to store color space info or metadata, requiring external systems (like MXF or DICOM) to map colors correctly
- Extremely computationally expensive to encode and decode compared to standard DCT-based JPEG
- Zero web browser support
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
J2C
Use J2C when…
- Digital Cinema Packages (DCP)
- Medical Imaging (DICOM Payloads)
- Professional Broadcast and Archiving
- Embedded Hardware Encoding
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage