Free webp to jpg
Image MIME Reference
3DS

Autodesk 3D Studio

image/x-3ds
VS

Radiance HDR

image/vnd.radiance
Radiance

A complete technical comparison of Autodesk 3D Studio and Radiance HDR — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature 3DS Radiance
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
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
Full 3DS reference →
Radiance HDR
image/vnd.radiance
Extension
.hdr.pic.rgbe.xyze
Container Radiance Information Header
Compression Run-Length Encoding (RLE) / Uncompressed
Algorithm
Adaptive Run-Length Encoding (RLE)
Color Depth 32-bit (8-bit per channel RGB + 8-bit shared Exponent)
Developed by Greg Ward (Lawrence Berkeley National Laboratory)
Released 1989
Magic Bytes
23 3F 52 41 44 49 41 4E 43 45
Full Radiance reference →

Browser Support Comparison

Browser 3DS Radiance
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE 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)
Radiance

Radiance Strengths

  • Universally supported by almost every 3D modeling software, renderer, and game engine in existence
  • RGBE encoding offers a brilliant balance between High Dynamic Range capability and small file size (compared to 32-bit float OpenEXR)
  • Simple, easy-to-parse ASCII header followed by straightforward RLE binary data
Limitations
  • Does not support alpha transparency (no way to store an isolated light source with a transparent background)
  • The shared exponent architecture can occasionally introduce banding or color artifacts in extreme edge cases compared to true 16-bit/32-bit floating-point formats like OpenEXR
  • Zero native browser support for 2D viewing

When to choose which format

3DS
Use 3DS when…
  • Legacy 3D Model Exchange
  • Low-Poly Game Assets
  • Historical 3D Archival and Academic Use
Radiance
Use Radiance when…
  • Image-Based Lighting (IBL)
  • 3D Environment Maps (HDRI Skydomes)
  • Lighting Simulation
  • VFX and CGI Rendering
Share this comparison