Errors & Fixes
SOLIDWORKS "Failed to save document" — how to fix it
When SOLIDWORKS refuses to save, the first job is to keep your work: save it under a new name on a local drive. Then find the cause. CATI traces most "Failed to save document" errors to minor corruption in an assembly or one of its parts, typically when saving across a network; cloud-sync folders, read-only files, very long paths and antivirus scanning are the other usual suspects.

Applies to: SOLIDWORKS 2018–2027 parts, assemblies and drawings.
Most likely causes
- Minor corruption in the assembly or a part, often after network saves (most common)
- A cloud sync tool holding the file while SOLIDWORKS writes it (common)
- Windows read-only attribute, or a PDM file not checked out (common)
- Folder and file path longer than Windows allows (occasional)
- Antivirus scanning SOLIDWORKS files and processes (occasional)
Fix order at a glance

- Save As a new name to a local folder — keep the work.
- Ctrl + Q, fix rebuild errors in every configuration, Save All.
- Add-ins off.
- Pack and Go to a clean folder.
- Rebuild the file into a new document.
Save as previous version is a different thing
If you need to hand a file to someone on an older release, that is not an error: since SOLIDWORKS 2024 Save As offers earlier releases — two back from the version you are in — for parts, assemblies and drawings, with the feature tree. It needs an active subscription, and features the older release lacks are flagged by a check and must be deleted. More in version compatibility.
Avoiding save problems
- Open and save on a local drive; copy back to the server when you finish.
- Keep projects out of cloud-synced folders while you work, and use Pack and Go to move them.
- Keep paths short — a project folder near the drive root is safer than one buried in nested folders.
- Save often, and turn on Backup in Backup/Recover so a failed save does not cost a day's work.
Fixes, in order
1. Save a copy locally right now
File → Save As with a new name to a local folder (the Desktop will do if the original is on a network or in a cloud folder). This keeps your changes while you work out the rest.
2. Rebuild, check configurations, save all
CATI's sequence: Save All, force a full rebuild with Ctrl + Q, step through every configuration fixing rebuild errors and saving, and check recently edited parts for errors. See rebuild errors.
3. Turn off add-ins
Disable all add-ins under Tools → Add-Ins and try again. If the save works, re-enable them one at a time.
4. Pack and Go the whole assembly
File → Pack and Go copies the assembly and every referenced file to a new folder with their references intact — a clean set to keep working on. Use it for every move, copy and rename.
5. Get the file out of the sync folder
GoEngineer advises against working inside non-CAD-aware cloud storage: a sync tool can take hold of a file mid-save and corrupt it. Save As with a new name, then work locally or pause sync.
6. Check read-only status
Clear the Windows Read-only attribute in the file's Properties, or check the file out in PDM. See read-only files.
7. Shorten very long paths
Deep folder structures with long names can exceed Windows' path limit (File Name Too Long). Shorten folder and file names, or enable long paths in Windows (Group Policy Enable win32 long paths, or the LongPathsEnabled registry value) and restart.
8. Exclude SOLIDWORKS from antivirus scanning
Hawk Ridge notes antivirus can slow Open, Save and Save As and cause runtime errors. Ask IT to exclude SOLIDWORKS processes such as sldworks.exe, plus SOLIDWORKS file types and work folders.
9. Rebuild the file into a new one
Still failing? Parts: Insert → Part into a new part and break the external references. Assemblies: insert into a new assembly and Dissolve Subassembly. Drawings: copy the sheets into a new drawing. Details in corrupted files.
Sources
- CATI — The Dreaded Failed to Save Document Error (Sep 2008)
- Hawk Ridge Systems Support — Unable To Save File
- GoEngineer — Cloud file management recommendations (Oct 2025)
- GoEngineer — SOLIDWORKS - Accessing and Deleting Long File Names and Paths
- Hawk Ridge — Antivirus recommendations for SOLIDWORKS
- Hawk Ridge Systems — Managing Read-Only Access in SOLIDWORKS (Apr 2019)
- GoEngineer — SOLIDWORKS PDM: A File is Checked Out, But Still Read-Only (Jun 2017)
Checked November 2026. SOLID WORKS Club is independent; menu names can differ slightly between releases.
Frequently asked questions
Why does SOLIDWORKS say "Failed to save document"?
+
Most often minor corruption in the assembly or one of its parts, usually after saving across a network. Cloud sync, read-only files, long paths and antivirus are other causes.
How do I keep my work when SOLIDWORKS will not save?
+
Save As with a new file name to a local folder such as the Desktop, then Pack and Go the assembly once it saves.
Can I save a SOLIDWORKS file to an older version?
+
Since SOLIDWORKS 2024, Save As can save parts, assemblies and drawings up to two releases back with an active subscription. Features the older release does not have must be deleted first. See future version files for the opposite direction.
Related
- Corrupted SOLIDWORKS file — how to open and recover itRecover a corrupted SOLIDWORKS file: the built-in repair, AutoRecover .SWAR files, Advanced open for assemblies, and rescuing the geometry from a bad part.
- SOLIDWORKS file is read-only — why and how to fix itFix SOLIDWORKS files that open read-only: someone else has them open, the Windows read-only flag, PDM check-out, Get Write Access and multi-user options.
- SOLIDWORKS file saved in a newer version — how to open itSOLIDWORKS says a file was saved in a newer version? Your options: Future Version mode on SP5, Save As previous version from 2024, STEP and eDrawings.
- SOLIDWORKS rebuild errors and warnings — how to fix themFix SOLIDWORKS rebuild errors: red and yellow feature icons, the What's Wrong dialog, dangling references, zero-thickness geometry and failed fillets.