Quick answer: Close Word, delete the contents of %temp% and %localappdata%\Microsoft\Office\UnsavedFiles, then disable all COM add-ins via File > Options > Add-ins. If that doesn't cut it, set the DisableAutosaveForDraft registry key to 1.
I know this error is infuriating — you've got a 200-page report, you hit Ctrl+S, and Word throws a tantrum about memory or disk space. Most people panic and start deleting files, but the real culprit is rarely your actual RAM or free disk space. It's a combination of bloated temp files, a corrupt autosave cache, and add-ins that leak memory like a sieve. I've seen this on everything from Windows 10 with 8GB RAM to beefy 64GB workstations. The fix is the same.
Why this happens
Word uses a scratch space in your temp folder when saving large documents — especially those with embedded images, tables, or tracked changes. If that folder hits a permission issue or fills with junk, Word chokes. Also, the autosave feature (introduced in Word 2010) keeps a cached version of your doc in %localappdata%\Microsoft\Office\UnsavedFiles. A corrupt autosave file can trigger a false "not enough memory" error on save, even when everything else is fine.
Fix steps (in order of effectiveness)
Step 1: Clear the temp and autosave folders
This is the first thing I do, and it works about 70% of the time. Close Word completely. Then open File Explorer and paste this into the address bar:
%temp%
Select everything in that folder and delete it. Windows will skip files in use — that's fine. Then go to:
%localappdata%\Microsoft\Office\UnsavedFiles
Delete everything in there too. Now reopen Word and try saving. If it works, you've got your document back. If not, move to step 2.
Step 2: Disable COM add-ins
Third-party add-ins — especially PDF converters, citation managers, or document comparison tools — are notorious for leaking memory when you save. They hook into Word's save routine and bloat it. To check:
- In Word, go to File > Options > Add-ins.
- At the bottom, set "Manage" to COM Add-ins and click Go.
- Uncheck every add-in listed. Don't worry, you can re-enable them later.
- Click OK and try saving again.
If that fixes it, re-enable add-ins one by one to find the troublemaker. In my experience, it's almost always a PDF tool.
Step 3: Turn off autosave
Autosave is great, but it's also the source of this error on larger files. Word keeps a backup in memory, and when that backup gets corrupted, saving fails. To disable autosave just for draft documents (so you don't lose the feature entirely on files saved to OneDrive):
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options
Create a new DWORD (32-bit) value named DisableAutosaveForDraft and set it to 1. Restart Word.
Step 4: Check disk space and file permissions
Sometimes the error is literal. If you're saving to a network drive or a USB stick, Word can misread available space. Make sure you have at least 1GB free on the drive where the file resides. Also, right-click the folder you're saving to, go to Properties > Security, and confirm your user account has "Full control" or at least "Write" permission. This matters more on corporate PCs.
Step 5: Replace the document content into a new file
This is the nuclear option, but it works when the file itself is corrupted. Open the document, then press Ctrl+A to select everything, copy it, and paste into a brand new blank Word document. Then save that. You'll lose some formatting quirks, but you won't lose your work.
If the main fixes don't work
Try opening the document in Word's Safe Mode (hold Ctrl while launching Word). If it saves fine there, it's definitely an add-in. Also, run a repair on Office: go to Control Panel > Programs > Microsoft Office > Change > Quick Repair. That's fixed weird memory errors for me more times than I can count.
Prevention tip
For documents over 50MB, split them into sections if you can. I know that's a pain, but large files with heavy embedded content will always strain Word. Also, get in the habit of clearing the temp folder once a month — it's a 30-second chore that prevents a 2-hour headache later. And if you're on a corporate laptop with a managed Office install, don't fight the system: use the repair tool first, then the registry tweak above.
One last thing — if you're still hitting this after all that, check whether you're on a 32-bit version of Office. Switch to the 64-bit version if you can. The 32-bit version has a hard 2GB memory ceiling, and large documents will smash into it. That's not a fix, that's a root cause.