Free webp to jpg
Image MIME Reference
PJPEG

Progressive JPEG (Legacy IE Alias)

image/pjpeg
VS

PTI Image (Personal/Vanity Tree)

image/prs.pti
PTI

A complete technical comparison of Progressive JPEG (Legacy IE Alias) and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

PJPEG wins on browser support

Feature Support

Feature PJPEG 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
Progressive JPEG (Legacy IE Alias)
image/pjpeg
Extension
.jpeg.jpg.pjpeg.pjp.jfif
Container JPEG (ISO/IEC 10918-1)
Compression Lossy (DCT)
Algorithm
Discrete Cosine Transform (DCT)
Color Depth 8-bit, 12-bit
Developed by Joint Photographic Experts Group / Microsoft (Alias)
Released 1992
Magic Bytes
FF D8 FF E0 (JFIF) / FF D8 FF E1 (Exif)
Full PJPEG reference →
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
Full PTI reference →

Browser Support Comparison

Browser PJPEG PTI
Chrome Chrome
✓ All
Firefox Firefox
✓ All
Safari Safari
✓ All
Edge Edge
✓ All
IE IE (Legacy)
PJPEG

PJPEG Strengths

  • Progressive JPEGs (which this MIME type attempted to describe) provide excellent perceived loading speeds on slow connections by rendering a low-resolution preview first
  • Files sent with this MIME type are fully backwards compatible with any standard JPEG decoder
Limitations
  • It is a non-standard MIME type that violates IANA specifications
  • Causes strict file upload validation scripts to fail if not explicitly whitelisted or mapped
  • Creates unnecessary confusion, as the official image/jpeg MIME type already fully encompasses progressive encoding
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

PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
PTI
Use PTI when…
  • Legacy Application Specific Workflows
  • Proprietary Image Storage
Share this comparison