Exporting from Revit to Navisworks: A Complete Guide

Welcome back to our comprehensive Navisworks video series. This is the final installment of our three-part importing and exporting workflow series. In this tutorial, we'll master the essential skill of exporting from Revit to NWC (Navisworks Cache format), a critical workflow for BIM coordination and clash detection in modern construction projects.

Before we begin, ensure you have Revit open and ready. We'll start with the BIM361-ARC model as our working example. The NWC export process shares similarities with DWG exporting, but offers distinct advantages for Navisworks users, particularly in maintaining model intelligence and organization.

The foundation of successful NWC export lies in proper view preparation. Navigate to a 3D view and configure your visibility settings with precision—hide elements you don't need exported and ensure all critical components are visible. This upfront investment in view configuration will save significant time during coordination reviews. Access the export function through the Application button, then Export > NWC.

You'll notice our Lesson 2 folder already contains several NWC files. These weren't manually created—Navisworks automatically generates cache files during DWG import operations, streamlining subsequent access to the same data. However, the files we're creating now serve a different purpose entirely.

Before proceeding with the export, verify your settings carefully. Ensure coordinates are set to "Project Internal" to maintain model positioning integrity, and confirm you're exporting the current view. These settings are crucial for successful model federation later in your workflow.

To distinguish our manually exported files from Navisworks-generated cache files, we'll append a lowercase "x" to our filename: BIM361-ARC-x.nwc. This naming convention becomes invaluable when managing multiple file versions across project phases. Click Save to complete the export.

Now let's validate our work by returning to Navisworks and opening BIM361-ARC-x.nwc. You'll immediately notice this file preserves the visual fidelity of the original Revit model, including materials, shading, and grid lines. In the Selection Tree, observe how the file maintains Revit's level-based organization structure, unlike DWG exports which flatten this hierarchy.

---

This brings us to a critical question: when should you export to NWC versus importing RVT files directly? The answer lies in control and workflow optimization. Direct RVT import gives Navisworks complete access to the entire model, importing everything without discrimination. While comprehensive, this approach can create unwieldy file sizes and complicate clash detection workflows.

Let's demonstrate this principle with the MEP file. When we initially opened this RVT file in Navisworks, the software imported all trades simultaneously—electrical, mechanical, and plumbing systems together. For complex projects, this unified approach can mask coordination issues and slow performance.

Strategic separation of building systems dramatically improves clash detection efficiency and allows for more targeted coordination meetings. Let's export each trade individually, starting with electrical systems. Navigate to Application > Export > NWC, and save as ELEC-x.nwc. This granular approach enables discipline-specific reviews and more precise clash reporting.

Continue this process for mechanical systems (MECH-x.nwc) and plumbing (PLUMB-x.nwc). Each export creates a focused dataset that coordination teams can toggle independently, streamlining the review process and improving meeting productivity.

While maintaining our workflow efficiency, close the MEP file and open the structural model. Export this single-discipline file using the same naming convention, creating STRUCT-x.nwc. This systematic approach to file organization pays dividends during coordination phases.

Returning to Navisworks, we'll now federate these individual trade files into a comprehensive coordination model. Use the Home tab's Append function to systematically add each NWC file: structural, plumbing, mechanical, and electrical. This federation approach gives you unprecedented control over model visibility and performance.

---

With all files successfully appended, test your setup by toggling individual trades on and off. Verify spatial relationships and ensure proper positioning—this quality control step prevents coordination issues downstream. Establish a logical Home viewpoint, perhaps showcasing the building's primary elevation, and save your federated model as BIM361-complete.nwf.

Remember that file format flexibility is one of Navisworks' greatest strengths. You might prefer structural models in DWG format for compatibility with certain workflows, while maintaining MEP trades as NWC files for their superior intelligence. Similarly, architectural models might perform better as direct RVT imports depending on your specific requirements and software licensing.

Your format selection should be driven by three key factors: the information richness required from each discipline, available software licenses within your organization, and the layer organization that best supports your coordination objectives. In 2026's increasingly collaborative AEC environment, this flexibility becomes essential for cross-platform team coordination.

For the remainder of this course, we'll standardize on NWC format exports, with our BIM361-complete file serving as the master coordination model. This approach provides the optimal balance of file performance, model intelligence, and coordination functionality for modern BIM workflows.

This concludes our comprehensive exploration of importing and exporting workflows in Navisworks. These fundamental skills form the backbone of successful BIM coordination, and mastering them will significantly enhance your project delivery capabilities. Join us in the next section as we dive deeper into advanced Navisworks coordination techniques.