Free webp to jpg
EN
Image MIME Reference
PJPEG

Progressive JPEG (Legacy IE Alias)

image/pjpeg
VS

GIMP Image Format

image/x-xcf
XCF

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

PJPEG wins on browser support

Feature Support

Feature PJPEG XCF
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No Yes
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
EXIF Metadata Yes Yes
ICC Color Profile Yes Yes
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 →
GIMP Image Format
image/x-xcf
Extension
.xcf
Container GIMP Hierarchical Chunk Container
Compression None / RLE (Run-Length Encoding) / Zlib / Deflate (In newer GIMP versions)
Algorithm
NoneRLEZlib
Color Depth 8-bit per channel, 16-bit per channel, 32-bit floating point
Developed by Spencer Kimball, Peter Mattis, and the GIMP Development Team
Released 1995
Magic Bytes
67 69 6D 70 20 78 63 66
Full XCF reference →

Browser Support Comparison

Browser PJPEG XCF
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
XCF

XCF Strengths

  • Preserves all non-destructive editing elements, layer hierarchies, masks, and alpha channels across GIMP sessions
  • Open and thoroughly documented specification within the open-source community, allowing third-party tools like Krita and ImageMagick to read project files
  • Reliable magic byte header prevents misidentification
Limitations
  • Massive file sizes because raw, unflattened layer bitmaps and masks are stored directly within the project archive
  • Completely proprietary to the GIMP ecosystem for deep editing; cannot be natively rendered or parsed by web browsers
  • Third-party software supporting XCF may occasionally struggle to render complex text layer adjustments or advanced layer blend modes identically to GIMP

When to choose which format

PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
XCF
Use XCF when…
  • GIMP Native Project Archival
  • Layered Photo Editing and Graphic Design
  • Intermediary Asset Preparation for Export

More comparisons

PJPEG vs ACES → XCF vs ACES → PJPEG vs APNG → XCF vs APNG → PJPEG vs AVCI → XCF vs AVCI → PJPEG vs AVCS → XCF vs AVCS → PJPEG vs AVIF → XCF vs AVIF → All comparisons →
Share this comparison