Revit IT Requirements: What Your Studio’s Workstations, Network and Storage Actually Need

Most architecture firms buy Revit machines the same way they buy accounting laptops, then wonder why a 25-minute sync has become normal. The hardware Revit needs isn’t a mystery. Autodesk publishes it, model size drives most of it, and the rest is the network and storage the model sits on. This guide is for principals, BIM leads and office managers at Ontario studios of roughly 15 to 80 people, and it sits alongside our broader guide to IT for architecture firms.

I’m Jeffrey Bowles, Partner and Director of IT Services at ACT360. Below you’ll find Autodesk’s current requirements in plain terms, how to pick the right tier for each person, why clock speed beats core count, and the network and workset habits that decide whether good hardware actually feels fast.

Revit 2027 runs only on 64-bit Windows 11. Autodesk lists 16 GB of RAM as the minimum, 32 GB as its balanced tier and 64 GB for large, complex models, with a DirectX 11 graphics card carrying 4 to 8 GB of video memory.

Here are the three tiers from Autodesk’s system requirements for Revit 2027 products, which Autodesk labels entry-level, balanced price and performance, and large, complex models.

Revit 2026 is different on one line that matters. Its requirements still allow Windows 10 version 1809 or later. But Windows 10 reached end of support on October 14, 2025, and Revit 2027 drops it entirely. Any studio machine still on Windows 10 is both unpatched and unable to run the current release. That makes it the first line on a refresh plan, ahead of RAM or graphics.

Autodesk also notes that models created in earlier versions may need more memory for the one-time upgrade. If a large project is about to move up a release, do it on the strongest machine in the office.

Pick the tier from the largest model each person opens, then add the size of the models linked into it. Autodesk ties 16 GB to models up to about 300 MB, 32 GB to about 600 MB and 64 GB to about 1 GB.

That model-size column is the most useful line in Autodesk’s whole table, and it’s the one most firms skip. Before you buy anything, have someone sort the project folders by file size and look at the 5 largest central models. Linked structural and MEP models load into memory too, so a 450 MB architectural model with two consultant links can push a 32 GB machine past its comfortable range.

A common pattern: the whole studio gets the same laptop, the 2 people on the hospital or school project struggle every day, and everyone else is over-equipped. Spending more on those 2 machines and less on the rest usually costs the same and fixes the actual complaint.

Because a lot of everyday modelling waits on one core at a time. Autodesk recommends the highest single-core base clock speed, while noting that Revit uses multiple cores for many tasks, so a fast-clocked processor usually beats one with more, slower cores.

This is where well-meaning purchases go wrong. A workstation with a very high core count and a modest clock speed can look impressive on a quote and still feel sluggish when someone edits a wall or switches views. Rendering and some exports do spread across cores, so firms that render heavily in Revit get value from both. For most design work, though, clock speed is the number to compare first.

The same logic rules out a common shortcut. Running Revit on a spare server or an old high-core machine “because it has lots of cores” rarely helps.

A card that supports DirectX 11 and Shader Model 5, with 4 GB of video memory at minimum and 6 to 8 GB for larger models. Autodesk’s Accelerated Graphics mode needs OpenGL 4.5, with 8 GB or more recommended.

Graphics certification also works differently than it used to. Autodesk’s hardware certification FAQ explains that since Revit 2023.1, the old certified-card status has been replaced by a direct report on whether the system’s DirectX version, Shader Model and available graphics memory meet the hardware acceleration requirements. In practice, that means checking each machine in Revit itself rather than trusting a card name on a spec sheet.

Two practical points:

• Drivers matter as much as the card. Keep one tested driver version across the studio and update deliberately, not whenever a pop-up suggests it.
• Laptops are the weak spot. Thin laptops with shared graphics memory can technically run Revit and still struggle once views get busy. Anyone doing real modelling on a laptop needs one with its own graphics memory.

More free space than people expect. Autodesk lists 30 GB to install Revit and recommends 100 GB free for temporary files, and every person working on a workshared model keeps a local copy of it.

A 512 GB drive fills quickly once you add Revit, other Autodesk products, local copies of several central models and Windows updates. When the drive gets tight, saves slow down and temporary files fail in ways that look like model problems. We recommend a fast solid-state drive for modelling machines, with enough room that the 100 GB temp recommendation is still met a year later.

Cloud worksharing changes the sums again. Autodesk’s requirements page says Revit Cloud Worksharing needs about 3 times the disk space of the equivalent RVT files, because of how it caches models locally.

Because worksharing depends on the path between the workstation and the central model. Autodesk links slow or failed syncs, “Central Model is busy” errors, crashes and model corruption to file-based worksharing over a WAN or VPN.

Autodesk’s support article on file-based worksharing over a WAN or VPN lists those symptoms in detail. In practice, a new 64 GB workstation at home, connected over a VPN to a central file on an office server, can feel worse than an older machine plugged into the office network.

• In the office: wire the modelling desks, keep the central model on fast server storage, and keep it on the same network as the people syncing.
• For remote staff: use an option built for distance, such as a remote session into an office workstation, a cloud desktop, Revit Server or Revit Cloud Worksharing.
• For cloud worksharing: Autodesk lists symmetrical connections of 5, 10 or 25 Mbps per machine for burst transfers across its three tiers, so check upload speed at home, not just download.

Choosing between those options is a bigger decision than this article can settle. We walk through it on our BIM IT support page.

Open less of the model. Autodesk says closing worksets you don’t need releases memory for Revit, and recommends opening workshared projects selectively instead of loading everything every time.

Hardware sets the ceiling, but habits decide how close you get to it. Autodesk’s help page on worksets and performance gives a short list that any BIM lead can adopt:

1. Split big projects into worksets by building, core and shell, or other logical areas.
2. Put links and imports on their own worksets and close them when nobody needs them.
3. Open only the worksets needed for the task in front of you.
4. Borrow elements rather than checking out whole worksets, which Autodesk calls the general best practice.

None of this needs new hardware. It’s often the cheapest performance gain a studio can make, and it buys time before a refresh.

On a Mac, Revit runs inside Windows through Parallels Desktop, which Autodesk recommends, with 32 GB of memory listed. Remote and cloud desktops are often the better route for designers who need a strong machine away from the office.

Revit is a Windows application, so a Mac user is really running a Windows virtual machine. It works for lighter use, but it’s worth testing a real project before standardizing on it. For mostly remote teams, a cloud-hosted desktop keeps the model next to the compute and sends only the picture to the person’s screen. Graphics-capable cloud machines cost more than standard ones, so size them to the work. Our cloud migration page explains how we plan a phased move like that without stopping live projects.

Answer these 6 questions before buying a single workstation. Together they tell you which machines need replacing, which need memory, and which problems hardware won’t solve.

1. Which machines are still on Windows 10? They can’t run Revit 2027 and no longer get security updates.
2. How big are your 5 largest central models, with links? That sets the RAM tier for the people who open them.
3. Which Revit release is each live project on? One release per project, installed on every machine that touches it, saves a lot of grief.
4. Where do slow syncs happen? If it’s mostly at home or in a second office, look at the network before the workstation.
5. How much free disk space is left on modelling machines? Less than Autodesk’s 100 GB temp recommendation is a warning sign.
6. Who owns graphics drivers and Revit updates? Without an owner, every machine drifts to a different version.

CAD-heavy engineering teams face a similar list. Our CAD IT support page covers it for AutoCAD and other design software.

We look before we recommend. Through the Assess and Comprehend steps of our ACTION approach, we inventory each workstation against Autodesk’s tiers, check Windows versions and free disk space, measure where syncs slow down, and ask your BIM lead which projects and people are hurting most. Often the answer is 2 or 3 targeted upgrades, a network fix and a workset cleanup, not a studio-wide refresh.

Workstation and server hardware is quoted when you need it, and the ongoing support sits inside ACT360 Managed IT, priced per user per month. For a breakdown by studio size, see IT support costs for architecture firms. If you’d like the wider picture of where studios struggle, read why architecture firms struggle with IT.

Revit performance is rarely one big problem. It’s usually a Windows 10 machine nobody replaced, a 16 GB laptop on the biggest project, a central model reached over a VPN and a project nobody split into worksets. Fix them in that order of cost and most studios get their afternoons back without buying a room full of new hardware.

If you’d like a second opinion on your setup, our free IT Readiness Assessment looks at your workstations, network and models and gives you a short list of what to fix first. You can also call 705-739-2281 or email [email protected].