Limitations when importing from other applications
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 animationA collection of images that create a moving image when played sequentially. In Unity, an animation is the result of adding two different animation keys, at two different times, for the same animatable property. More info
See in Glossary from two different types of files:
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 Exporting from 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:
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.
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.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thanks for helping to make the Unity documentation better!
Limitations when importing from other applications