Supported Files in Model Coordination

Model Coordination supports content from various file formats, including 3D models, point clouds, and Data Exchanges, which are summarized in the following table and sections.

In addition to 3D models, Model Coordination supports point cloud viewing. Point clouds let you aggregate scanned ReCap RCS files alongside your design models for visual comparison and QA/QC.

Automatic clash detection requires that each model element has a stable and unique ID across file versions. This ensures that clashes and other data remain associated with the correct elements when models are updated. Only the file types that are listed as supported for automatic clash detection have been verified as having stable element IDs. Extended properties are also supported for all file types with stable element IDs. Other file types can use extended properties, but will lose all property data when new file versions are uploaded.

For other file types, element IDs may be unstable or have not yet been verified. If you have a file type not listed as supported for clash detection and would like it verified, post a request on the Autodesk Forma forum.

Some files that are not compatible with automatic clash detection can still be viewed and aggregated with other models in Model Coordination, and used in other worfkflow such as Save to Files, object colors and so on. They can also be accessed in Autodesk Navisworks using the Navisworks Coordination Issues Add-In.

Tip: Coordination spaces with automatic clash detection turned on can only contain a maximum of 1000 models. All listed file types count toward this limit, whether they are supported for clash detection or not. See Model Coordination Frequently Asked Questions for more information.

File format ▼	Model aggregation ▼	Automatic clash detection & Extended properties ▼	Access in Autodesk Navisworks¹ ▼
3DM	Yes	No	Yes
3DS	Yes	No	Yes
3DXML	Yes	No	Yes
AXM	Yes	No	Yes
CATPART	Yes	No	Yes
CATPRODUCT	Yes	No	Yes
CGR	Yes	No	Yes
DAE	Yes	No	Yes
Data Exchanges (Revit and Inventor)⁵	Yes	Yes	No
Data Exchanges (other)⁵	Yes	No	No
DDX	Yes	No	Yes
DDZ	Yes	No	Yes
DGK	Yes	No	Yes
DGN²	Yes	No	Yes
DLV3	Yes	No	Yes
DMT	Yes	No	Yes
DWF	Yes	No	Yes
DWG	Yes	Yes	Yes
DWFX	Yes	No	Yes
DXF	Yes	No	Yes
EXP	Yes	No	Yes
F3D	Yes	No	Yes
FBX	Yes	No	Yes
GBXML	Yes	No	Yes
GLB	Yes	No	Yes
GLTF	Yes	No	Yes
IAM	Yes	No	Yes
IFC (tracked)³	Yes	Yes	Yes
IFC (other)	Yes	No	Yes
IGES	Yes	No	Yes
IGS	Yes	No	Yes
IPT	Yes	No	Yes
IWM	Yes	No	Yes
JT	Yes	No	Yes
MAX	Yes	No	Yes
MODEL	Yes	No	Yes
NWC (tracked)⁴	Yes	Yes	Yes
NWC (other)	Yes	No	Yes
NWD	Yes	No	Yes
OBJ	Yes	No	Yes
PAR	Yes	No	Yes
PRT	Yes	No	Yes
PSM	Yes	No	Yes
PSMODEL	Yes	No	Yes
RCS	Yes	No	No
RVM	Yes	No	Yes
RVT	Yes	Yes	Yes
SAT	Yes	No	Yes
SKP	Yes	No	Yes
SLDASM	Yes	No	Yes
SLDPRT	Yes	No	Yes
SMB	Yes	No	Yes
STEP/STP	Yes	No	Yes
STPZ	Yes	No	Yes
STL	Yes	No	Yes
USD	Yes	No	Yes
USDZ	Yes	No	Yes
VPB	Yes	No	Yes
VUE	Yes	No	Yes
WIRE	Yes	No	Yes
X_B	Yes	No	Yes
X_T	Yes	No	Yes
XPR	Yes	No	Yes

¹ Models opened through the Navisworks Coordination Issues Add-In are connected to Model Coordination and support issues-based workflows. Any file formats natively supported by Navisworks can be accessed in Model Coordination through Autodesk Desktop Connector, however these are not connected to Model Coordination.

² There is a known issue where some DGN files containing point primitives may produce an error when loading into Navisworks.

³ Includes IFC files exported from 12D (9.0 onwards), Allplan (2024 onwards), AutoCAD (architecture, AutoCAD MEP, and Civil 3D 2018 and onwards), ARCHICAD, AVEVA E3D Design (3.1.8.0 and onwards), BricsCAD (V24 onwards), E3D Design (4.1.0.0 and onwards), MagiCAD for Revit and AutoCAD, Revit, Siemens NX, Strakon, Tekla Structures, and VectorWorks.

Note: When exporting IFC files from 12D, select the Use attribute as IFC Globalid option to ensure stable object IDs are generated to facilitate clash detection. 12D, Allplan, and BricsCAD IFC files are only supported in V2 coordination spaces.

⁴ Includes NWC files exported from Revit, any AutoCAD-based application (including third-party apps), and from the ReCap 2026 scan-to-mesh process (NWC files from older versions of ReCap are supported for model aggregation only).

Note: When exporting NWC files from Revit for use in Model Coordination, turn on the Convert Element Ids option in Revit before exporting. This ensures Model Coordination recognizes that the NWC file is from Revit, and includes it in automatic clash detection. See the Revit page topic in the Navisworks help for more information on the Revit file exporter options.

⁵ A Data Exchange contains a subset of model data shared from a 3D view. Data Exchanges don't have a file extension, but Model Coordination treats them like files. Only Data Exchanges created from Revit and Inventor support automatic clash detection. Data Exchanges created or updated after August 13, 2026 with the latest connectors support all the listed workflows. Older Data Exchanges are visible in Model Coordination, but don't support automatic clash detection, the object table, or Save to Files. See Data Exchanges for more information, or read this blog post to learn how Data Exchanges work with Model Coordination.