If you’ve ever watched Revit slow down dramatically on a model you know isn’t particularly large, there’s a good chance RAM is part of the story. Most Revit users have experienced this. Far fewer have a framework for understanding why it happens or how to prevent it.
There’s a rule of thumb in the Revit community that goes largely unmentioned in official documentation but shows up consistently in the experience of practitioners working on demanding projects: Revit’s performance tends to degrade when system RAM drops below approximately 20 times the file size of the model being worked on. It’s an approximation, not a precise formula, but it’s a useful starting point for understanding why a 32 GB workstation that handles most projects fine can still struggle on specific files.
What the Math Looks Like in Practice
A 100 MB Revit file is a relatively small model. By the 20x rule, you’d want around 2 GB of RAM available for Revit to work with it comfortably, which is well within any modern workstation’s capacity.
A 500 MB Revit file, which represents a moderate-to-large architectural or MEP model, puts the RAM recommendation at 10 GB just for Revit’s working memory. On a workstation with 32 GB total, that’s manageable, but once you account for the operating system, background processes, and any other applications open simultaneously, the headroom starts to shrink.
A 1.5 GB Revit file, the kind that appears on large hospital, mixed-use, or campus projects with extensive MEP, structural, and architectural models linked together, puts the theoretical recommendation at 30 GB of RAM for Revit alone. On a 32 GB machine, you’re running the model at or past the threshold where performance starts to degrade. On a 64 GB machine, you have room to work.
This is one of the reasons that 64 GB has become the practical standard for Revit workstations on professional-scale projects, and why Autodesk’s own recommendations for Revit 2026’s Accelerated Graphics feature specify 64 GB as the baseline.
Navisworks Makes the RAM Problem Worse
Revit isn’t the only application in the AEC workflow with significant RAM demands. Navisworks, which is used for model coordination and clash detection across disciplines, loads the entire federated model into memory to process it. Unlike Revit, which reads from file and caches selectively, Navisworks pulls the full dataset into RAM.
On a large hospital project, the federated Navisworks model can easily exceed 10 to 15 GB of raw geometry and data. Running a coordination session on that model requires enough RAM to hold the full dataset in memory while still leaving the operating system and other processes room to function. Teams trying to run Navisworks coordination on 32 GB machines on large projects know what the outcome looks like: slow load times, sluggish navigation, and occasional crashes when the system runs out of headroom.
For VDC coordinators and BIM managers running coordination on projects of significant scale, 64 GB is the starting point, not the premium option. 128 GB becomes relevant for the largest federated models encountered in healthcare, infrastructure, and large commercial construction.
Practical Recommendations
For most architectural, MEP, and structural users working on projects up to medium scale, 32 GB of RAM is functional and 64 GB provides meaningful headroom and future-proofing. For teams working on large projects, or for VDC coordinators running Navisworks coordination regularly, 64 GB is the practical minimum. For enterprise environments and the largest coordination workflows, 128 GB becomes justifiable.
The uncomfortable truth is that many AEC workstations are still configured at 16 GB, which was a reasonable standard a decade ago and is now a constraint for professional workflows. The cost of upgrading from 16 GB to 32 GB or 64 GB of DDR5 memory is modest relative to the productivity impact of running models at or past the memory threshold regularly.
Configure your hardware to the way you work.
If you’re unsure whether your current hardware configuration is adequate for your team’s project scale, the BIMBOX team can walk through your workflow and help you understand where the constraints are.
Contact us below and let’s figure out what your team’s hardware should actually look like.