MAX File Documentation

---

Technical details

Feature	Value
Full name	3ds Max scene file
File extension	.max
MIME type	application/octet-stream
Format type	Proprietary binary 3D scene (project file)
Developer	Autodesk (originally Yost Group / Discreet)
Introduced	1996 (3D Studio MAX 1.0, Windows NT)
Container / base format	Microsoft OLE2 Compound File (Structured Storage)
Magic number	D0 CF 11 E0 A1 B1 1A E1
Byte order	Little-endian (OLE2 header)
Open standard	No — proprietary and undocumented
Internal layout	Version-specific, not published
Contents	Geometry, materials, lights, cameras, animation, modifiers
Third-party read	None — only 3ds Max opens it natively
Version compatibility	Forward-incompatible; “Save As Previous” goes back a few releases only
Scripting	MAXScript embedded in scenes (a security consideration)
Platform	Windows only (no macOS/Linux 3ds Max)
Free preview	Autodesk Viewer (web) — view only
Export targets	.fbx, .obj, .3ds, .gltf, .stl, .dwg
Related extensions	.3ds, .fbx, .obj, .ase, .blend
Specification	autodesk.com/products/3ds-max/overview

What is a MAX file?

A .max file is the native scene format of Autodesk 3ds Max, the 3D modelling and animation package first released in 1996 as 3D Studio MAX 1.0 for Windows NT (built by the Yost Group, later Discreet, now Autodesk). It is not a mesh or a single 3D object. It is a complete project file that can hold everything in a scene at once: all geometry, materials and texture assignments, lights, cameras, animation keyframes, the modifier stack, particle and physics setups, render settings and scene references. 3ds Max is a mainstream tool for game art, architectural visualisation, film and TV VFX and product rendering, so .max files circulate as deliverables throughout those pipelines.

Two hard facts govern how anyone deals with a .max. It is proprietary and effectively undocumented, so no third-party application reads it natively; and it is forward-incompatible, so a scene saved in a newer 3ds Max will not open in an older one. Everything below follows from those two constraints.

The OLE2 compound-document container

A .max is physically a Microsoft OLE2 Compound File, also called Structured Storage or Compound File Binary. That is a small filesystem packed inside one file: it has storages (the equivalent of directories) and streams (the equivalent of files), organised through a FAT-like allocation table and a directory of named entries. The same container underpins legacy .doc and .xls, which is why a .max begins with the identical 8-byte signature:

offset 0:  D0 CF 11 E0 A1 B1 1A E1   OLE2 / Compound File header
           ... 512-byte header: sector size, FAT sector list,
               directory start sector, MiniFAT ...
           directory entries name the storages and streams
           inside which 3ds Max writes the scene data

The container is standard and readable, tools and libraries can enumerate the streams of any OLE2 file, but that only exposes the named streams, not their meaning. The actual scene, the geometry, the modifier stack, the animation, is serialised inside those streams in a layout Autodesk has never published, and that layout changes between releases. So while you can prove a file is an OLE2 compound document and even list its streams, you cannot reconstruct the scene without 3ds Max. This is the technical reason there is no free .max reader: the wrapper is open, the contents are not.

What the scene actually holds

Inside the container, a .max aggregates the entire authoring state of a project. It is worth being concrete about the categories, because it explains why the files are large and why simple mesh formats cannot represent them:

Scene component	What it stores
Geometry	Every object with its full modifier stack, not just final vertices
Materials & maps	Material definitions and texture assignments (paths to external images)
Lights & cameras	Lighting rigs, camera setups and their animation
Animation	Keyframes, controllers and constraints on any animatable value
Render / scene settings	Renderer config, environment, scene metadata, external references

The modifier stack is the point that most distinguishes a .max from an exported mesh. 3ds Max keeps geometry as a base object plus an ordered list of non-destructive modifiers (bend, turbosmooth, edit poly and so on). The .max stores that stack, so the object stays fully editable; an OBJ or STL export instead bakes the stack down to plain triangles and throws the history away. Note too that materials reference external texture image files by path, so a .max moved to another machine without its texture folder shows missing maps.

Forward incompatibility and the “won’t open” error

The most common failure with a .max is a version mismatch. A scene saved in a newer 3ds Max generally will not open in an older one, producing a “file save version” error, because the internal stream layout evolves each release and older code cannot parse newer structures. 3ds Max offers a “Save As Previous” option, but it only reaches back a limited number of versions, not arbitrarily far. The practical fix when a collaborator’s file will not open is to ask them to re-save to your specific version, or to update 3ds Max. Before assuming a version problem, it is worth confirming the file is even a 3ds Max scene at all, since the .max extension is heavily reused (older PCB/CAD layout tools, photo and album apps, game data). A .max that did not come from a 3D pipeline may belong to an entirely different program, and the OLE2 header is the quick check for the 3ds Max case.

Moving a scene out: export, do not convert

Because nothing but 3ds Max reads a .max, every route to another application goes through 3ds Max’s exporters, not a standalone converter. The recommended interchange is FBX (File > Export > FBX), which preserves meshes, materials, cameras, lights and animation and imports cleanly into Blender, Maya, Unreal and Unity. OBJ carries geometry plus a companion .mtl for basic materials but drops animation; the legacy .3ds format maximises compatibility with old tools at the cost of modern features; glTF/GLB targets real-time and web engines with PBR materials; and STL produces a plain triangle soup for 3D printing (check the mesh is watertight first). All of these require access to 3ds Max, and a free trial or student licence is enough to perform the export. There is no .max-to-.blend converter: Blender cannot read .max, so the path is always to export FBX or OBJ from 3ds Max first, then import that into Blender.

For someone who only needs to look at a scene without a licence, Autodesk’s web-based Autodesk Viewer previews many .max files in a browser. It is a viewer, not a converter: it will not export editable data, but it answers “what is in this file” without installing anything.

References

• Autodesk — 3ds Max overview
• Autodesk — Malware in 3ds Max (Safe Scene Script Execution)
• Wikipedia — Autodesk 3ds Max

Feedback

Was this page helpful?

Yes No

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.