Free webp to jpg
Image MIME Reference
KTX

Khronos Texture

image/ktx
VS

Progressive JPEG (Legacy IE Alias)

image/pjpeg
PJPEG

A complete technical comparison of Khronos Texture 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 KTX 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
Khronos Texture
image/ktx
Extension
.ktx
Container KTX (Khronos Texture 1.1)
Compression Uncompressed / GPU Compressed (ASTC, ETC, BCn, PVRTC)
Algorithm
ASTCETC1 / ETC2BCn (DXT)PVRTCBasis Universal (in KTX2)
Color Depth 8-bit, 16-bit, 32-bit (Integer/Float)
Developed by Khronos Group
Released 2010
Magic Bytes
AB 4B 54 58 20 31 31 BB 0D 0A 1A 0A
Full KTX 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 KTX PJPEG
Chrome Chrome
✓ All
Firefox Firefox
✓ All
Safari Safari
✓ All
Edge Edge
✓ All
IE IE (Legacy)
KTX

KTX Strengths

  • Enables direct-to-GPU texture uploading, drastically reducing load times and CPU overhead in 3D applications
  • Supports complex texture types natively (mipmaps, cubemaps, 3D volumes, texture arrays)
  • Standardized across major Khronos APIs (OpenGL, Vulkan, WebGL) unlike vendor-specific formats like DDS
Limitations
  • Requires custom JavaScript loaders to parse and display on the web
  • Zero native support in consumer image viewers or 2D photo editing software
  • Format fragmentation: a KTX file containing an ASTC payload will fail to render on hardware that only supports BCn compression (KTX2 and Basis Universal solve this)
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

KTX
Use KTX when…
  • Real-time 3D Graphics
  • WebGL / WebGPU Applications
  • Mobile Games
  • Virtual/Augmented Reality (VR/AR)
PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
Share this comparison