If you have noticed that Word becomes sluggish, freezes briefly, or lags when typing after about 30 minutes of active editing, you are not alone. This performance drop is often caused by the accumulation of temporary data in the document’s memory cache combined with background processes that Word runs to maintain undo history and AutoSave versions. This article explains the technical reasons behind this slowdown and provides specific steps to reduce or eliminate the lag.
Key Takeaways: Reducing Word Lag During Long Editing Sessions
- File > Options > Save > Keep the last autosaved version if I close without saving (uncheck): Stops Word from retaining large temporary files that slow performance over time.
- File > Options > Advanced > Editing options > Update automatic links at open (uncheck): Prevents Word from repeatedly checking external links, which adds overhead during active editing.
- Ctrl+Shift+End then Ctrl+Space: Clears hidden formatting from the end of a document, which can accumulate and bloat the file size.
Why Word Slows Down After Extended Editing Sessions
Word is designed to maintain a full undo history and continuous AutoSave backups. After 30 minutes of active editing, the following processes consume increasing system resources:
Undo history growth. Every change you make is stored in memory. Word keeps a stack of undo actions. After many edits, this stack can exceed several hundred entries, consuming RAM and CPU cycles when you type or delete.
AutoSave and version accumulation. Word saves a new version every few seconds by default. Each version is stored as a separate file in the temporary folder. Over 30 minutes, hundreds of version files are created, and Word must manage them in the background.
Hidden formatting and content bloat. If the document contains tracked changes, comments, or unused styles, these elements add to the file size. Word must process them every time you scroll or edit, which becomes more noticeable after 30 minutes of work.
Hardware graphics acceleration. Word uses your GPU to render the page. On systems with integrated graphics or outdated drivers, the GPU memory can become saturated after extended use, causing input lag.
Steps to Restore Word Performance During a Long Editing Session
Apply these settings before or during a long editing session. You do not need to restart Word after each change.
Disable AutoSave for Local Documents
- Open Word options
Click File > Options. The Word Options dialog opens. - Go to the Save tab
In the left pane, click Save. - Turn off AutoSave for local files
Under Save documents, uncheck Keep the last autosaved version if I close without saving. This prevents Word from retaining AutoSave files after you close the document. Click OK.
Reduce Undo History Depth
- Open the Registry Editor
Press Windows + R, type regedit, and press Enter. Click Yes if prompted by User Account Control. - Navigate to the Word undo key
Go to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options. Replace 16.0 with your Word version number (16.0 for Office 2016 and later). - Create a new DWORD value
Right-click in the right pane, select New > DWORD (32-bit) Value. Name it UndoHistory. - Set the undo depth
Double-click UndoHistory, set Base to Decimal, and enter a value between 10 and 50. Lower values reduce memory usage. Click OK and close Registry Editor. Restart Word.
Disable Hardware Graphics Acceleration
- Open Word Options
Click File > Options. - Go to the Advanced tab
Click Advanced in the left pane. - Find the Display section
Scroll down to the Display group. - Uncheck hardware acceleration
Uncheck Disable hardware graphics acceleration. This forces Word to use software rendering, which is more stable on older GPUs. Click OK.
Clear Hidden Formatting at the End of the Document
- Go to the end of the document
Press Ctrl+End to jump to the last character. - Select all content from the end
Press Ctrl+Shift+Home to select from the cursor to the start of the document. This highlights everything. - Reset formatting
Press Ctrl+Space to remove direct formatting. Then press Ctrl+Q to reset paragraph formatting. This removes hidden styles and empty paragraphs that bloat the file.
If Word Still Has Issues After the Main Fix
Word Freezes When Scrolling Through a Long Document
If the document contains many embedded images or tables, Word may struggle to render them after extended editing. Switch to Draft view by clicking View > Draft. Draft view disables page layout rendering, which reduces GPU load.
AutoSave Stops Working After 30 Minutes
If AutoSave is on and the file is stored on OneDrive, Word may pause saving if the network connection is slow. Check your internet speed. If the connection is stable, close and reopen the document to reset the AutoSave timer.
Typing Lags Even After Disabling AutoSave
Third-party add-ins can cause performance degradation over time. Disable all add-ins temporarily. Go to File > Options > Add-ins. At the bottom, next to Manage, select COM Add-ins and click Go. Uncheck all add-ins and click OK. Restart Word. If typing improves, re-enable add-ins one by one to find the culprit.
Word Online vs Desktop: Performance Degradation After Extended Editing
| Item | Word Desktop | Word Online |
|---|---|---|
| Undo history limit | Configurable via Registry (default 1000) | Fixed at 100 actions |
| AutoSave behavior | Saves locally every few seconds; can be disabled | Saves to cloud every few seconds; cannot be disabled |
| Hardware acceleration | Can be disabled in Options | Not applicable (runs in browser) |
| Performance after 30 minutes | Slows down due to undo stack and version files | Slows down due to browser memory and cloud sync |
| Best for long editing sessions | After applying the fixes above | Only for short documents under 20 pages |
After applying the steps in this article, you can expect Word to maintain consistent performance during editing sessions lasting over an hour. Start by disabling AutoSave for local documents and reducing the undo history depth to 50. As an advanced tip, create a macro that runs every 15 minutes to clear the undo stack using the Application.UndoClear command. This prevents the undo history from growing too large without losing your ability to undo recent changes.