CAD Workstation Cleanup: Keeping Huge Assemblies Flowing

Where the gigabytes actually are

The biggest hoarders are the CAD systems themselves. Autodesk Inventor keeps a copy of every save in OldVersions folders next to each part, so a project tree accumulates a full shadow history of itself; on a team share with years of work, OldVersions regularly outweighs the live data. Revit writes journal files to %LOCALAPPDATA%\Autodesk and keeps numbered backup chains like project.0001.rvt next to every model, and AutoCAD scatters sv$ autosave files, .bak saves and .dwl lock files that crashed sessions forgot to clean.

SolidWorks parks auto-recovery files and diagnostic logs wherever its options point, which on a default install is the temp folder nobody watches. Rendering and simulation runs leave their outputs wherever the user last pointed them a year ago, and every crashed session of any CAD application leaves temp litter behind. None of this is exotic — it is the normal byproduct of engineering work, and it compounds quietly because it stays invisible next to the model files people actually open.

• Inventor OldVersions folders — a copy of every save, a shadow history of the whole project
• Revit journals in %LOCALAPPDATA% and numbered .0001.rvt backup chains next to the models
• AutoCAD sv$ autosave files, .bak saves and abandoned .dwl/.dwl2 lock files
• SolidWorks auto-recovery files and Rx diagnostic logs
• Render and simulation outputs parked in the project root since last year
• %TEMP% litter from every crashed session of any CAD app

Clean without destroying work

The rules are strict because the stakes are real. Never touch live model files, and treat project backups as sacred until they are archived deliberately — an OldVersions folder trimmed after a milestone is legitimate, the same folder deleted before a deadline is a career event. Journals and logs are diagnostics, not engineering data: archive the last quarter if a support case is still possible, delete the rest. Lock files (.dwl, .dwl2) are only ever garbage from crashed sessions — but confirm nobody has the drawing open first.

Autosave orphans deserve a look before deletion: open the DWG, confirm it is intact, and only then let the sv$ and .bak files go. And do the math before cleaning shared drives — local cleanup is your business, but a team file server has its own retention rules and someone else's name on the properties. As a rule of thumb for the system drive, keep at least a fifth of the SSD free: below that line, write performance degrades and the machine starts feeling slower in every CAD operation, not just saves.

Keeping it flowing

Performance maintenance for CAD is mostly storage hygiene plus a few habits. Certified GPU drivers over generic ones, and a clean driver install when viewports start misbehaving; Windows Search indexing kept off the project share if you search inside the CAD apps anyway; and a deliberate, documented decision about real-time antivirus scanning of live project folders — IT departments do make such exclusions, but that risk trade-off belongs to whoever owns the data, not to a forum tip.

Schedule the boring part: once a quarter, sweep the autosave folders, temp directories and journal locations, and check the free-space margin on every drive the projects touch. A junk scanner like Kleaner PRO covers the temp-and-leftovers side without going near project files, which is the right division of labor. The CAD seats we support stay fast not because of any single trick, but because the drive never gets close to full and the byproducts never get years to pile up.

Questions and Answers

Read next