Image MIME Reference
3DS
Autodesk 3D Studio
image/x-3ds
VS
JPEG Stereo Image
image/x-jps
JPS
A complete technical comparison of Autodesk 3D Studio 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 | 3DS | JPS |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | Yes | ✕ No |
| Progressive Loading | ✕ No | Yes |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | ✕ No | Yes |
Autodesk 3D Studio
image/x-3ds
Extension
.3ds
Container
Binary Chunk System
Compression
Uncompressed Binary (Chunk-based)
Algorithm
None
Color Depth
Not Applicable (Stores 3D geometry and material RGB definitions)
Developed by
Autodesk (The Yost Group)
Released
1990
Magic Bytes
4D 4D
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 | 3DS | JPS |
|---|---|---|
Chrome
|
✕ |
✓ 1
|
Firefox
|
✕ |
✓ 1
|
Safari
|
✕ |
✓ 1
|
Edge
|
✕ |
✓ 12
|
IE (Legacy)
|
✕ |
✓
|
3DS
3DS Strengths
- Nearly universal support; practically every 3D modeling application created in the last 30 years can read and write 3DS files
- Extremely simple, well-documented binary structure that is trivial to parse for custom rendering engines
Limitations
- Hard limit of 65,536 vertices and polygons per mesh due to 16-bit addressing
- Enforces archaic 8.3 MS-DOS filename length restrictions for all linked texture files
- Lacks support for modern 3D concepts like skeletal animation (rigging), normal mapping, and physically based rendering (PBR)
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
3DS
Use 3DS when…
- Legacy 3D Model Exchange
- Low-Poly Game Assets
- Historical 3D Archival and Academic Use
JPS
Use JPS when…
- Stereoscopic 3D Photography
- Virtual Reality (VR) Image Galleries
- Cross-eye / Parallel Stereograms