Revit Workstation Specs: What to Buy for a Practice, Not a Benchmark

Home Insights Guides Revit Workstation Specs: What to Buy for a Practice, Not a Benchmark

A BIM coordinator working across a federated model on two screens
Guides

Revit Workstation Specs: What to Buy for a Practice, Not a Benchmark

Every guide to Revit workstations on the internet is written by someone selling the workstation. The specs are real and the benchmarks are real, but the frame is one enthusiast building one machine. A practice buys thirty, replaces them on a cycle, and has to explain the invoice to a director who wants to know why the drafters’ computers cost more than the accountants’. This guide is written for that conversation.

We manage IT for architecture, engineering and construction firms, and workstation sizing is the thing generalist providers get wrong most consistently. Not because they’re careless. Because the intuition that more cores means faster is correct for almost everything except the software your practice runs.

Start with what Autodesk actually says

Autodesk’s published system requirements for Revit 2026 are short. The one line that matters is the CPU guidance. It reads: a processor with 2 GHz or higher base clock speed, and then, “highest single core base clock speed (GHz) is recommended.” Not core count. Single-core clock.

That’s because most of what Revit does when a drafter is working, regenerating views, updating the model after an edit, loading families, runs on one core at a time. Some operations are multi-threaded and Autodesk has been adding more each release. But the thing a drafter waits for, dozens of times an hour, is single-threaded, and a chip with fewer, faster cores gets through it sooner than a chip with sixteen slower ones.

Autodesk's published requirements for Revit 2026, as quoted in this guide
ComponentAutodesk saysWhat it means for a practice
CPU2 GHz or higher base clock. "Highest single core base clock speed (GHz) is recommended."Buy clock, not cores, for drafters.
RAM16 GB entry level. 64 GB or more for large, complex models.32 GB is the practical floor beyond small residential work.
GraphicsDirectX 11 with Shader Model 5. 4 GB video memory minimum, 8 GB and up for large models.Mid-range professional GPU for drafters. Rendering cards for visualisers only.
Disk30 GB for the installation. 100 GB recommended free for temporary files.The figure everyone ignores. NVMe for BIM managers.
OSWindows 10 from version 1809, or Windows 11. .NET 8.Windows 10 left Microsoft support in October 2025. Plan the move.

That Windows 10 line deserves a second look. Autodesk still lists it as supported, but Microsoft ended support for Windows 10 in October 2025, which means a fleet still running it has an operating system that no longer receives security patches. For a practice that needs to evidence Essential Eight maturity, that’s disqualifying on its own, so plan the move before the next tender rather than after it.

The purchase most practices get wrong

It’s the sixteen-core workstation. A procurement person compares two machines, sees one with twice the cores for a few hundred dollars more, and buys it for the whole fleet. It benchmarks well. The drafters find it slower than the five-year-old machine it replaced, and nobody can explain why, and the provider says the model must be corrupt.

Why the sixteen-core machine feels slower Two workstations. Sixteen cores at a lower clock: one core carries the drafter's work, fifteen sit idle, and the wait is longer. Eight cores at a higher clock: one core carries the work, the wait is shorter. Illustrative, not a benchmark. One core does the waiting. Buy the fastest one. Illustrative, not a benchmark. Rendering is the exception; it uses every core and the GPU. Sixteen cores, lower clock 1 busy · 15 idle Regenerate a view "The model must be corrupt." It isn't. Eight cores, higher clock 1 busy · 7 idle Regenerate a view Sized for the software.
The new chip has a lower single-core clock than the old one, and Revit spends its day on one core.

The model isn’t corrupt. The new chip has a lower single-core clock than the old one, and Revit spends its day on one core. We’ve walked into this at more than one Melbourne practice, and the fix, unfortunately, is usually a second purchase.

Ashley Neilson, one of our systems engineers, has spent fifteen years supporting architecture and design environments and has a simpler rule for it. If the quote leads with the core count, the person writing it hasn’t read Autodesk’s requirements page. Ask them for the base clock instead. Watch what happens.

Is this the problem you're having?

Tap what fits. A consultant gets back to you within one business day.

We only use these details to reply to this enquiry. Privacy Policy

Spec by role, not by budget band

A practice doesn’t have one kind of Revit user. It has at least three, and the same machine is wrong for at least one of them.

RoleCPURAMGPUStorage
Drafters and documentersHighest single-core clock you can buy32 GB practical floor beyond small residentialMid-range professional. Not a rendering card.Standard SSD
BIM managers and coordinatorsClock still matters. The one role where a few extra cores earn their keep.64 GB, Autodesk's large-model tierMid-range professionalFastest in the office. NVMe. Linked models load from disk constantly.
Visualisers (Enscape, Twinmotion, V-Ray)Many cores. Rendering is heavily multi-threaded.64 GBLarge-memory GPU. Rendering is GPU-bound.NVMe

Drafters and documenters spend their day in the model, in views, editing and regenerating. They need the highest single-core clock you can buy, 32 GB of RAM as a practical floor for anything beyond a small residential project, and a mid-range professional GPU. They do not need a rendering card. Buying one for them is the second most common waste we see.

BIM managers and coordinators open federated models, run clash detection, and keep Navisworks and Revit open at the same time. They’re the 64 GB tier Autodesk describes, and they benefit from the fastest storage in the office because linked models load from disk constantly. Give them the NVMe drive and the RAM. The clock speed matters here too. But they’re the one role where a few extra cores earn their keep.

Visualisers rendering in Enscape, Twinmotion or V-Ray are the exception to everything above. Rendering is heavily multi-threaded and GPU-bound, so this is the seat where you buy the many-core chip and the large-memory GPU. If a practice has one visualiser and specifies the whole fleet around their needs, twenty-nine people get a slower machine so one person gets a faster one.

A drafter at a workstation in safety glasses
Three kinds of user, three specs. The fleet should not be built around the one visualiser.

Laptop or desktop

Desktops, for anyone who mostly works at a desk. The same money buys a meaningfully higher clock and better cooling, which matters because a laptop that thermal-throttles under a long regeneration is a laptop that’s slower than its spec sheet says. Mobile workstations have their place for site visits and client presentations, and the current generation is good. But they cost more for less, and the fleet should be desktops with a handful of laptops for the people who genuinely travel.

On refresh cycles, three years is the number most practices use and it’s roughly right for drafting machines, because the single-core clock improvement across three generations is what a drafter actually feels. BIM manager machines can stretch to four years if the RAM was specified generously at purchase. The mistake is refreshing on age alone rather than on the model sizes the practice is now handling, which have a habit of growing faster than the hardware budget does.

When the workstation isn't the problem

Before a practice spends on hardware, it’s worth being honest about whether the workstation is the bottleneck at all. A well-specified machine hitting a central model on a NAS that was bought for capacity rather than latency will be slow, and the slowness will look like a computer problem. So will a worksharing setup where sync-with-central takes four minutes because the network wasn’t designed for it. We’ve seen practices buy a fleet to fix a storage problem. The fleet didn’t fix it.

The test

Open a large local copy of the model and time a few common operations, then do the same against the central file. If the local copy is fast and the central is slow, the money belongs in storage and networking, not on desks.

The cloud option, and who it's for

There’s a third path that didn’t exist five years ago. GPU-backed virtual desktops run Revit on a server, and the drafter’s machine becomes a thin client. It works, the performance is real, and it changes the economics for a practice with staff across multiple cities or a lot of contractors. It also introduces a dependency on the connection and a monthly cost that never ends, and for a single-office practice with stable staff it’s usually dearer over three years than buying the machines. We run this as a service and we’ll put the three-year cost side by side with buying, so the decision is made on numbers.

How we specify a fleet

We specify from your models, not from a phone call. The right answer for a practice doing residential work in Revit LT is not the right answer for one doing hospital documentation with linked structural and services models, and any provider who quotes a workstation spec from a phone call is quoting a guess. Bring a representative project to the conversation, ideally the largest one your practice has open right now, and the spec gets a lot more accurate.

N
Editorial team, NexSys

Written and reviewed by the NexSys engineers, design technology specialists and consultants who build and support IT for architecture, engineering and construction firms across Australia. Every price, rule and vendor statement is checked against its source on the date shown.

Last updated 18 Sept 2026
Talk to a consultant

Free, and no sales deck. We reply within one business day.

Or call 1300 733 010

Bring your largest model to the conversation

We specify from your models, not from a phone call. Book a strategic review and bring a representative project, ideally the largest one your practice has open right now.

Or call 1300 733 010

Step 1 of 3

What can we help with?

Pick anything that applies.

Talk to a consultant

Tell us what's going on and we'll get back to you within one business day.

Rather talk now?1300 733 010
What can we help with?

How should we get back to you?

We only use these details to reply to this enquiry. Privacy Policy