Image MIME Reference
3DS
Autodesk 3D Studio
image/x-3ds
VS
Kodak KDC Raw Image
image/x-kodak-kdc
Kodak-KDC
A complete technical comparison of Autodesk 3D Studio and Kodak KDC Raw Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | 3DS | Kodak-KDC |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | Yes | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| 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
Kodak KDC Raw Image
image/x-kodak-kdc
Extension
.kdc
Container
TIFF/EP
Compression
Uncompressed / Proprietary Lossless
Algorithm
NoneLossless JPEG (ITU-T81)Proprietary Kodak Compression
Color Depth
10-bit, 12-bit (Per Channel)
Developed by
Eastman Kodak Company
Released
1995
Magic Bytes
49 49 2A 00 or 4D 4D 00 2A
Browser Support Comparison
| Browser | 3DS | Kodak-KDC |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
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)
Kodak-KDC
Kodak-KDC Strengths
- Preserves original raw sensor data, allowing modern demosaicing software to extract significantly more detail and dynamic range than the camera's built-in JPEG engine could at the time
- Utilizes the standard TIFF container structure, ensuring broad compatibility with open-source decoding libraries (like LibRaw)
Limitations
- Completely obsolete proprietary format tied to a defunct line of consumer digital cameras
- Subject to widespread misidentification by automated MIME detection libraries due to structural similarities with standard TIFFs
- Cannot be natively viewed in web browsers or standard operating system image viewers without specialized decoders
When to choose which format
3DS
Use 3DS when…
- Legacy 3D Model Exchange
- Low-Poly Game Assets
- Historical 3D Archival and Academic Use
Kodak-KDC
Use Kodak-KDC when…
- Vintage Digital Photography Archival
- Kodak DC and EasyShare P-Series Raw Post-Processing
- Historical Imaging Research