Image MIME Reference
JPM
JPEG 2000 Compound Image File Format
image/jpm
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of JPEG 2000 Compound Image File Format 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 | JPM | PTI |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG 2000 Compound Image File Format
image/jpm
Extension
.jpm.jpgm
Container
ISOBMFF / JPM (ISO/IEC 15444-6)
Compression
Lossy / Lossless / Mixed Raster Content (MRC)
Algorithm
JPEG 2000JBIG2JPEGMMR
Color Depth
1-bit (Text/Masks), 8-bit, 16-bit, 24-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2003
Magic Bytes
00 00 00 0C 6A 50 20 20 0D 0A 87 0A ... 66 74 79 70 6A 70 6D 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 | JPM | PTI |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
JPM
JPM Strengths
- Highly optimized for scanned documents, drastically reducing file sizes without sacrificing the readability of text or the quality of embedded photos
- Supports multi-page documents within a single file
- Object-based architecture allows for complex layout representation and independent extraction of elements
Limitations
- Failed to achieve widespread adoption, largely being overshadowed by PDF/A and DjVu
- Zero native web browser compatibility
- Requires complex, specialized software to properly encode and decode the multi-layered MRC structure
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
JPM
Use JPM when…
- Scanned Document Archiving
- Mixed Raster Content (MRC) Imaging
- Digital Libraries
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage