Image MIME Reference
3DS
Autodesk 3D Studio
image/x-3ds
VS
JPEG Network Graphics
image/x-jng
JNG
A complete technical comparison of Autodesk 3D Studio and JPEG Network Graphics — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | 3DS | JNG |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| 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 Network Graphics
image/x-jng
Extension
.jng
Container
PNG-style Chunk Structure (JHDR, JDAT, IDAT, IEND)
Compression
Lossy (JPEG/DCT for color) / Lossless (Deflate for alpha mask)
Algorithm
JPEG (Discrete Cosine Transform)Deflate (LZ77)
Color Depth
8-bit, 12-bit, 24-bit (RGB), 32-bit (RGBA)
Developed by
MNG Development Group (Glenn Randers-Pehrson et al.)
Released
2001
Magic Bytes
8B 4A 4E 47 0D 0A 1A 0A
Browser Support Comparison
| Browser | 3DS | JNG |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
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)
JNG
JNG Strengths
- Solved a massive technical hurdle in the early 2000s by combining high-compression lossy photographic data with crisp, 8-bit alpha transparency
- Utilized the highly robust, extensible chunk-based architecture of the PNG format
- Provided an excellent, bandwidth-saving alternative to massive 32-bit transparent PNGs for web design
Limitations
- Failed to achieve critical mass; browser vendors largely abandoned the MNG/JNG standard due to implementation complexity
- Completely obsolete today, having been superseded by natively supported, superior formats like WebP, AVIF, and HEIC
- Decoding requires a hybrid engine that can parse PNG chunks while simultaneously decoding a JPEG stream and a Deflate stream, complicating software support
When to choose which format
3DS
Use 3DS when…
- Legacy 3D Model Exchange
- Low-Poly Game Assets
- Historical 3D Archival and Academic Use
JNG
Use JNG when…
- Embedded frames in MNG animations
- Historical web graphics requiring lossy compression with transparency