3ds Max

The native scene format of Autodesk 3ds Max, storing 3D geometry, materials, cameras, lights, animation, and modifier stacks in a proprietary binary structure tied to a specific application version.

Extension

.max

Full name

Autodesk 3ds Max Scene File

Introduced

1996 (as 3D Studio MAX, from Kinetix)

Vendor

Autodesk

What is inside the container

A .max file bundles editable-mesh/poly geometry, the modifier stack history, scene hierarchy, material and map assignments, cameras, lights, and keyframe animation data in one binary file. It is not an exchange format: the internal chunk structure changes between major 3ds Max releases, and files are read reliably only by the same or a newer version of 3ds Max itself, unlike open interchange formats such as FBX or OBJ that the same scene can also be exported to.

How to open it

Windows Autodesk 3ds Max (the only application that opens .max files natively; requires a paid subscription)

Windows/macOS/Linux (viewing only) Autodesk Viewer or third-party tools like Chaos' Corona/V-Ray asset browsers can generate thumbnails from associated render output, but cannot open the .max file itself

Any OS Export from 3ds Max to FBX, OBJ, or glTF for use in Blender, Unreal Engine, Unity, or other 3D tools that cannot read .max directly

DAM/asset pipeline Batch conversion via 3ds Max's MAXScript or Python scripting API, run headless on a render-node license, to generate FBX/glTF proxies and PNG thumbnails for indexing

For archives

Because .max is closed, version-locked, and undocumented, a DAM should never treat it as the sole archival copy of a 3D asset: keep the .max as the editable source but also export and store an open interchange format (FBX or glTF/OBJ) alongside it for long-term access and cross-application reuse. Render a static image or turntable preview at ingest time, since no lightweight viewer can preview .max files without a full 3ds Max license.

The .max format dates to 1996, when Autodesk’s Kinetix division shipped 3D Studio MAX as a ground-up, Windows NT-native rewrite of the DOS-based 3D Studio line. The new application replaced the old .3ds scene format with .max, a binary container built around 3ds Max’s modifier-stack architecture, which records not just final geometry but the ordered history of edits (bevels, bends, booleans) applied to it. That editability is the format’s main value and also its main liability: because the chunk layout is proprietary and shifts with each major release, a .max file saved in a newer version routinely cannot be opened in an older one.

For a DAM, .max sits firmly in the “native source, not exchange” category alongside PSD or Adobe Illustrator files: valuable to keep as the editable master for a 3D artist, but useless for anyone downstream without a matching 3ds Max license. Studios and product-visualization teams that store .max libraries typically pair every file with an exported FBX or glTF proxy and a rendered still, so the asset can be previewed, searched, and reused without launching 3ds Max at all — the same pattern picajet and other DAM tools apply to any closed, application-locked source file.

Frequently asked

Can a DAM generate a thumbnail preview of a .max file automatically?

Not without 3ds Max itself. There is no independent parser for the format, so DAM platforms either shell out to a licensed, headless 3ds Max instance to render a preview image, or rely on a preview image the artist exported and uploaded alongside the file.

Why won't a .max file saved in the newest 3ds Max open in an older version?

The internal chunk structure changes across major releases and Autodesk does not guarantee backward compatibility; older 3ds Max builds simply don't recognize newer chunk types, so the file fails to open or loads with missing data.

Should a DAM store .max as the only copy of a 3D asset?

No. Because it's a closed, version-locked format, best practice is to keep .max as the editable source and also store an open export (FBX, glTF, or OBJ) so the asset remains usable if 3ds Max access is ever lost or the license lapses.

Does .max store textures and materials inside the file?

Material definitions and file-path references are stored inside the .max file, but the actual texture bitmaps are usually external files the scene links to, so a DAM needs to track and bundle those dependencies too, not just the .max file alone.

What's the difference between .max and .3ds?

.3ds is the older, simpler DOS-era 3D Studio format with tight limits on object/material counts and no modifier history; .max is the modern native format with full editability, introduced when 3D Studio MAX replaced 3D Studio DOS in 1996.

Can Blender or Maya open a .max file directly?

No. Neither has native .max support; the asset must be exported from 3ds Max to a neutral format like FBX or OBJ first, which is why many 3D-asset DAM workflows standardize on FBX as the shared preview/exchange format.

Is .max a good format for long-term digital preservation?

No — its closed specification and version fragility make it a poor archival target on its own. Preservation guidance for proprietary CAD/3D formats generally recommends pairing the native file with an open, documented export for long-term access.

How does a DAM know which 3ds Max version a .max file needs?

The version isn't exposed cleanly in metadata the way a document format's version might be; most teams track it manually in the DAM's asset metadata fields or rely on a naming convention, since opening the file in the wrong version is the only way to confirm compatibility.

Sources

3D Studio MAX was released by Kinetix, Autodesk's multimedia division, in 1996 as a Windows NT-native rewrite that replaced 3D Studio DOS. checked 2026-08-07 — Wikipedia — Autodesk 3ds Max
The .max format was introduced as the native scene format for 3D Studio MAX, distinct from the earlier DOS-era .3ds format. checked 2026-08-07 — Wikipedia — .3ds