Free webp to jpg
Image MIME Reference
JXL

JPEG XL

image/jxl
VS

Progressive JPEG (Legacy IE Alias)

image/pjpeg
PJPEG

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

PJPEG wins on browser support

Feature Support

Feature JXL PJPEG
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading Yes Yes
HDR Support Yes ✕ No
EXIF Metadata Yes Yes
ICC Color Profile Yes Yes
JPEG XL
image/jxl
Extension
.jxl
Container ISOBMFF / JPEG XL Codestream
Compression Lossy (VarDCT) / Lossless (Modular)
Algorithm
VarDCT (Variable block-size DCT)Modular (Predictive coding for lossless)
Color Depth 8-bit, 10-bit, 12-bit, 16-bit, 32-bit (Float)
Developed by Joint Photographic Experts Group (JPEG)
Released 2021
Magic Bytes
FF 0A (Codestream) / 00 00 00 0C 4A 58 4C 20 0D 0A 87 0A (Container)
Full JXL reference →
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 →

Browser Support Comparison

Browser JXL PJPEG
Chrome Chrome
✓ All
Firefox Firefox
✓ All
Safari Safari
✓ 17+
✓ All
Edge Edge
✓ All
IE IE (Legacy)
JXL

JXL Strengths

  • Capable of losslessly recompressing legacy JPEG files, saving ~20% space while retaining perfect byte-for-byte restorability
  • Highly superior progressive decoding (Saliency-driven), allowing recognizable images to load extremely fast on slow connections
  • Outperforms WebP and competes favorably with AVIF, especially at high-fidelity settings and for complex textures/photography
  • Royalty-free with an open-source reference implementation (libjxl)
Limitations
  • Google's removal of JXL support from Chrome severely hindered its adoption as a universal web standard
  • Lack of hardware decoding chips compared to video-derived codecs like AVIF (AV1)
  • File parsing logic is complex due to the split between raw codestreams and ISOBMFF containers
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

When to choose which format

JXL
Use JXL when…
  • High-End Web Delivery (via Safari/Polyfills)
  • HDR Photography
  • Legacy JPEG Archiving
  • Digital Art & Image Storage
PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
Share this comparison