OneDrive for Business Word AutoSave creates conflicts for offline edits: Fix Guide

When you edit a Word document offline while OneDrive AutoSave is enabled, the file can become conflicted once you reconnect to the internet. This happens because AutoSave continuously saves changes to the cloud version, but offline edits are stored locally and cannot sync until the connection resumes. When both versions diverge, OneDrive creates a separate copy or shows a merge conflict prompt. This article explains why these conflicts occur and provides a step-by-step fix to resolve them.

Why AutoSave Creates Conflicts During Offline Edits

AutoSave in Word for Microsoft 365 saves changes to OneDrive every few seconds by default. When you work offline, Word cannot send those saves to the server. Instead, the changes remain in a local cache. Meanwhile, if another user or process modifies the same file on OneDrive, the cloud version advances. After you reconnect, OneDrive detects two different versions and cannot determine which one to keep. It then creates a conflict copy with a name like Document (conflicted copy from user’s name).docx or prompts you to merge manually.

The root cause is the timing mismatch. AutoSave expects constant connectivity. Offline edits interrupt that flow, and Word does not pause AutoSave automatically when the network drops. The file remains in a pending sync state, and the conflict arises from the divergence between the local cache and the cloud version.

What Happens to the Original File

The original file on OneDrive retains the last cloud-saved state before you went offline. Your offline changes are stored in a separate local file. After reconnection, OneDrive may rename the original file to include a version number or create a second file with your edits. The Word document you see in File Explorer might show a red circle with a white minus sign, indicating a sync error.

Steps to Resolve AutoSave Conflicts for Offline Edits

Use the following steps to recover your offline changes and merge them back into the cloud version. Perform these steps after reconnecting to the internet.

1. Open the conflicted file in Word
   Double-click the file in File Explorer. If you see a prompt that says “Resolve conflict,” click the message to open the conflict resolution pane. If no prompt appears, go to the next step.
2. Review the conflict resolution pane
   In Word, click the Review tab and then click Compare. Select the conflicted copy from the list. Word shows a side-by-side comparison of the cloud version and your offline changes. Accept or reject each change using the buttons in the Compare pane.
3. Save the merged document
   After resolving all changes, click File > Save. Word overwrites the cloud version with the merged result. The conflicted copy is automatically deleted from OneDrive after the merge completes.
4. Use Version History if the conflict pane does not appear
   Open the original file from OneDrive in Word. Go to File > Info > Version History. Select a version dated before the conflict occurred. Click Restore to revert the cloud file to that state. Then open your local offline copy, copy the content, and paste it into the restored version. Save the file again.
5. Disable AutoSave before future offline work
   Open Word and go to File > Options > Save. Under the Save Documents section, uncheck the box for “AutoSave OneDrive and SharePoint files by default.” Click OK. You can also toggle AutoSave off using the switch in the top-left corner of the Word window before disconnecting from the internet.

If OneDrive Still Shows Conflicts After the Main Fix

OneDrive created multiple conflict copies

If you see more than one conflicted copy in the OneDrive folder, open each one in Word. Compare them with the original file using the Compare tool on the Review tab. Merge the changes from each copy into the original. After merging, delete the extra copies by right-clicking them in File Explorer and selecting Delete.

Word does not show the conflict resolution pane

The conflict pane only appears when OneDrive detects a version mismatch during sync. If Word does not show it, the conflict might have been resolved automatically by OneDrive. Check the OneDrive activity center by clicking the OneDrive cloud icon in the notification area. If no conflicts are listed, the file is synced. Open the file and verify that your offline changes are present. If they are missing, use Version History to restore an earlier version and manually add your edits.

AutoSave keeps turning back on

Some Microsoft 365 policies enforce AutoSave for enterprise users. If you disabled AutoSave but it re-enables, your IT administrator may have set a group policy. You cannot override this setting locally. In that case, work on a local copy of the file saved outside the OneDrive folder. After finishing edits, copy the file back into OneDrive and let it sync. This avoids AutoSave conflicts entirely.

AutoSave On vs Off for Offline Edits: Key Differences

Item	AutoSave On	AutoSave Off
Default state	Enabled for OneDrive files	Disabled for all files
Behavior offline	Creates pending saves that conflict on reconnection	No saves attempted; no conflict created
Manual save required	No, saves happen automatically	Yes, press Ctrl+S to save
Conflict resolution	OneDrive prompts merge or creates conflicted copy	No conflict; local file syncs normally
Best for	Always-online collaboration	Offline work or unstable connections

Now you can resolve AutoSave conflicts in Word for offline edits using the conflict resolution pane or Version History. Before going offline again, toggle AutoSave off from the Word title bar to prevent future conflicts. For repeated issues, save a local copy outside OneDrive and sync it manually after reconnecting. This approach gives you full control over when changes are uploaded to the cloud.