Image MIME Reference
JPS
JPEG Stereo Image
image/x-jps
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of JPEG Stereo Image and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
JPS wins on browser support
Feature Support
| Feature | JPS | PTI |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG Stereo Image
image/x-jps
Extension
.jps
Container
JPEG (JFIF/Exif)
Compression
Lossy (JPEG/DCT)
Algorithm
JPEG (Discrete Cosine Transform)
Color Depth
8-bit (Grayscale), 24-bit (RGB)
Developed by
Stereoscopic Community (Unofficial Standard)
Released
1990
Magic Bytes
FF D8 FF
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 | JPS | PTI |
|---|---|---|
Chrome
|
✓ 1
|
✕ |
Firefox
|
✓ 1
|
✕ |
Safari
|
✓ 1
|
✕ |
Edge
|
✓ 12
|
✕ |
IE (Legacy)
|
✓
|
✕ |
JPS
JPS Strengths
- 100% backward compatible with every standard 2D image viewer and web browser (which simply display the two halves side-by-side)
- Inherits JPEG's excellent lossy compression, resulting in small file sizes ideal for web transmission
- Extremely easy to generate programmatically by simply stitching two JPEG images side-by-side onto a wider canvas
Limitations
- Lack of a dedicated metadata standard means viewing software has to guess whether the layout is 'cross-eyed' (right eye left, left eye right) or 'parallel' (left eye left, right eye right), occasionally causing inverted depth
- Suffers from JPEG compression artifacts, which can break the stereoscopic illusion if compression noise differs between the left and right eyes
- Superseded in consumer electronics by the MPO (Multi-Picture Object) format, which stacks separate full-resolution JPEGs rather than squishing them side-by-side
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
JPS
Use JPS when…
- Stereoscopic 3D Photography
- Virtual Reality (VR) Image Galleries
- Cross-eye / Parallel Stereograms
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage