Image MIME Reference
3DS
Autodesk 3D Studio
image/x-3ds
VS
BlockFact Image
image/vnd.blockfact.facti
FACTI
A complete technical comparison of Autodesk 3D Studio and BlockFact Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | 3DS | FACTI |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| 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
BlockFact Image
image/vnd.blockfact.facti
Extension
.facti
Container
BlockFact Authenticated Container
Compression
Container (Inherits payload compression, e.g., JPEG/PNG)
Algorithm
None (Pass-through to embedded payload)
Color Depth
Inherited from payload
Developed by
BlockFact
Released
2025
Magic Bytes
Unknown (Proprietary Container)
Browser Support Comparison
| Browser | 3DS | FACTI |
|---|---|---|
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)
FACTI
FACTI Strengths
- Provides undeniable, mathematically verifiable proof of a photo's origin (time, location, and device) via the StarkNet blockchain [1.3.1]
- Privacy-first design utilizes zero-knowledge proofs (Groth16), meaning the actual image is never uploaded to a central server or blockchain
- Invisible watermarking ensures that even if the image is screenshotted or cropped, tampering can be detected
Limitations
- Lacks native rendering support in web browsers and standard image viewers, requiring specialized software to view
- Requires blockchain registration at the moment of capture, making it incompatible with existing legacy photos
- The proprietary nature of the container limits integration to environments supporting the BlockFact SDK
When to choose which format
3DS
Use 3DS when…
- Legacy 3D Model Exchange
- Low-Poly Game Assets
- Historical 3D Archival and Academic Use
FACTI
Use FACTI when…
- Journalism and Media Authentication
- Legal and Insurance Evidence
- AI Deepfake Prevention
- Content Provenance and Authorship