Image MIME Reference
J2C
JPEG 2000 Codestream
image/j2c
VS
JPEG Stereo Image
image/x-jps
JPS
A complete technical comparison of JPEG 2000 Codestream and JPEG Stereo Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
JPS wins on browser support
Feature Support
| Feature | J2C | JPS |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | Yes |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | ✕ No | Yes |
JPEG 2000 Codestream
image/j2c
Extension
.j2c.j2k.jpc
Container
None (Raw Bitstream)
Compression
JPEG 2000 (Discrete Wavelet Transform) / Lossless / Lossy
Algorithm
Discrete Wavelet Transform (DWT)
Color Depth
8-bit, 10-bit, 12-bit, 16-bit (Per Channel)
Developed by
Joint Photographic Experts Group (JPEG)
Released
2000
Magic Bytes
FF 4F FF 51
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
Browser Support Comparison
| Browser | J2C | JPS |
|---|---|---|
Chrome
|
✕ |
✓ 1
|
Firefox
|
✕ |
✓ 1
|
Safari
|
✕ |
✓ 1
|
Edge
|
✕ |
✓ 12
|
IE (Legacy)
|
✕ |
✓
|
J2C
J2C Strengths
- Provides state-of-the-art wavelet compression for high-end professional workflows (Digital Cinema)
- Allows for highly efficient progressive decoding (by resolution or quality layer) natively within the stream
- Supports lossless mathematical compression and high bit-depths (up to 16-bit per channel) natively
Limitations
- Lacks a standard container to store color space info or metadata, requiring external systems (like MXF or DICOM) to map colors correctly
- Extremely computationally expensive to encode and decode compared to standard DCT-based JPEG
- Zero web browser support
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
When to choose which format
J2C
Use J2C when…
- Digital Cinema Packages (DCP)
- Medical Imaging (DICOM Payloads)
- Professional Broadcast and Archiving
- Embedded Hardware Encoding
JPS
Use JPS when…
- Stereoscopic 3D Photography
- Virtual Reality (VR) Image Galleries
- Cross-eye / Parallel Stereograms