How to Open .max Files in Cinema 4D

Can Cinema 4D Open .max Files?

The short answer is no. Cinema 4D has no built-in importer for .max files and Maxon has never announced plans to add one. This isn't an oversight — it's a technical limitation rooted in how .max files work.

Cinema 4D supports importing a wide range of formats: FBX, OBJ, Alembic, USD, glTF, STEP, IGES, and more. But .max is conspicuously absent from that list. The reason is that .max is not an interchange format — it's Autodesk's proprietary project format, and it was never intended to be read by anything other than 3ds Max itself.

If you try to drag a .max file into Cinema 4D, nothing happens. There's no error message, no partial import, nothing. Cinema 4D simply doesn't recognize the format. To get your scene across, you need a different approach entirely.

Why .max Is a Closed Format

Autodesk 3ds Max stores everything about a scene in a single proprietary binary container: geometry, materials, modifiers, plugin data, render settings, animation controllers, and the entire scene graph hierarchy. The .max format has no public specification — Autodesk has never documented its internal structure, and the format changes between 3ds Max versions.

This is fundamentally different from interchange formats like FBX or OBJ, which are designed to transfer specific types of data between applications. The .max file is a serialized snapshot of the entire 3ds Max runtime state, including references to third-party plugins.

That means your .max file contains data that only makes sense inside 3ds Max:

• Corona materials — CoronaPhysicalMtl, CoronaBitmap, CoronaColorCorrect, CoronaMixMtl, CoronaLayeredMtl, and 20+ other material and shader types with all their interconnected parameters.
• V-Ray materials — VRayMtl, VRayBlendMtl, VRayFastSSS2, VRayLightMtl, and the full V-Ray shading tree with BRDF models, coat layers, and subsurface scattering.
• Render settings — GI solver configuration, denoiser settings, tone mapping curves, LUT files, progressive rendering limits, and environment overrides.
• Plugin-specific data — ForestPack scatter objects, RailClone parametric geometry, Tyflow particle systems, Phoenix FD simulations — all stored as plugin-native binary blobs.

None of this data is accessible without 3ds Max itself. The only way to read a .max file is through the 3ds Max SDK, running inside an active 3ds Max session.

Method 1: FBX Export (and Why It Fails)

The traditional approach to getting a .max scene into Cinema 4D looks like this: open the .max file in 3ds Max, go to File → Export, choose FBX, import the FBX into Cinema 4D. It sounds straightforward, but the result is almost always disappointing.

FBX is a geometry interchange format. It handles meshes, bones, and basic animation well. But it was never designed to carry renderer-specific material graphs. When you export a Corona or V-Ray scene via FBX, here's what you lose:

• All Corona and V-Ray materials — FBX has no representation for CoronaPhysicalMtl, VRayMtl, or any renderer-specific material. They're either replaced with empty Standard materials or stripped entirely.
• Node graph connections — A CoronaBitmap feeding through CoronaColorCorrect into a roughness slot? The entire shader tree is flattened. FBX cannot represent nested node graphs.
• Multi/Sub-Object assignments — Material IDs that assign different materials to different faces of a single object are lost or collapsed. You get one material per object at best.
• Render settings — GI solver, denoiser, tone mapping, exposure — none of it is part of the FBX spec. You copy these values by hand from screenshots.
• Texture paths — FBX partially embeds paths but breaks on UNC paths, network drives, and cloud-synced folders. You spend 30+ minutes relinking bitmaps.
• Corona and V-Ray lights — Converted to generic point/spot lights. Shape, IES profiles, color temperature, and renderer-specific settings are all gone.

The result is gray, untextured geometry with an empty material editor. You then spend 4 to 8 hours rebuilding every material from scratch, referencing screenshots of the original 3ds Max scene. For a scene with 200+ materials, this is simply not viable.

For a detailed side-by-side comparison of every feature FBX loses, see MAX2C4D vs FBX Export.

Method 2: MAX2C4D — Open .max Files Directly from Cinema 4D

MAX2C4D takes a completely different approach. Instead of relying on FBX as a middleman, it reads your .max file directly through 3ds Max and transfers every piece of scene data to Cinema 4D — including everything FBX drops.

Here's how the process works:

The entire conversion happens automatically. In a real-world test on an 847-object archviz interior with 200+ Corona materials, the process completed in 43 seconds — from selecting the .max file to having a render-ready Cinema 4D scene.

For a detailed walkthrough with screenshots, see How MAX2C4D Works — Step-by-Step Tutorial.

3ds Max (Original)

Cinema 4D (via MAX2C4D)

What Transfers When You Open a .max File

MAX2C4D doesn't just transfer geometry. It rebuilds the full scene structure, including renderer-specific data that no interchange format can carry:

For the full list of supported material types, shader nodes, and render parameters, see Features.

Opening .max Files on Mac

3ds Max is Windows-only, but that doesn't mean your Cinema 4D workflow needs to stay on Windows. The MAX2C4D importer plugin runs natively on macOS, including Apple Silicon (arm64) Macs.

The workflow is simple: run the MAX2C4D exporter on your Windows machine (or any machine with 3ds Max installed) to convert the .max file into the intermediate format. Then copy the output folder to your Mac and open the project in Cinema 4D. The C4D importer reads the scene data and rebuilds everything natively — no Windows dependency at runtime.

This is especially useful for studios that use 3ds Max for asset creation but run their Cinema 4D pipeline on macOS. Convert once on a Windows workstation, then share the C4D project across your Mac-based team.

On first launch, macOS Gatekeeper may block the plugin since it's not distributed through the App Store. Right-click the plugin file and choose “Open” to bypass this. For detailed installation steps, see How It Works.

Related Guides

Frequently Asked Questions