Revit guide
Add-ins, families, cloud collaboration, and what to send support.
Open guideArticle
If Revit, Civil 3D, AutoCAD, ArcGIS Pro, MicroStation, or another design app is slow or freezes when you open a big model, the cause is usually hardware load, file size, network latency, or a setting like background save. Apps rarely "go slow" on their own. Walk these checks before reinstalling or asking for a new computer.
Step One
Is it slow to open the file? Slow to switch views? Slow to save? Slow to plot? Each of those points to a different cause. "Slow" is too vague for IT to act on.
Open a small drawing or model. If the small file works fine, the original file is the issue (size, references, audit). If even small files are slow, the computer or the network is the issue.
Copy the file to your local Documents folder and open it from there. If the local copy is fast and the network or sync version is slow, the problem is the network path, the sync app, or VPN latency - not the app or the file.
Step Two
Press Ctrl+Shift+Esc. Click "Performance." If CPU is at 100% the whole time, the model is bigger than the CPU can keep up with or another process (antivirus scan, Windows Update, OneDrive indexing) is competing. If memory is at 95%+, the model is bigger than RAM can hold and Windows is paging to disk. If disk is at 100% on a spinning drive, you really need an SSD or a beefier computer.
Revit and Civil 3D are memory-hungry. Close Outlook, browsers with 50 tabs, Teams meetings running in the background, or another model open in the background. Re-test.
Windows Update install or restart pending, or a full antivirus scan, can make any large-file app feel broken. Restart, let updates finish, and re-test.
For 3D-heavy apps (Revit, Civil 3D 3D views, MicroStation, Navisworks), out-of-date GPU drivers cause freezes when rotating views. The vendor's recommended driver matters, not always the newest one - check the app's certified driver list.
Step Three
A 500 MB Revit central model on a server across a VPN is going to be slow. A 5 MB DWG on the local C: drive should not be. If a small file is slow, audit the file (in AutoCAD: AUDIT command; in Revit: keep a recent backup and use Audit on open).
Civil 3D and AutoCAD wait a long time for missing xrefs, missing data shortcuts, and unreachable network paths. Open the External References panel - broken paths show up there. Fix the path or unload the missing reference.
Revit Cloud Worksharing, Autodesk Construction Cloud, and ProjectWise can be slow when a save involves syncing back to the cloud. That is normal during sync; if it is slow at all other times, it is a network or saved local data issue.
If a workshared model is corrupt, opening it as Detached with Audit selected can clean it up. Save the audited copy under a new name. Coordinate with the BIM lead before doing this on a live project.
Slow Down
If the project is shared or cloud-hosted, deleting locally can wipe pending changes, break worksharing for the team, or sync the deletion to the cloud copy.
Purge and Audit on a Revit central model or a Civil 3D shortcut project should be coordinated with the BIM lead or CAD manager. Done at the wrong time, this can break references for the rest of the team.
Computers do age out, but most "Revit is slow" tickets are not actually about the computer. Confirm the file size, location, and references first. A new laptop will not save you from a 2 GB central model on a flaky VPN.
If You Need IT
"Revit 2026.1, central model Project-XYZ-ARCH.rvt on Autodesk Construction Cloud." Versions live under Help > About.
"Open is fine but switching to a 3D view freezes for 60 seconds." That is far easier to act on than "Revit is slow."
A screenshot of Task Manager during the slow action - CPU, memory, disk. This often points straight at the cause.
"My BIM team can all open the same model, only mine is slow" -> it is your computer or your network. "We are all slow on this model since yesterday" -> it is the model or the cloud service.
CAD / AEC Notes
Include whether the model is local, central, cloud workshared, or detached; whether Sync with Central is slow; and whether linked models, worksets, or one view make the issue worse.
Include DWG size, xref count, data shortcut paths, surfaces, point clouds, and whether the drawing is opened from a synced or network location. Missing references can make a healthy computer look slow.
For GIS and CAD, note layer count, imagery, terrain, databases, or data sources. For Bluebeam, note PDF page count, markup count, Studio Session status, and whether the PDF is on a network or cloud path.
Related
Add-ins, families, cloud collaboration, and what to send support.
Open guideCountry kits, data shortcuts, and template / standards checks.
Open guideIf the model is on ACC, ProjectWise, or OneDrive and syncing is the bottleneck.
Open articleIf you are slow only when on VPN, Citrix, or a Cloud PC.
Open articleOpen a ticket with the Task Manager screenshot and details.
Open contact page