Navisworks NWD — Autodesk's federated BIM format for clash detection and 4D simulation

Navisworks NWD is Autodesk's "published" federated BIM format: a single file aggregating an architectural model from Revit, structural from Tekla, MEP networks from MagiCAD, and a point cloud from the construction site into one common, viewable snapshot. If .rvt is the architect's working file with parametric elements and change history, .nwd is the publication: compressed geometry, immutable, optimized for viewing and clash analysis. In a typical skyscraper project a 200 MB .nwd file can contain a coordinated model from dozens of source files totaling 20 GB.

History: from British startup Navisworks Ltd to Autodesk

Navisworks was born in Sheffield, UK, in the late 1990s. British company Navisworks Ltd specialized in viewing large CAD models: AutoCAD files, MicroStation .dgn, 3D Studio .max. By the early 2000s the product known as JetStream became the de-facto standard for contractors on major infrastructure projects: Heathrow Terminal 5, London Crossrail, BP and Shell projects.

In June 2007 Autodesk acquired Navisworks Ltd for an undisclosed sum and renamed the line to Autodesk Navisworks. That same release introduced Clash Detective — the module for finding geometric conflicts between models of different disciplines (beam intersecting duct, cable tray going through a load-bearing wall). This became the killer feature: before Navisworks, contractors caught such collisions only on the construction site, at a cost of millions.

In 2009 TimeLiner was added — a 4D scheduling module: every model element receives start and end dates, and Navisworks shows a construction animation over time. From 2013 came Quantification — the 5D module with quantity takeoff and cost. By the 2020s Navisworks had become the standard for General Contractors in the US, UK, and UAE.

Since 2018 Autodesk sells Navisworks only as part of the AEC Collection — a bundle with Revit, Civil 3D, AutoCAD, InfraWorks. Standalone licenses no longer exist. The standalone viewer Navisworks Freedom is free for clients and owners to read .nwd files.

What's inside .nwc, .nwf, .nwd

The main feature of Navisworks is not one format but three paired ones, each with its own role:

NWC — Navisworks Cache. A cache file of one source model. When you open .rvt or .dwg in Navisworks, the program generates a same-named .nwc next to it — a light compressed representation of the geometry, 10–50× smaller than the source. NWC is created either via File → Open (with Navisworks Manage) or via an export plugin from the source program itself: Revit → Add-Ins → External Tools → Navisworks Exporter. NWC stores only geometry + basic properties (name, category, material) and doesn't let you edit the model.

NWF — Navisworks File. Federation file: a list of references to multiple .nwc + view settings, saved viewpoints, search sets, Clash Detective rules, TimeLiner schedule. The .nwf itself contains no geometry — it loads on opening via references to .nwc. This is a live document of a coordination session: if tomorrow the architect resaves .rvt and generates a fresh .nwc, opening the .nwf automatically pulls in the updated model.

NWD — Navisworks Document. A published single file — a federation snapshot. Unlike .nwf, the .nwd embeds all geometry from all .nwc at publication time. The file becomes self-contained: you can send it to a client, open in Freedom viewer on the construction site, and it will show exactly what existed at publication.

Inside .nwd / .nwc is a closed Autodesk binary format. Geometry is lossy-compressed: optimized for viewing, not editing. Thousands of triangles per wall become tens — the eye doesn't see the difference, but file size drops 30–50×. This compromise is intentional: Navisworks was never positioned as an editor.

Supported source formats — over a hundred: Revit (.rvt), AutoCAD (.dwg, .dxf), MicroStation (.dgn), Bentley OpenBuildings (.imodel), Tekla Structures (.ifc), 3ds Max (.3ds), SketchUp (.skp), STEP (.stp), IGES (.igs), Catia (.catpart), Inventor (.ipt), SolidWorks (.sldprt), point clouds (.rcp, .e57). This makes Navisworks a universal model aggregator.

Who needs Navisworks: five roles

General Contractor. The contractor responsible for the building as a whole uses Navisworks for weekly coordination sessions with subcontractors. Architect, structural, MEP, facade — each sends their .nwc, the GC federates into .nwf, runs Clash Detective, and discusses conflicts. This reduces on-site rework by 30–50%.

BIM Coordinator on a major project. A person whose job is keeping the .nwf federation current: updating references, rerunning clash tests, sending clash reports in BCF (BIM Collaboration Format). On an airport or metro-scale project this is full-time work for years.

4D Construction Scheduler. Uses TimeLiner to link the model with the work schedule from Primavera P6 or Microsoft Project. Each element gets construction start/end dates, after which Navisworks renders a building-erection animation over time. Used for client presentations, sequence verification, site logistics assessment.

Quantity Surveyor / Estimator. Via the Quantification module extracts volumes from the coordinated model: concrete, rebar, brick, drywall, pipe length, window area. Calculation runs by rules described in .nwt (template) format, savable and reusable across projects.

Client / Owner. Receives the final .nwd as deliverable and opens in free Navisworks Freedom. Doesn't edit, but can: 3D navigation, distance measurement, reading element properties, viewing saved views and construction animation. This is the verification artifact: "this is what I'm paying for."

Software for NWD: seven programs

Autodesk Navisworks Manage. Full edition with Clash Detective, TimeLiner, Quantification, Scripter. Part of AEC Collection. Bundle price ~$3000/year. autodesk.com/products/navisworks

Autodesk Navisworks Simulate. "Mid" SKU: opens all formats, supports TimeLiner, but lacks Clash Detective and Quantification. Used by subcontractors who need to show their part in 4D without doing full coordination.

Autodesk Navisworks Freedom. Free viewer for .nwd. View, measure, saved-view navigation only. Ideal for client, site supervisor, presentations. autodesk.com/products/navisworks/freedom

Autodesk Construction Cloud / BIM 360. Cloud platform: Document Management module stores .nwd with versions, Model Coordination does clash detection in the browser without installing Manage. Since 2022 the direction is positioned as a replacement for desktop Navisworks for distributed teams. construction.autodesk.com

Solibri Office. Alternative path for clash detection via .ifc instead of .nwd. Stronger in rule-based model quality checks (e.g. "all fire-rated doors must carry FD60 certification"). solibri.com

Bentley Synchro 4D. Direct competitor to TimeLiner from Bentley: integration with MicroStation, OpenBuildings, ProjectWise. Used in Bentley shops. bentley.com/software/synchro-4d

OpenProject IFC Viewer. Open-source web viewer for .ifc. Doesn't open .nwd directly, but if you convert .nwd → .ifc via Navisworks Export → IFC, you can use it as a free alternative for small-team coordination. openproject.org

Pitfalls and tips

NWC does not auto-update. When the architect saves .rvt, the .nwc is not automatically regenerated — an explicit export via Add-Ins → Navisworks Exporter (or batch File → Batch Utility) is needed. On major projects teams configure a nightly job on Jenkins / Azure DevOps: every night a script opens all .rvt and re-saves .nwc, and the .nwf automatically pulls fresh versions in the morning.

All sources must share coordinates. The most common .nwf problem is models not lining up in space. The architect works in Revit's local system, the structural engineer in geodetic UTM, MEP in its own arbitrary system. Solved through Project Base Point + Survey Point + Shared Coordinates in Revit, equivalents in AutoCAD and Tekla. If coordinates aren't unified from project start, models must be shifted manually in Navisworks via Item Tools → Override → Move/Rotate.

Clash Detective generates noise. Running a clash test across the entire project naively easily yields 50,000 "conflicts" — most of them false positives (wall intersecting baseboard, cable intersecting wall at a pass-through). Reduce noise via Filter Tolerances (minimum 25 mm), Search Sets instead of "All Items", and conflict clustering (Cluster) by 1 m³ cubes.

TimeLiner breaks when element IDs change. If the architect deleted and re-created a wall in Revit, it gets a new ElementID, and the TimeLiner binding to the schedule breaks. Prevention: link tasks to Search Sets (by type, by layer), not to specific elements by ID.

NWD is a publication; .nwf is the working file. Don't send .nwf to subcontractors — it's a reference file and their .nwc paths won't resolve. Always publish via File → Publish → NWD: it packs all geometry, the file is self-contained. This is especially important for government acceptance, where the artifact must be unambiguous.

Element properties can be lost. When exporting Revit → NWC, standard category properties (Comments, Mark, Type Name) are preserved. Custom shared parameters survive only if added to Project Information and flagged for export in Revit. Test on a pilot model before kicking off the real project.

Freedom viewer doesn't show Clash Results. The free Navisworks Freedom opens .nwd but doesn't show Clash Detective results — that requires Manage. If the client needs to see conflicts — export Clash Report to HTML or BCF via File → Export → Report.

How to build site context for Navisworks via osm2cdr.ru

Navisworks doesn't load OSM directly but federates via a CAD chain. The standard pipeline for site context is exporting DWG (or DXF) from osm2cdr.ru, opening in AutoCAD or Revit, generating NWC, and appending to the .nwf.

Step 1. On osm2cdr.ru outline a bbox around the construction site — usually 500×500 m for a single object, 1×1 km for a block, 5×5 km for a linear object (metro, road). Step 2. Choose format DWG (or DXF for portability). Step 3. Choose the style "buildings + roads + railways + waterways" — for a contractor this is the base environment kit. Step 4. Download. Step 5. Open in AutoCAD (or Revit), align to project coordinates, save as .dwg in the coordinated system. Step 6. Export NWC:

In AutoCAD: _-EXPORTTONWC (or ribbon → Output → Export → Navisworks). In Revit: Add-Ins → External Tools → Navisworks Exporter. NWC is created next to the source file. Step 7. In Navisworks Manage open your .nwf, run Home tab → Append, pick the site-NWC. Site context appears as a separate federated model.

For batch publication via the Navisworks .NET API (C# example):

using Autodesk.Navisworks.Api;
using Autodesk.Navisworks.Api.Controls;

var doc = Application.ActiveDocument;
doc.AppendFile(@"C:\projects\osm2cdr-site-context.nwc");
doc.SaveFile(@"C:\projects\federation-with-site.nwf");
// Publish snapshot
doc.PublishAs(@"C:\projects\federation-with-site.nwd",
              new PublishOptions { IncludeReviewComments = true });

Or one-liner via CLI (Roamer.exe):

"%ProgramFiles%\Autodesk\Navisworks Manage 2026\Roamer.exe" ^
  -OpenFile "C:\projects\fed.nwf" ^
  -ExeScript "C:\scripts\publish-nwd.js"

A typical case is a coordination session for a city-block reconstruction: site context from osm2cdr.ru shows neighboring buildings and streets, the architectural model from Revit shows the new building, MEP shows engineering networks. Clash Detective discovers that the proposed cable tray crosses the red line and intersects the existing tram line.

Related formats and resources

• Revit RVT — Autodesk's flagship BIM format
• IFC — open BIM standard from buildingSMART
• DGN — Bentley MicroStation flagship
• DWG — binary AutoCAD standard
• MicroStation — Bentley's format and tool
• DWG landing page

Sources

• Autodesk Navisworks Product Page — autodesk.com/products/navisworks
• Autodesk Knowledge Network, Navisworks documentation — help.autodesk.com/view/NAV/2026/ENU/
• Autodesk acquires Navisworks (2007 press release) — press.autodesk.com
• Navisworks .NET API documentation — help.autodesk.com/view/NAV/2026/ENU/?guid=NavisworksAPI
• BCF Specification, buildingSMART — github.com/buildingSMART/BCF-XML
• Autodesk Construction Cloud, Model Coordination — construction.autodesk.com/products/autodesk-build/model-coordination