Image MIME Reference
3DS
Autodesk 3D Studio
image/x-3ds
VS
Progressive JPEG (Legacy IE Alias)
image/pjpeg
PJPEG
A complete technical comparison of Autodesk 3D Studio 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 | 3DS | PJPEG |
|---|---|---|
| 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
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)
Browser Support Comparison
| Browser | 3DS | PJPEG |
|---|---|---|
Chrome
|
✕ |
✓ All
|
Firefox
|
✕ |
✓ All
|
Safari
|
✕ |
✓ All
|
Edge
|
✕ |
✓ All
|
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)
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
3DS
Use 3DS when…
- Legacy 3D Model Exchange
- Low-Poly Game Assets
- Historical 3D Archival and Academic Use
PJPEG
Use PJPEG when…
- Legacy Internet Explorer File Uploads
- Progressive Image Rendering (Historical context)