Free webp to jpg
Image MIME Reference
JPEG-XS-Codestream

JPEG XS Codestream

image/jxsc
VS

Progressive JPEG (Legacy IE Alias)

image/pjpeg
PJPEG

A complete technical comparison of JPEG XS Codestream 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 JPEG-XS-Codestream PJPEG
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No Yes
HDR Support Yes ✕ No
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
JPEG XS Codestream
image/jxsc
Extension
.jxsc.jxs
Container None (Raw Codestream)
Compression Lossy (Visually Lossless) / Mathematically Lossless
Algorithm
JPEG XS (ISO/IEC 21122-1)
Color Depth 8-bit, 10-bit, 12-bit, 14-bit, 16-bit
Developed by Joint Photographic Experts Group (JPEG) / intoPIX
Released 2019
Magic Bytes
FF 10
Full JPEG-XS-Codestream 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 JPEG-XS-Codestream PJPEG
Chrome Chrome
✓ All
Firefox Firefox
✓ All
Safari Safari
✓ All
Edge Edge
✓ All
IE IE (Legacy)
JPEG-XS-Codestream

JPEG-XS-Codestream Strengths

  • Eliminates container overhead, maximizing parsing speed and minimizing latency to fractions of a millisecond
  • Highly optimized for direct hardware implementation in FPGAs and ASICs
  • Perfect for continuous data streaming over IP networks without needing to establish file headers
Limitations
  • Lacks standard container metadata (EXIF, XMP, ICC profiles), meaning color space and orientation data must be handled externally or out-of-band
  • Zero support in web browsers or standard consumer operating systems
  • Often requires specialized broadcast hardware or custom software libraries to decode
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

JPEG-XS-Codestream
Use JPEG-XS-Codestream when…
  • Hardware Decoding Pipelines (FPGA/ASIC)
  • Live Broadcast Infrastructure
  • Video over IP Transport
  • Embedded Camera Systems
PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
Share this comparison