Share

Supported Files in Model Coordination

Model Coordination supports 3D models from various file formats, which are summarized in the following table.

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. 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 ACC forum.

Some files that are not compatible with automatic clash detection can still be viewed and aggregated with other models in Model Coordination, and 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 Access in Autodesk Navisworks*
DGN** Yes No Yes
DWG Yes Yes Yes
IFC (tracked)*** Yes Yes Yes
IFC (other) Yes No Yes
NWC (tracked)**** Yes Yes Yes
NWC (other) Yes No Yes
NWD Yes No Yes
RVM Yes No Yes
RVT Yes Yes Yes
SKP Yes No Yes
VUE 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.

Was this information helpful?