Supported Model file formats

Note: This section provides information about proprietary file formats that use FBX conversion. However, there are two file formats that do not use FBX as an intermediary: SketchUp and SpeedTree. For more information about importing these file formats, see the SketchUp Settings and SpeedTree topics.

Unity supports importing Meshes and animation from two different types of files:

• Exported 3D file formats, such as .fbx or .obj. You can export files from 3D modeling software in generic formats that can be imported and edited by a wide variety of different software.

• Proprietary 3D or DCC (Digital Content Creation) application files, such as .max and .blend file formats from Autodesk® 3ds Max® or Blender, for example. You can only edit proprietary files in the software that created them. Proprietary files are generally not directly editable by other software without first being converted and imported.

Unity can import and use both types of files, and each come with their own advantages and disadvantages.

Exported 3D files

Unity can read .fbx, .dae (Collada), .3ds, .dxf, and .obj files. For information about exporting 3D files, see Using FBX files in other applications or read the documentation for your 3D modeling software.

Advantages:

• You can import only the parts of the model you need instead of importing the whole model into Unity.
• Exported generic files are often smaller than the proprietary equivalent.
• Using exported generic files encourages a modular approach (for example, using different components for collision types or interactivity).
• You can import these files from software that Unity does not directly support.
• You can re-import exported 3D files (.fbx, .obj) into 3D modeling software after exporting, to ensure that all of the information has been exported correctly.

Disadvantages:

• You must re-import models manually if the original file changes.
• You need to keep track of versions between the source file and the files imported into Unity.

Proprietary 3D application files

Unity can import proprietary files from the following 3D modeling software:

• Autodesk® 3ds Max®
• Autodesk® Maya®
• Blender
• Modo
• Cheetah3D

Warning: Unity converts proprietary files to .fbx files as part of the import process. However, it is recommended that you export to FBX instead of directly saving your application files in the Project. It is not recommended to use native file formats directly in production.

Note: As of Unity 2019.3, Unity no longer provides built-in support for Cinema4D files. To continue using Cinema4D files in Unity for versions 2019.3 and later, install Maxon’s Cinema4D importer. Alternatively, you can export an FBX file from Cinema4D instead.

Advantages:

• Unity automatically re-imports the file if the original model changes.
• This is initially simple; however it can become more complex later in development.

Disadvantages:

• A licensed copy of the software used must be installed on each machine that uses the Unity Project.
• Software versions should be the same on each machine using the Unity Project. Using a different software version can cause errors or unexpected behavior when importing 3D models.
• Files can become bloated with unnecessary data.
• Big files can slow down Unity Project imports or Asset re-imports, because you have to run the 3D modeling software you use as a background process when you import the model into Unity.
• Unity exports proprietary files to .fbx internally, during the import process. This makes it difficult to verify the .fbx data and troubleshoot problems.

Note: Assets saved as .ma, .mb, .max, .c4d, or .blend files fail to import unless you have the corresponding 3D modeling software installed on your computer. This means that everybody working on your Unity Project must have the correct software installed. For example, if you use the Autodesk® Maya LT™ license to create ExampleModel.mb and copy it into your Project, anyone else opening that Project also needs to have Autodesk® Maya LT™ installed on their computer too.