Word creates several kinds of temporary files whenever a document is opened, edited, saved, or when AutoRecover runs. These files are expected and are part of Word’s data‑integrity and performance design, especially when working across a network share such as an SMB share on a NAS.
Key points relevant to the Synology NAS scenario:
- When a previously saved file is opened from a share, Word creates an owner file in the same directory as the source file. This file name starts with
~$ followed by the rest of the original file name and contains the logon name of the user who opened the document. It is used to detect when a document is already open by another user.
- When Word saves a document, it first writes the content to a temporary file and only then deletes the previous version and renames the temporary file to the original name. This protects the document from corruption if a problem occurs during the save.
- When copying and pasting between documents, Word may create additional temporary files in the same directory as the source file, especially if the source file is saved or closed while the Clipboard still references its content.
- Word normally deletes these temporary files when the document is closed and Word shuts down normally. If there is any interruption in the save/close process (for example, a network glitch, permission issue, or other environmental problem on the NAS), the temporary files can be left behind and accumulate.
- On macOS as well as Windows, if something environmental breaks the save or AutoRecover process, Word can report disk‑related errors and leave behind
~Word Work File S{…}.tmp or similar files. Updating Office for Mac to the latest build is recommended to reduce such issues.
Practical mitigation steps based on this behavior:
- Ensure Office for Mac is fully updated so that the save/AutoRecover logic and network handling include the latest fixes.
- Verify that the SMB share on the Synology NAS allows Word to create, rename, and delete files in the document folders without interruption; intermittent network or permission issues will cause temporary files to remain.
- Periodically clean up leftover temporary files on the NAS (files starting with
~$ or with temporary names) when no one has the corresponding documents open.
- Prefer working with AutoRecover and other temporary locations on a local path where possible, as Word performs best when its temporary/scratch files are on local storage.
References: