Navisworks Workstation Guide: What Computer Do You Need for Autodesk Navisworks?

Navisworks is where every model on a project meets. The architect's Revit model, the structural model, the mechanical and electrical services, the civil works, the steel fabricator's Tekla model, an IFC from a subcontractor and, increasingly, a laser scan of the existing site are appended into one federated model, clashed against each other, sequenced against the programme and walked through in coordination meetings. Each of those models was built on a machine specified for its own software; Navisworks has to hold all of them at once. That is why a computer that is perfectly adequate for Revit can struggle in Navisworks, and why the official system requirements for Navisworks are no help at all in choosing one. This guide is written by Modena Technologies, Africa's only Autodesk Platinum Partner and an Autodesk Authorised Training Centre, and by Modena Computers, which builds and stress-tests workstations in Cape Town. We support Navisworks users, train BIM coordinators and specify their hardware every working day.

The guide covers what Autodesk officially requires and why that table is not the place to start, how Navisworks actually uses each component, the thresholds we work to when we specify a machine, and which Modena Computers configuration suits which kind of Navisworks user, from single-discipline review through multi-discipline clash detection and 4D sequencing to federations with point clouds. It applies to Navisworks Manage and Navisworks Simulate; the free Navisworks Freedom viewer places the same demands on a computer for the same model. We have deliberately avoided naming processor and graphics card models so that the principles stay useful as components change. The exact parts in each configuration are on the Apollo and Vulcan product pages.

What Autodesk officially requires, and why it is not enough

Autodesk publishes a single minimum specification for the Navisworks 2027 products, with no recommended tier. These are the figures.

	Autodesk minimum (Navisworks 2027)
Processor	3GHz or faster
Memory	2GB
Graphics	Direct3D 9 and OpenGL capable card with Shader Model 2
Display	1280 x 800 true colour; 1920 x 1080 recommended
Storage	15GB free for installation
Operating system	64-bit Windows 11 or Windows 10

Read that table for what it is: the specification needed to install Navisworks and open a small model. It has been essentially unchanged for a decade, and it says nothing about the work Navisworks is bought for. Autodesk's own support guidance is far more useful. Its article on Navisworks performance says plainly to "use computer with 64 GB RAM for large models (a few GB models)". Its article on slow-loading NWD files lists what load time depends on: "file size, model complexity, embedded geometry, attached properties, available system memory, processor performance, graphics hardware, and storage performance", and tells users to store the file on a local SSD rather than open it from a network location. Its article on point cloud crashes gives the cause in one sentence: "the point cloud file is too large for the computer hardware". Those three statements are a better specification than the official table, and this guide is built on them.

How Navisworks uses a computer

Navisworks is built around memory. When you open an NWF or NWD, the geometry and properties of every appended model are read into RAM, and they stay there while you navigate, select, search, clash and sequence. The more disciplines you append and the more detail each model carries, the more memory the federation occupies, and when it no longer fits, Windows starts paging to disk and everything slows at once: loading, orbiting, selection and clash runs. A point cloud appended to the federation is the heaviest single item a Navisworks model can carry, and Autodesk's remedy for a crash on a large point cloud is to reduce the point density until it fits the hardware. Memory is the first thing we size on a Navisworks workstation and the one most often under-specified.

The processor does two kinds of work. Loading a model, navigating it, selecting and searching objects and running a TimeLiner simulation are largely single-threaded, so they depend on the sustained speed of one core, which is why Autodesk's one hardware figure is a 3GHz processor. Clash Detective is different: Navisworks has an option to "allow use of all your CPU cores when running clash detection", so a clash run across a large federation scales with core count, and so does rendering with the Autodesk renderer and exporting animations. A coordinator who runs clash tests several times a day gets real value from more cores; a reviewer who navigates and marks up does not.

The graphics card has a smaller role than in design software, with one large caveat. Navisworks draws the federated model through the card and drops detail during navigation to keep the frame rate up, so a competent dedicated card with a current driver is enough for most models. The caveat is that Autodesk's troubleshooting for slow or crashing Navisworks almost always begins with the graphics card: use the strongest graphics hardware in the machine, update the driver, and test with hardware acceleration off to confirm the driver is the cause. The lesson is not to spend more on the card; it is to buy a current dedicated card, keep its driver current, and make sure Navisworks is using it rather than the processor's built-in graphics.

Memory: size it from the federated model

The question that decides a Navisworks workstation is how large the federated model is, and the honest answer is usually larger than people think, because it includes every discipline, every linked file, the properties attached to every object, and whatever point cloud or site scan has been appended. Autodesk's performance guidance says 64GB for models of "a few GB". Add Revit or Civil 3D open alongside with the source model loaded, which is how most coordinators work, and the figure rises again.

The thresholds we use are these. 32GB is the floor; it covers single-discipline review, models in the hundreds of megabytes, TimeLiner on modest projects, and the browser, email and issue-tracking tools that stay open alongside. 64GB is for federated multi-discipline building models of a gigabyte or more, which is Autodesk's own figure for large models, and for clash detection across them. 96GB or more is for federations with point clouds appended, campus and infrastructure scale models, and coordinators who keep Revit or Civil 3D open with the source models while they work in Navisworks. If you are unsure, open your largest federation with your usual applications running and check the memory figure in Windows Task Manager; above 70% of what you have, you need more, and if Navisworks is slow after a long session the figure has probably already passed it.

Memory in matched pairs running in dual channel is how every configuration we sell is built, and all Modena Computers workstations can be upgraded to 192GB later, which matters more for Navisworks than for most software because federated models only grow as a project progresses.

Processor: clock speed for navigation, cores for clash runs

Autodesk's one hardware figure for Navisworks is a 3GHz or faster processor, and for most of the working day that is the right emphasis. Loading, navigating, selecting, searching and sequencing run largely on one core, so sustained single-core speed is what makes Navisworks feel responsive on a large model. The base clock is what the processor holds under load; the turbo figure is what it reaches briefly when cool. A long model load or a clash run is sustained load.

Clock speed is not comparable across processor generations. A newer processor completes more work per cycle than an older one at the same frequency, so compare processors on current single-core benchmarks rather than on GHz alone, and be wary of high-core-count workstation and server processors, which usually run at lower clock speeds and are slower in Navisworks' single-threaded navigation than a current mainstream desktop processor costing far less.

Extra cores earn their place in three places: Clash Detective, which can use every core when multi-threading is enabled; rendering and animation export; and keeping Revit, Civil 3D or ReCap responsive alongside Navisworks. A BIM coordinator who runs clash tests across a large federation several times a day, or who publishes rendered sequences, is the Navisworks user who benefits from more cores. A reviewer who navigates and marks up should spend on clock speed and memory first.

Graphics: a current dedicated card, driven properly

Navisworks is undemanding of the graphics card compared with design and visualisation software, and the old advice that a mid-range card is enough for most users remains true. What Autodesk's support articles make clear is that the card still has to be a dedicated one with a current driver, that Navisworks must be set to use it rather than the processor's integrated graphics, and that a stale or corrupted driver is the most common cause of crashes and stuttering navigation. Spend on getting the graphics right rather than on getting it big.

Our thresholds: a current dedicated card with 8GB of graphics memory is the floor for any new Navisworks workstation, and it is where most coordinators should stay. 12GB is for federations with point clouds appended, for 4K displays, and for the large shared screens used in coordination rooms. 16GB is only worth it if the same machine also runs visualisation software such as Twinmotion or Enscape, which have their own, much higher, graphics needs. Every configuration in our range starts at 8GB.

You do not need a professional-series workstation graphics card for Navisworks. There is no certified-driver requirement and no feature that a professional card unlocks. A current consumer card with a stable, current driver, which is part of our build process, does the job at a lower price. We also configure the machine so that Navisworks uses the dedicated card, and we recommend the monitors are connected to the graphics card rather than the motherboard.

Storage and network: where the NWD lives

Navisworks itself needs about 15GB, but the storage that matters is where your models live. Autodesk's guidance on slow-loading NWD files is to store them on a local SSD instead of opening them from a network location, and its guidance on slow navigation says the same about files accessed from a central server. Coordination offices usually keep the NWF and its source files on a server so that the whole team sees the same federation, which is right for collaboration and slow for loading; the practical compromise is a fast network, a fast local drive, and local copies of the largest NWDs and point clouds for the machines that do the heavy work.

An NVMe drive is the only sensible choice for the operating system, Navisworks and your working files. Read and write speeds of around 2,000MB/s are a reasonable floor. On capacity, 1TB serves most coordinators whose federations live on a server. Choose 2TB if you keep large NWDs or point clouds locally, as Autodesk recommends for performance; our Max configurations are built with 2TB for exactly that. On the network side, a wired gigabit connection to the server is the minimum for loading federations of a gigabyte or more; a coordination workstation on Wi-Fi will spend its mornings waiting.

Cooling and sustained performance

Cooling is the part of a workstation that spec sheets leave out, and for Navisworks it decides whether you keep the processor speed you paid for through a long clash run or a rendered animation. Those operations hold the processor at full load for minutes or longer. If the cooler and case cannot carry the heat away, the processor drops its clock speed to protect itself and the run takes longer; to the user it feels like Navisworks lagging, when the cause is thermal.

A substantial air cooler with good case airflow will hold a non-overclocked processor at its rated speed indefinitely, and that is how we build Apollo. Processors tuned above their standard settings need a large liquid cooler to sustain the gain, which is why Vulcan uses a 360mm radiator and holds its speed under sustained load rather than only in short bursts. A power supply rated well above the system's actual draw runs cooler, quieter and longer. Every Modena Computers workstation runs under sustained full load before it leaves Cape Town, so throttling, instability and noisy fans are found on our bench rather than in your coordination meeting.

Why a gaming PC is not a Navisworks workstation

A gaming PC looks like a bargain for Navisworks, because Navisworks does not need the expensive graphics card that a gaming PC is built around. That is exactly the problem: the gaming PC spends its budget on the one component Navisworks needs least and economises on the one it needs most. The typical result is 16GB of memory, often in a single stick, which will not hold a multi-discipline federation; a processor chosen for gaming frame rates rather than sustained single-core speed and clash-run core count; a single 1TB drive; a compact case with the airflow of a compact case; and a power supply sized to the exact components in it.

None of those compromises shows on a spec sheet. They show the first time the structural and services models are appended to the architecture: the memory fills, the machine pages to disk, loading takes ten minutes and navigation stutters. A well-specified gaming PC can run Navisworks, but it was not specified for Navisworks, and when a driver update makes the model flicker during navigation the support line has not heard of hardware acceleration. A workstation built for Navisworks starts from the size of your federated model and the software you run alongside it, is tested under the loads you will put on it, and comes with a warranty and support from people who use the software.

Which Modena Computers workstation for which Navisworks user

We build two models in three configurations each. Apollo uses a standard processor with a high-performance air cooler; Vulcan uses a tuned processor with a 360mm liquid cooler, more cores and faster storage. Both carry a four-year warranty and lifetime hardware support, both are built to order in Cape Town, and both are delivered anywhere in South Africa.

Because Navisworks is led by memory and clock speed rather than graphics, the Apollo range suits Navisworks users well, and the choice between configurations is mostly a choice of memory. Vulcan adds the fastest sustained navigation and more cores for clash runs.

Configuration	Memory	Graphics memory	Suits
Apollo Standard	32GB	8GB	Single-discipline review, small to medium NWDs in the hundreds of megabytes, TimeLiner on modest projects, site and office review stations
Apollo Pro	48GB	8GB	Multi-discipline federations approaching a gigabyte, clash detection and 4D sequencing, issue-tracking tools open alongside
Apollo Max	64GB	12GB	Large federated building models, point clouds appended, a 4K display or coordination-room screen; meets Autodesk's 64GB guidance for large models
Vulcan Standard	32GB	8GB	Fastest loading and navigation for small to medium models, with more cores for frequent clash runs
Vulcan Pro	64GB	12GB	BIM coordinators running clash tests across large federations daily, rendering and animation export, Revit or Civil 3D open alongside
Vulcan Max	96GB	16GB	Campus and infrastructure scale federations with point clouds, several heavy applications at once, visualisation software on the same machine

If your work goes beyond this, for example very large scan datasets appended to a federation, we build custom specifications up to 192GB of memory and 32GB of graphics memory. Tell us what you work on and we will specify the machine for it.

See all configurations and current prices Request a custom spec

Frequently asked questions

Is a gaming PC good enough for Navisworks?

Usually not, and for an unusual reason: gaming PCs spend on the graphics card, which Navisworks barely needs, and economise on memory, which Navisworks needs most. A 16GB gaming PC will not hold a multi-discipline federation. If you buy one for Navisworks, insist on 32GB of memory in two sticks as a minimum, 64GB for federated models, and a processor chosen for sustained single-core speed.

How much RAM does Navisworks need?

Autodesk's official minimum is 2GB, which is not a buying guide. Autodesk's own performance advice is 64GB for large models of a few gigabytes. We specify 32GB as a floor for single-discipline review, 64GB for federated multi-discipline models and clash detection, and 96GB or more for federations with point clouds, campus-scale models, or Revit and Civil 3D open alongside.

Does Navisworks use the graphics card?

Yes, to draw the model, but modestly. A current dedicated card with 8GB is enough for most coordinators, and 12GB covers point clouds and 4K. What matters more is that the driver is current and that Navisworks is set to use the dedicated card rather than integrated graphics; Autodesk's troubleshooting for crashes and stuttering starts there.

Does Navisworks use multiple cores?

Partly. Loading, navigating, selecting and TimeLiner are largely single-threaded, so clock speed matters most. Clash Detective has an option to use all processor cores, and rendering and animation export use them too, so coordinators who run clash tests all day benefit from more cores.

Do I need a workstation-class graphics card for Navisworks?

No. Navisworks has no certified-driver requirement and no feature that a professional card unlocks. A current consumer card with 8GB or more and a stable driver does the job at a lower price.

Is Intel or AMD better for Navisworks?

Either. Autodesk supports both. What matters is sustained single-core speed for navigation, enough cores for clash runs, and cooling that holds the speed under load. We build on whichever platform delivers that best at the time, and the current components are listed on each product page.

Should I buy a laptop or a desktop for Navisworks?

Navisworks is one of the few Autodesk products regularly used on site, so a laptop has a real place for reviewing and marking up a published NWD in a site office. For the coordinator who builds the federation, runs clash tests and keeps Revit open alongside, choose a desktop: laptops rarely offer 64GB of memory at a sensible price, and their processors run at lower sustained speeds. Many offices run both, a desktop for coordination and a laptop for review.

Can I upgrade a Modena Computers workstation later?

Yes, and for Navisworks the upgrade that matters is memory, which can be increased to 192GB as the federation grows. The graphics card and storage can also be replaced, and the four-year warranty and lifetime hardware support continue.

Next step

Browse the Modena Computers workstations to see the current configurations and prices, or contact us with the size of your federated models, whether you append point clouds, how often you run clash tests and what you run alongside Navisworks, and we will tell you which configuration fits, or build one that does.