Word .docx corrupted after OneDrive sync conflict? Here's the fix

You've got a Word file — let's call it Q4_Report.docx. You opened it, made changes, saved. Then OneDrive throws a sync conflict. Now you've got a file with Q4_Report (1).docx or Q4_Report-Sync-conflict-2025-02-16.docx. And when you double-click it? Word says it's corrupted. Unreadable. The file exists, it's got the right extension, but it won't open. This usually happens after you and a colleague both edited the file offline, or when OneDrive paused syncing mid-save and then reconnected.

Root cause

The culprit here is almost always a partial write. When OneDrive merges two versions, it sometimes creates a new file that's incomplete. Word expects a full .docx structure (which is actually a ZIP archive). If the file gets truncated during the sync merge — even by a few bytes — Word can't unzip it. And it throws a generic "corrupted" error. It's not really corrupted in the data-loss sense. It's just missing its header or footer structure. This happens more than you'd think with Office 365 on Windows 10/11 when OneDrive's sync engine hits a timing glitch during conflict resolution.

Don't bother reinstalling Office or running a full repair. That's not the issue. The file itself is fixable 9 times out of 10.

The fix — step by step

1. Close Word completely. Make sure it's not running in the background. Check Task Manager — kill any WINWORD.EXE processes.
2. Locate the corrupted file. Right-click it, choose Properties. Check the Previous Versions tab. If you see an earlier version, restore it. That's the fastest fix. If not, move to step 3.
3. Rename the file extension. Change .docx to .zip. Yes, really. Right-click the file, rename it to Q4_Report.zip. Windows will warn you — click Yes.
4. Try to open the ZIP file. If it opens normally, the data is intact. Look for a folder called word inside. If that folder is missing or empty, the file is genuinely corrupted — skip to “Still failing?” below.
5. If the ZIP doesn't open at all, you've got a truncation issue. Download a tool like 7-Zip (it's free and handles partial archives better than Windows Explorer). Right-click the .zip file, choose 7-Zip > Open archive. If it shows a warning but lists files inside, extract the word/document.xml file.
6. If 7-Zip can't extract it, use DiskInternals Word Recovery or Recuva — both have free versions that scan for raw .docx structures. They'll pull out the readable content even if the file structure is shot.
7. If you can extract document.xml, open it in Notepad or any text editor. You'll see XML — lots of angle brackets. Look for your text buried in <w:t> tags. Copy the text between those tags. Past it into a new Word document, save as .docx. Done.
8. Still no luck? Try opening the corrupted file in Word Online (browser version). It sometimes handles sync-conflict files that desktop Word won't. Go to onedrive.live.com, find the file, click it. If it opens, save a copy to your local drive.
9. If Word Online also fails, check OneDrive's version history. Right-click the file in OneDrive's file explorer, choose Version history. You'll see every saved version. Pick one from before the conflict. Download it. That's your most reliable recovery path.

Still failing?

If none of that works, the file is truly hosed. OneDrive's sync engine sometimes writes a zero-byte or near-zero-byte placeholder when a conflict happens and the original upload failed. Check the file size — if it's under 1KB, it's a ghost file. Delete it and restore from backup. You are backing up, right?

For future prevention: turn off OneDrive sync in Word when you're working on shared files. Go to File > Options > Save and uncheck AutoSave OneDrive and SharePoint Online files by default in Word. This forces you to manually save, which gives you more control over sync timing. Also, tell your team to avoid opening the same file simultaneously — OneDrive's conflict resolution is still clunky in 2025.

One last thing: if you're on Windows 11 with the new OneDrive sync client (the one that ships with the OS), these conflicts happen more often. Downgrading to the classic OneDrive client isn't possible anymore. Your only real defense is to use version history proactively — check it before you start editing a shared file, and save a local copy as a .docx backup every hour.