Why Revit and AutoCAD Run Slow Over a Network Drive

You hit “open” on a Revit or AutoCAD file. Then you wait. And wait. The spinning circle just keeps going. By the time the model loads, you have already checked your email and refilled your coffee. The technical term for this is Revit slow over network drive performance.

If your files live on a shared network drive or a server, this is one of the most common problems we see at small architecture and engineering firms. The good news is that slow Revit, slow AutoCAD, and “the server keeps crashing” are usually the same problem wearing three different masks. Fix the root cause and all three get better.

Here is the short version. Revit and AutoCAD run slow over a network drive because these programs were never built to work directly off a shared drive. They constantly read and write tiny pieces of the file. Every one of those tiny trips has to travel across your network, and the network adds delay to each one. That delay adds up fast.

Let’s walk through why this happens, and what you should actually do about it.

What a “network drive” really is

First, let’s make sure we mean the same thing.

A network drive is a folder that does not live on your computer. It lives on another machine, like a server in your closet or a network box (often called a NAS, which is short for “network attached storage”). Everyone on your team maps to that same folder so they can share files. You probably see it as a drive letter, like the S: drive or the P: drive.

That setup is great for sharing. One copy, everybody can reach it. We are glad you have a shared spot for your files, because the alternative (files scattered across ten desktops) is much worse.

But here is the catch. Your local hard drive talks to your computer almost instantly. A network drive has to send that same request down a cable, through a switch, over to the server, and back. Even on a fast office network, that round trip takes longer.

Slow is not normal. It is fixable.

Why Revit and AutoCAD make it worse

Some programs open a file once and read the whole thing into memory. Revit and AutoCAD do not work that way.

Revit, in particular, is chatty. It opens a file and then keeps making thousands of small read and write requests while you work. For example, let’s say you open a model with linked files in it (other Revit, CAD, or DWG files attached to the main one). Revit has to go fetch each of those links too. If those links also live on the network, that is a lot of back-and-forth before you even start working.

Autodesk says this directly. Opening files straight from a network location is slow, and nested links on the network make it worse (Autodesk Support).

Saving is its own headache. When Revit saves to a network share, it uses something called “write through.” In plain English, that means Revit refuses to call the save “done” until every last bit of the file has fully landed on the server’s disk. It skips the shortcut that Windows normally uses to speed saves up. So your save bar crawls (Autodesk Support).

This is what we call working “directly off the network.” And it is the thing you want to avoid.

The right way to work on Revit files: local, then sync

Here is the rule that fixes most of this. You should not open and edit a Revit project straight off the network drive. You should work on a local copy on your own computer, and let Revit sync your changes back to the shared file.

This is what Revit calls worksharing. It works like this:

• One main file lives on the server. This is the central file.
• Each person makes their own copy on their own computer. This is the local file.
• You work fast on your local copy, because it is right there on your hard drive.
• Every so often, you hit “Synchronize with Central.” Revit sends only your changes back to the shared file and pulls down everyone else’s.

So you get the speed of working locally and the teamwork of one shared model. You are no longer dragging the whole file across the network every time you click something.

AutoCAD has its own version of this idea. For drawings you are actively editing, copy them local, work, then copy back. For shared content like blocks and templates, point AutoCAD at the network as little as possible, because every reach across the network adds lag (CADnotes).

We have a separate post on setting up Revit worksharing for small firms. If you are sharing one big Revit file off a drive right now, that is the first thing to fix.

Other reasons Revit runs slow over a network drive

Sometimes the slowness is not Revit’s fault and not AutoCAD’s fault. It is the road they have to drive on, let’s check the road.

Old network gear. A lot of small firms are still running on a switch and cabling that were fine ten years ago. If your office network tops out at one gigabit, big BIM models will feel it. Moving the server and the workstations that touch it up to faster connections can make a real difference.

Wi-Fi for heavy files. Wi-Fi is convenient. It is also slower and less steady than a wired connection. For anyone working on big Revit or CAD files all day, you should run a real cable to their desk. Save the Wi-Fi for laptops and phones.

A tired server. The machine holding your files might be the bottleneck. If it is old, low on memory, or still running on spinning hard drives instead of solid state drives (SSDs, which have no moving parts and are far faster), it cannot serve files quickly no matter how good the rest of your network is.

Too much on one wire. If your file server, your backups, and your internet all fight over the same path at the same time, everything slows down. Sometimes the fix is as simple as moving the nightly backup to run after hours.

Here is the honest part. From what we have seen, the cause is often a mix of these, not one single thing. That is why “just buy a faster server” does not always fix it. You have to look at the whole picture, because the slow part might be the cable, the switch, the server, or the way the files are being opened.

What about the cloud? (BIM 360, ACC, OneDrive, Dropbox)

For Revit teamwork, Autodesk does offer cloud worksharing through BIM 360 and Autodesk Construction Cloud. It can work well, especially if your team is spread across more than one office. But it is not magic. Cloud models can be slow to open too, usually when your internet upload speed is weak or the model is huge (Autodesk Support).

One thing you should not do: never point Revit or AutoCAD straight at a basic file-sync folder like OneDrive or Dropbox and edit live project files there. Those tools were built to sync documents, not to handle the constant tiny reads and writes that Revit makes. You will get corrupt files. Microsoft and Autodesk both warn against it. If you want the cloud, use a tool built for CAD and BIM, not a consumer sync folder.

A simple plan to speed things up

If your CAD and Revit files feel slow over the network, here is the order we would tackle it in:

1. Stop editing directly off the drive. Set up proper Revit worksharing so everyone works local and syncs. For AutoCAD, copy the file you are editing to your machine and copy it back when done.
2. Wire the heavy users. Get a real cable to anyone working on big models all day. Take them off Wi-Fi.
3. Check the server’s health. Is it on SSDs? Does it have enough memory? Is it ancient? An old, full, spinning-disk server will always feel slow.
4. Check the network gear. Old switches and slow cabling cap your speed no matter what else you do.
5. Move backups to off-hours. Do not let your nightly backup fight your team for the network during the workday.

Being proactive here is a lot cheaper than being reactive. The reactive version is your team losing fifteen minutes per file open, every day, for years. That is real money and real frustration, and most people just learn to live with it because they think slow is normal. It is not normal. It is fixable.

We are happy to look at it

We help small architecture and engineering firms here in the Knoxville area get their Revit, AutoCAD, and BIM setups running the way they should, so your team can focus on the work, not on watching a load bar. See how we help architecture firms with issues like Revit slow over a network drive.

If your files are crawling over the network, give us a call. We will look at how your files are stored, how they are opened, and where the real slowdown is hiding. No jargon, no scare tactics, just a clear answer.

Written by Austin — Founder & Lead Technician, Aspen IT Group. Managed IT for small architecture, engineering, and construction firms in East Tennessee. Rooted in reliability.