Free webp to jpg
Image MIME Reference
JPS

JPEG Stereo Image

image/x-jps
VS

Khronos Texture

image/ktx
KTX

A complete technical comparison of JPEG Stereo Image and Khronos Texture — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

JPS wins on browser support

Feature Support

Feature JPS KTX
Transparency (Alpha) ✕ No Yes
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
JPEG Stereo Image
image/x-jps
Extension
.jps
Container JPEG (JFIF/Exif)
Compression Lossy (JPEG/DCT)
Algorithm
JPEG (Discrete Cosine Transform)
Color Depth 8-bit (Grayscale), 24-bit (RGB)
Developed by Stereoscopic Community (Unofficial Standard)
Released 1990
Magic Bytes
FF D8 FF
Full JPS reference →
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 →

Browser Support Comparison

Browser JPS KTX
Chrome Chrome
✓ 1
Firefox Firefox
✓ 1
Safari Safari
✓ 1
Edge Edge
✓ 12
IE IE (Legacy)
JPS

JPS Strengths

  • 100% backward compatible with every standard 2D image viewer and web browser (which simply display the two halves side-by-side)
  • Inherits JPEG's excellent lossy compression, resulting in small file sizes ideal for web transmission
  • Extremely easy to generate programmatically by simply stitching two JPEG images side-by-side onto a wider canvas
Limitations
  • Lack of a dedicated metadata standard means viewing software has to guess whether the layout is 'cross-eyed' (right eye left, left eye right) or 'parallel' (left eye left, right eye right), occasionally causing inverted depth
  • Suffers from JPEG compression artifacts, which can break the stereoscopic illusion if compression noise differs between the left and right eyes
  • Superseded in consumer electronics by the MPO (Multi-Picture Object) format, which stacks separate full-resolution JPEGs rather than squishing them side-by-side
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)

When to choose which format

JPS
Use JPS when…
  • Stereoscopic 3D Photography
  • Virtual Reality (VR) Image Galleries
  • Cross-eye / Parallel Stereograms
KTX
Use KTX when…
  • Real-time 3D Graphics
  • WebGL / WebGPU Applications
  • Mobile Games
  • Virtual/Augmented Reality (VR/AR)
Share this comparison