When you save a document in Word, you may notice that a temporary .tmp file is created in the same folder each time, rather than the existing .tmp file being updated. This behavior can cause confusion, especially if you are monitoring file activity or troubleshooting disk space usage. The root cause lies in Word’s save architecture, which uses a write-to-temp-then-rename strategy to prevent data corruption. This article explains the technical reason behind this design and shows you how to verify it, along with related behaviors you should understand.
Key Takeaways: How Word’s Save Process Creates a New .tmp File Each Time
- Write-to-temp-then-rename strategy: Word writes the entire document to a new .tmp file, then deletes the original and renames the .tmp to the .docx name, ensuring an atomic save that prevents corruption if the process is interrupted.
- No incremental updates to .tmp files: Word never modifies an existing .tmp file in place; it always creates a new one because the old .tmp file no longer exists after the rename step completes.
- File > Options > Save > Save AutoRecover information every N minutes: This setting controls how often Word creates a new .tmp file for AutoRecover, separate from manual saves, and each AutoRecover save also uses a fresh .tmp file.
Why Word Uses a New .tmp File for Every Save Operation
Word does not update the existing .tmp file because the save process is designed to be atomic. An atomic save means that either the entire save succeeds, or the original file remains untouched. To achieve this, Word writes the full document content to a brand-new temporary file with a random name in the same folder as the original document. After the write completes successfully, Word deletes the original document file and renames the temporary file to match the original file name. The old .tmp file from the previous save no longer exists at this point — it was either deleted during the previous save cycle or never had the same name.
The temporary file is created with a .tmp extension but a unique base name generated by the system (for example, ~WRD0001.tmp). Each save operation generates a new random name, so you see a new file appear and then disappear as the rename occurs. If you watch the folder during a save, you will see a .tmp file appear briefly and then vanish, replaced by the updated .docx file. This mechanism protects against data loss: if Word crashes while writing the .tmp file, the original .docx file remains intact because it has not been deleted yet.
Another reason Word recreates the .tmp file each time is that the old .tmp file is already gone by the time the next save begins. After the rename step, the temporary file is no longer a .tmp file — it is now the .docx file. So there is no existing .tmp file to update. The next save starts fresh, creating a new .tmp file from scratch. This is consistent across all versions of Word for Windows, including Word 2016, 2019, 2021, and Word for Microsoft 365.
The Role of AutoRecover .tmp Files
Word’s AutoRecover feature also creates .tmp files, but those are stored in a different location by default (usually C:\Users\[username]\AppData\Local\Microsoft\Word\). Each AutoRecover save creates a new .tmp file in that folder, not in the document folder. These files are named with the pattern ~WR[A-F0-9]{8}.tmp. When Word restarts after a crash, it scans this folder for .tmp files and offers to recover them. The same atomic save principle applies: Word writes the entire recovery data to a new .tmp file, then renames it to a .asd file (AutoRecover file) after the write is verified.
Steps to Observe Word’s .tmp File Behavior
You can verify the save process yourself using File Explorer. This helps confirm that Word is not updating an existing file but creating a new one each time.
- Open the document folder in File Explorer
Press Win+E to open File Explorer and navigate to the folder where your Word document is saved. Arrange the view by Details and add the Date modified column if not already visible. - Open the Word document and make a small change
Open the document in Word. Type a single character or delete a space. Do not save yet. - Press Ctrl+S to save
Watch the File Explorer window. You will see a new .tmp file appear in the list for less than a second, then disappear. The original .docx file’s Date modified timestamp will update immediately after the .tmp file vanishes. - Repeat the save multiple times
Make another trivial change and press Ctrl+S again. Each time, a new .tmp file appears briefly. The file name of the .tmp file will be different each time (for example, ~WRD0002.tmp, then ~WRD0003.tmp). - Check the AutoRecover folder
Open File Explorer and paste this path into the address bar: %AppData%\Microsoft\Word. You will see .tmp files there as well, created by AutoRecover saves. Note that these .tmp files persist until Word deletes them after a successful recovery or document close.
Common Misconceptions and Edge Cases
Why Does the .tmp File Sometimes Stay Behind?
If Word crashes or is terminated during the save process — after the .tmp file is written but before the rename completes — the .tmp file remains in the folder. This is a leftover from an interrupted atomic save. When you reopen Word, it may prompt you to recover the document from that .tmp file. If you do not see a recovery prompt, you can manually rename the .tmp file to .docx and open it. Word will attempt to repair the file if needed.
Does Word Ever Update a .tmp File In Place?
No. Word never modifies an existing .tmp file. The save design always writes a new file. This is a deliberate choice to avoid partial writes that could corrupt the file. Even if the .tmp file were still present from a previous interrupted save, Word would not reuse it; it would create a new one with a different name.
Can I Reduce the Number of .tmp Files Created?
You cannot change the core save mechanism, but you can reduce the frequency of AutoRecover .tmp files. Go to File > Options > Save and increase the minutes in “Save AutoRecover information every N minutes.” The default is 10 minutes. Setting it to 20 or 30 reduces the number of temporary files created by AutoRecover. However, this also reduces the frequency of backup points in case of a crash.
Word Save Methods: Manual Save vs AutoRecover vs Quick Save
| Item | Manual Save (Ctrl+S) | AutoRecover Save | Quick Save (Disabled by Default) |
|---|---|---|---|
| Trigger | User presses Ctrl+S or clicks Save | Timer interval set in Options | User enables in Options and saves |
| File location | Same folder as original document | %AppData%\Microsoft\Word | Same folder as original document |
| Creates .tmp file | Yes, new each time | Yes, new each time | Yes, but only appends changes |
| Atomic write | Yes | Yes | No — updates original in place |
| Data loss risk if interrupted | Low — original preserved until rename | Low — .tmp recovered on restart | High — partial write corrupts file |
Quick Save is a legacy feature that was removed in Word 2013 and later. It updated the file in place without creating a temporary file, which increased corruption risk. Modern Word versions always use the atomic write method described above, even for AutoRecover saves.
Now you understand why Word recreates a .tmp file on every save: the atomic write-to-temp-then-rename strategy ensures your document is never left in a partially saved state. You can verify this behavior using File Explorer as shown above. If you ever encounter a leftover .tmp file, rename it to .docx to recover your work. For advanced users, consider adjusting the AutoRecover interval to balance backup frequency with temporary file creation.