AutoCAD slows down on network folders: cache, paths, DWG rules

Why AutoCAD slows down on network folders

The situation is usually the same: a drawing opens noticeably slower, saving causes pauses, and sometimes regenerations or switching sheets «hang». The PC itself may be fine, while delays appear only on projects stored on the server.

The reason is often simple: the network is almost always slower and less reliable than a local SSD. AutoCAD reads and writes not only the DWG. It constantly accesses temporary files, autosave, fonts, support paths, external references and underlays. On a local disk this is barely noticeable, but over the network every small operation becomes a wait.

It’s usually more effective to speed up three things rather than everything at once: opening DWG (initial load and locating dependent files), saving (main file plus service writes) and autosave (pauses every N minutes).

The good news is some improvements can be made without reinstalling software or admin rights. Simple steps help: move TEMP and the autosave folder to a local disk, shorten long support paths, remove unnecessary network locations from the search, and agree on clear project storage rules.

A typical story: DWGs are on the server and autosave also writes there. Every 10 minutes everyone experiences short «stops» and AutoCAD seems to freeze. Moving autosave to the local disk often removes those pauses immediately, even if projects remain on the server.

Quick diagnosis: where time is lost

First understand what is actually slow: the file itself, the network, or the environment (references, fonts, support paths). This usually takes 10–15 minutes but lets you fix the real cause instead of everything at once.

Start with a simple comparison. Take the same DWG and open it locally (copied to drive C:) and from the network share. If the difference is large, the issue is usually the network, permissions, antivirus scanning, handling of references, or AutoCAD repeatedly searching resources over network paths.

Check more than just opening. On one test file measure several operations because “slow” means different things to different people:

• Opening the file (time until commands are fully responsive)
• Save and SaveAs (time until the save indicator disappears)
• Autosave (felt pauses every N minutes)
• Plot (time to preview and start printing)
• Closing the file (sometimes long due to writing temp data)

Then determine the scope: slow in one project or all DWGs on the server. If it’s one project, Xref, underlays, nonstandard fonts or heavy external resources are often to blame. If it’s everywhere, network latency, VPN, security policies or user profile issues are likely.

Check dependence on time of day and VPN. A simple sign: everything flies in the morning but “sticks” during the day when saving. That means the network is congested or the file server has queues.

For IT it’s useful to gather a few numbers:

• DWG size
• Number of Xrefs and their total size
• Timings: Open, Save, SaveAs, Plot

Example: an 80 MB file with 12 Xrefs opens locally in 25 seconds but over the network in 2 minutes; Save takes 40 seconds during the day. That’s a clear signal where to look and what to compare after changes.

Local cache and temp folders: what to move off the network

While working AutoCAD constantly creates service files: temp copies, logs, cache for reopening, autosave files and backups. These are working traces that help the program read faster and recover after a crash.

The problem starts when these folders are on a network drive. Then every autosave and small operation becomes network traffic: more delays, more permission checks, more lock conflicts. The program feels slow even if the DWG itself is small.

It’s almost always worth keeping locally (on the user’s C drive or another fast local disk): Windows temporary folders (TEMP/TMP), AutoCAD autosave folder, user local data (usually AppData), and a separate working folder for unpacking and temporary exports if you use them.

If you use roaming profiles stored on the server, ask IT to exclude heavy and frequently changing directories from sync (usually AppData\Local and temp folders). Otherwise login, logout and even working will cause constant synchronization and AutoCAD will wait on the network.

Cleaning junk helps too, but carefully. It’s safer to delete only clearly temporary items (old files in TEMP, app caches) and keep drawing backups until verified.

A short rule: delete .sv$ and .bak only if you are sure the needed data is already saved and checked in the DWG. If there were freezes or lost changes, first find the latest autosaves, open them, and only then clean folders.

Step-by-step: set up cache, TEMP and autosave

Often delays are caused not by the DWG but by temp files: cache, autosaves and backups. There are many of them, they are constantly created and removed, and over the network that turns into latency.

1) Move all temporary data to a fast local disk

Create one clear local folder on an SSD, for example C:\CAD_Temp\. Then configure AutoCAD to write everything possible there and leave only final DWGs on the server.

Choose a local folder for Windows temporary files (TEMP/TMP) and make sure there’s enough free space. In AutoCAD open Options and in the Paths section point the autosave and temp folders locally (if configurable in your version). Verify the user has rights to create and delete files in those local folders. A frequent cause of slowdowns is files being created but not able to be overwritten correctly.

Also set rules for backups: whether .BAK is enabled, autosave frequency, and how many service files are kept. More frequent autosave and more copies means more write operations.

Measure results: time opening and first saving the same DWG before and after changes.

Example: a DWG on the server where each save takes 20–30 seconds. After moving autosave and TEMP to C:\CAD_Temp\ the delay often drops to a few seconds because the network is no longer involved in constant service-file writes.

The main idea: projects can stay on the server, but all temporary and autosave files are better kept locally on a fast disk.

Support paths: how to reduce startup and open delays

At startup and when opening a drawing AutoCAD walks support paths looking for needed files. These typically include fonts (SHX, TTF), templates (DWT), title blocks and blocks, plot styles CTB/STB, scripts and LISP. If the list contains many network folders and long paths, delays add up.

Every extra folder is an additional network access. If some paths are unreachable, AutoCAD waits for timeouts before proceeding.

How to speed up without losing order

Keep only what you actually need every day in the support paths and, if possible, keep those items local. A practical approach is to have two layers: local (fast) and shared (team).

Locally place fonts, CTB/STB, the most common blocks, and frequently autoloaded LISP. On the server keep rare libraries, archive templates and large content accessed infrequently.

Check the support paths list for duplicates and dead entries (old servers, renamed shares, temporary folders). Aim for a short, clear list: better 3–6 meaningful folders than 20 «just in case» entries.

Agree on a unified structure

So the team doesn’t each build their own support set, lock a simple structure: where CTB live, where fonts live, where templates live. A new user then gets a ready set of paths and IT can manage access and backups more easily.

Rule of thumb: everything that affects opening each file (fonts, plot styles, autoloaded LISP) should be as close as possible to the workstation. Other resources may remain on the server but in one pre-agreed location.

DWG storage rules on the server: structure and order

Sometimes the issue is not network speed but chaos on the file server. Folders with thousands of DWGs, backups, PDFs and old versions make Explorer, antivirus and AutoCAD take longer to search, check permissions and update metadata. Opening, saving and even Save As become slower.

A clear rule: one project — one root folder. Inside keep a stable structure so paths don’t change and references don’t break.

A minimal structure can be:

• 01_Work (working DWGs)
• 02_Xref (all external references and underlays)
• 03_Plot (PDF, DWF, releases)
• 04_Exchange (exchanges with contractors)
• 05_Archive (frozen versions, read-only)

This makes cleanup and permission setup easier and reduces the folders AutoCAD and the server must process during searches.

For Xref two rules work well: keep all references in one folder (e.g., 02_Xref) and use relative paths to them. Then the project can be moved to another network location or server and references remain valid. AutoCAD also won’t try to find the same file across many different paths.

Naming and versioning rules help too. Choose a simple format (for example Object_Part_Floor_Date), avoid names like “drawing(1).dwg” and duplicates like “final_final”. If history is needed, store it in Archive with clear labels rather than next to working files.

Example: a department kept 30,000 files in a single “Project” folder. After splitting into Work, Xref and Archive, reference resolution and saving became noticeably faster because AutoCAD and the server stopped processing many unnecessary objects.

References, fonts and underlays: hidden sources of delays

Delays often come not from the DWG itself but from its «wrapping»: Xrefs, images, PDF underlays, fonts and plot style tables. Each network lookup adds seconds or minutes.

How to tell if the wrapping is the problem

If the drawing opens but the cursor stalls and status shows loading or recalculation, check whether the file pulls dozens of references and underlays. It’s especially slow if resources are on different network locations or some paths no longer exist.

What finds the problem quickly:

• Open the External References palette and check for “Not found” statuses.
• See where underlays (PDF, DGN, images) are located and how large they are.
• Confirm whether nonstandard SHX/TTF fonts are used and where they are stored.
• Check CTB/STB plot styles: AutoCAD may search for them repeatedly across long network paths.

Practical storage that actually speeds things up

Keep heavy underlays next to the project and use relative paths. When you move the project folder to another server or drive nothing breaks and AutoCAD stops roaming the network for missing files.

A common cause of slowdowns is missing fonts and CTB. If a file is absent, AutoCAD may try multiple times across all support paths. The usual fix is a single agreed set of fonts and plot styles, and a short clear path to them (preferably local, or at least one shared network location without duplicates).

If a frequently used base file is opened by many people, don’t make it a working drawing. Better keep it as a read-only Xref; edit it via a separate file and a controlled update process. This reduces locks, save conflicts and accidental hangs.

Team work and saving: reduce risk of loss and hangs

In many teams the issue appears not when opening but when saving. The network adds latency and AutoCAD tries to protect files from concurrent edits.

When you open a DWG for write, lock files (DWL/DWL2) appear next to it. They prevent a second person from overwriting your work. Conflicts arise when locks don’t get created in time, remain after a connection drop, or the file is opened in different ways (wired vs Wi‑Fi vs VPN).

An unstable connection is dangerous because a save may hang mid-operation. Best case you lose recent edits; worst case you get a corrupted DWG or a permanent lock preventing colleagues from saving.

Simple separation of rights and roles helps a lot. Set clear rules:

• One file — one editor during edits
• Separate editing area (WIP) and view-only area (ISSUED/VIEW)
• No editing from Archive/Issued folders
• Unified access method to the server (avoid mixing different paths and shortcuts)
• If a DWG is «busy», first find who is working before deleting DWL files

To avoid copies named (1), (2), (final), use a short strict version scheme such as REV01, REV02 or date in format 2026-01-28. Keep interim versions in a separate _WIP folder and publish only approved variants to Issued.

If the network frequently drops (remote site, construction site, VPN), it’s safer to work locally: take a project copy to a local folder, make edits, and upload to the server according to rules (for example end of day or after a checkpoint). This reduces save hangs and makes it easier to track who changed what.

Common mistakes that prevent speed gains

If everything stays the same after «optimization», the cause is usually habits and small settings that repeatedly pull data over the network.

Most frequent mistakes:

• Temp files and cache remain on a network drive or inside a roaming profile. Then every autosave and open sends megabytes over the network.
• Support paths contain too many network folders (or the root of a shared drive was added). At startup and print time AutoCAD searches many locations for fonts, CTB, templates and LISP.
• Projects dumped into one shared folder without structure. Xrefs, underlays and images are scattered, duplicate names appear, and people open the wrong versions.
• Workstations lack a unified set of fonts and plot styles (CTB/STB). AutoCAD searches the network for them, substitutes, recalculates and slows down regeneration and output.
• Work proceeds over a slow link with no local workflow. Even good settings won’t help if heavy DWGs with Xrefs are opened and saved directly through an unstable VPN.

Typical example: projects in a single network folder while half the team stores CTB on their local disk. At print time AutoCAD searches the network, doesn’t find the expected table, substitutes another and the user blames the server.

Noticeable speed gains come when you fix the basics: TEMP and autosave local only, short and exact support paths, and clear storage rules (project structure, unified Xref, font and plot style folders).

Short checklist before contacting IT

Before reaching out to IT separate configuration problems from infrastructure problems. Often a few checks show where to dig next.

First ensure all temporary data is local:

• TEMP and TMP point to a local drive (e.g., C:) and you have write rights
• Autosave folder is local and accessible
• Backup files (BAK) are not written into a network profile or redirected Documents
• Project working folder is not synced live via cloud services
• There is enough space on the local disk (at least a few GB free)

Then check settings that commonly add delays. The goal is simple: fewer network calls at startup and when opening.

• Support paths contain only the minimum needed and network paths are last in the list
• Fonts and plot files (CTB, STB, PC3) are in one clear place without duplicates
• Xrefs are attached using consistent rules: identical relative paths and a single folder structure inside the project
• Underlays (PDF, images) and point clouds are not pulled from random folders on different servers
• Antivirus does not scan every AutoCAD temp file in real time (at least exclude TEMP and Autosave)

A mini test for facts: take the same DWG, open it locally (copy to C:) and measure time. Then open it over the network and compare. If the difference is large, the problem is almost certainly not the drawing itself.

Bring IT in if local performance is fast but network performance is slow, or if you see permission errors, long save hangs, or time-of-day variability. When contacting IT include server name and path, DWG sizes, local vs network open times, and whether Xrefs and underlays are present.

Example: speeding up a department where DWG are on a server

A team of 10 engineers works with projects from 5 to 200 MB. All DWGs are on one file server and over time opening and saving became noticeably slower. Workstations were fine; delays were caused by the network, server antivirus and constant access to many small files (fonts, templates, Xref).

The fastest effect usually comes from one simple logic: keep the server as the single repository for projects, but move everything AutoCAD reads and writes constantly to local disks. Projects stay in the network repo while temp files, autosave and part of the cache live locally.

Basic team rules:

• Each project on the server has a fixed structure: Work, Xref, Export/Plot, Archive.
• A shared Exchange folder exists but it is forbidden to attach Xrefs from it in working drawings.
• Xrefs and underlays are stored next to the project and attached with relative paths.
• Archiving is done in batches (e.g., weekly) so working folders don’t grow uncontrolled.

To prove the effect don’t argue about feelings. Measure before and after three actions on the same file: open time, first save time and Save As time into the same project.

Next steps after quick settings: a short audit of network and server disk subsystem, check antivirus policies for DWG and temp files, and then right-size workstations and servers for real load. If an upgrade plan is needed, systems integrators like GSE.kz usually start with measurements and diagnostics and then propose server and workstation configurations.

What to do next: lock settings and tidy up

One-off changes help, but steady speed comes when you lock a standard for the whole team. If slowdowns return it’s usually due to mixed paths, saving habits and a chaotic set of projects.

Start by gathering facts: where DWGs live, where fonts and templates are taken from, where TEMP, autosave and cache are written. This can be done in 1–2 hours and gives a clear picture.

A practical plan:

• List current paths: projects, support, fonts, templates, temp folders
• Approve a standard: DWG and shared resources on the server; cache and temp files local only
• Define project folder structure and naming rules so references and underlays don’t wander
• Put the standard in a short instruction and assign an owner
• Test the standard on 2–3 typical projects: open, save, resave, package and check references

If delays remain after the standard, look for infrastructure bottlenecks. Check server storage latency (IOPS and queue times), network load at peak hours, permission setups and antivirus on network folders.

When the issue hits server, storage or workstation limits, involve an integrator. GSE.kz can help select and implement servers and workstations and provide system integration and 24/7 support so AutoCAD configuration improvements are backed by stable storage and network.