Word Found Unreadable Content: What It Means and How to Recover Your Document

Quick answer

The “Word found unreadable content” prompt means the .docx file’s internal structure won’t parse cleanly — usually a bad save, a sync conflict, or a corrupted download. Click Yes to let Word try to recover it. If that fails, copy the broken file somewhere safe and use File → Open → Open and Repair. Most fixable files come back at one of those two steps. Don’t disable Protected View as a “fix” — it doesn’t repair anything.

Before you start

Make a copy of the broken file before you do anything else. Every fix below either modifies the file or changes how Word reads it. If a step makes things worse, you want the original intact for the next attempt. This single habit separates recovered documents from permanently lost ones.

Don’t keep clicking Yes on the recovery prompt expecting a different result. If the prompt opened a garbled document the first time, it’ll open the same garbled document the second time. Close it without saving and try a different method.

Don’t reinstall Office as your first move. Several older guides recommend it. Reinstalling Word doesn’t repair an already-broken document — it just delays you by half an hour. Save it for last, if at all.

If this is a work or school document, see the work-device section before changing settings.

What this means

The prompt usually appears as: “Word found unreadable content in [filename]. Do you want to recover the contents of this document? If you trust the source of this document, click Yes.”

A modern Word file (.docx) is technically a ZIP archive containing XML files that describe the document’s content, styles, headers, footers, footnotes, and tracked changes. When Word says it found unreadable content, it means at least one of those internal XML pieces won’t parse — broken markup, missing references, malformed content controls, or a damaged ZIP wrapper.

That distinction matters. If the body of the document is intact and the broken part is something peripheral (a tracked change, a content control, an embedded object), recovery is usually straightforward and you keep most formatting. If the body itself is damaged, you’ll get partial recovery at best, and “Recover Text from Any File” — which we’ll cover below — will return text only.

Older Word versions phrased the same problem as “Word was unable to read this document. It may be corrupt”. Different message, same underlying issue.

Where this error appears

  • Word desktop on Windows 10, Windows 11 (including 24H2 and 25H2), and macOS.
  • Word for the web when opening a damaged document from OneDrive or SharePoint.
  • Documents attached to Outlook emails — Protected View blocks them on first open and the file may have been truncated mid-download.
  • Documents downloaded from a learning management system (Canvas, Blackboard, Moodle) where compression and re-encoding can damage the file.
  • Templates with content controls — drop-downs, date pickers, and form fields. These are notably fragile and account for a disproportionate share of “Word found unreadable content” reports in shared-template environments.
  • Documents transferred between Word for Mac and Word for Windows — usually fine, but edge cases exist.

Common causes

Most “unreadable content” isn’t deep corruption. The likely culprits, ordered by frequency:

  • An interrupted save. Word was force-closed, the laptop slept mid-save, OneDrive sync interrupted the write, or the network drive disconnected.
  • A sync conflict. OneDrive, SharePoint, or Teams produced two competing versions and the merge failed. Look for files like Document 1.docx or Document-Conflict-PC1.docx in the same folder.
  • Damaged content controls — drop-downs and form fields in templates. This shows up as a recurring problem in organizations that share templates widely.
  • A truncated download. The file was cut off mid-transfer from email, a learning portal, or a shared link.
  • Track Changes or Comments going stale. Documents with thousands of tracked changes can hit edge-case parser bugs after passing through several versions of Word.
  • An add-in writing bad data on the last save. EndNote, Mendeley, Zotero, Grammarly, and various PDF tools are common culprits.
  • A genuinely corrupt sector on the drive, especially on SD cards and aging external drives.
  • Conversion from a different format (.doc, .rtf, Pages, ODT) that didn’t translate cleanly.

A note on viruses: a single broken Word document is not malware evidence. If multiple unrelated files are unreadable on the same machine, you have a different problem to investigate — but one broken .docx isn’t it.

Fixes to try first

Work through these in order. Each is reversible and free. Stop the moment you have a usable document.

1. Click Yes on the recovery prompt — once

When Word shows the prompt, click Yes. Word attempts to repair the document and open whatever it can salvage. If the result is readable, immediately do File → Save As under a new filename. Don’t save over the original.

If the result is garbled or empty, close the file without saving. Each click of Yes doesn’t help — the recovery process is deterministic. Move to method 2.

2. Use Open and Repair

This is the highest-yield fix and most users miss it because Word doesn’t surface it on a double-click.

  1. Open Word with no document on screen.
  2. Go to File → Open → Browse.
  3. Click the broken file once to highlight it. Don’t double-click.
  4. Click the small dropdown arrow next to the Open button.
  5. Choose Open and Repair.

Open and Repair runs a more thorough recovery than the inline prompt. It rebuilds the file’s internal structure and pulls out everything it can. If you get a usable document, save it under a new name immediately and stop.

3. Check OneDrive, SharePoint, or Teams version history

If the document lives in cloud storage, the cloud version may have a clean copy from before the corruption.

  • OneDrive: right-click the file in File Explorer → Version history. Open earlier versions and save the most recent good one as a new file.
  • OneDrive web: onedrive.com → find the file → three-dot menu → Version history.
  • SharePoint / Teams: the same flow works in document libraries.

This bypasses the broken file entirely. If you find a recent good version, you’re done. This is often the highest-yield work-device fix.

4. Try opening in a different app

If Word can’t open it, something else might. This is a useful diagnostic as much as a fix.

  • Word for the web at office.com — sometimes succeeds when desktop Word fails because it uses a different parser.
  • Google Docs at docs.google.com — upload the file directly. Formatting won’t fully survive, but text, basic structure, and most images do.
  • LibreOffice Writer — free, available for Windows, Mac, and Linux. Open the file directly.

If any of them open the document, copy the contents into a new Word file and you’re back in business.

5. Open Word in Safe Mode

If Word itself is the problem rather than the file, an add-in is the usual cause.

  1. Press Windows + R.
  2. Type winword /a and press Enter. (/a opens Word with all add-ins and templates disabled — a stricter recovery mode than the standard /safe.)
  3. Try opening your file from File → Open.

If the file opens cleanly, you have an add-in conflict. Go to File → Options → Add-ins, switch the Manage dropdown to COM Add-ins, click Go, and disable add-ins one at a time. Reference managers, citation tools, and PDF integrations are the usual suspects.

Advanced fixes

If the methods above didn’t work, the file is more seriously broken. These approaches recover less but pull more from genuinely damaged documents.

Recover Text from Any File

Word ships with a recovery converter that strips everything except raw text. It’s an option of last resort — but for a 30-page manuscript where you just need the words back, it’s often enough.

  1. Open Word with no document.
  2. File → Open → Browse.
  3. In the file type dropdown next to the filename field (it usually says “All Word Documents”), choose Recover Text from Any File.
  4. Open the broken file.

What you get back: text. What you lose: formatting, images, tables, headers, footers, footnotes, drawing objects, comments, and tracked changes. Field text, headers, footers, and footnotes are returned as plain text mixed inline. Expect some garbage characters around the start and end of the document.

If the text comes through, copy it into a fresh document, clean up the artifacts, and rebuild formatting from scratch. For a thesis, manuscript, or report where the words are what matter, this is a real win even though it looks like a defeat at first.

Rename .docx to .zip and extract

Because .docx is technically a ZIP file, you can sometimes pull content directly out of it bypassing Word entirely. This works when Word’s recovery refuses but the file’s text is intact in the underlying XML.

  1. Make a copy of the broken file. Rename it from document.docx to document.zip.
  2. Right-click → Extract All.
  3. Inside the extracted folder, look at word/document.xml. Open it in Notepad or any text editor.
  4. Your document text is in there, surrounded by XML tags. It’s ugly, but it’s readable.

This is the technique to use when nothing else has worked and Recover Text from Any File returned garbage. Copy the visible text out of the XML, paste it into a new Word document, and accept that you’re rebuilding formatting from scratch.

Save as .rtf, then back to .docx

For documents with broken content controls — drop-downs, form fields, date pickers — converting through Rich Text Format strips out the controls and often produces a clean file.

If you can open the document at all (even partially):

  1. File → Save As → Rich Text Format (.rtf).
  2. Close the document.
  3. Open the .rtf file you just saved.
  4. File → Save As → Word Document (.docx).

This kills the content controls — the drop-downs in templates, the date pickers, the structured form fields — but for many users that’s a feature, not a bug.

About third-party repair tools

Searches for this error are dominated by paid recovery tools — Stellar Repair for Word, EaseUS Fixo, Wondershare Repairit, 4DDiG, SysInfo Tools, and others. They exist because there’s a real category of damage where Word’s own recovery and the .docx-as-ZIP technique don’t work — files with damaged compression headers, broken ZIP central directories, or structural damage to the document part.

Honest points:

  • They are not magic. Success rates on genuinely corrupted files are often 30–60%, not the marketing-page numbers.
  • Most preview your file for free and only charge to save the recovered output. Use the preview to decide whether it’s worth paying.
  • Don’t upload sensitive documents to “online repair” services without checking the vendor’s data policies and your employer’s rules.
  • “Free” versions usually cap recovery to a small page count or file size.

We don’t take affiliate money from any of these vendors. If you’re getting a strong sales pitch from a search result, that’s a tell.

If you are on a work or school device

A few things change when this is a managed device:

  • Don’t disable Protected View as a “fix.” It doesn’t repair the document — it just removes a security warning. On managed devices, the setting may be enforced by Group Policy and you can’t change it anyway.
  • Check OneDrive, SharePoint, or Teams version history first. Most work documents live in cloud storage. Highest-yield work-device fix by a wide margin.
  • If this is a shared template — and it often is, when “unreadable content” hits a whole organization at once — the template itself probably has damaged content controls. The .rtf round-trip method usually fixes the template; share the cleaned version with colleagues.
  • Talk to your IT team before installing third-party repair software. Most managed environments block it, and uploading a work document to a vendor’s online service may violate your data handling policy.

If you are the IT person at a small business and this keeps happening across multiple users on the same template, the template is the problem — not the documents. Fix the template once and the symptom disappears.

When to stop

There’s a point where continuing makes things worse. Stop when:

  • You have a usable copy of the document, even without formatting. Save it under a new name and rebuild what’s missing.
  • You’ve worked through the prompt, Open and Repair, version history, alternative apps, and Recover Text from Any File without success — and the document isn’t business-critical.
  • The drive is misbehaving (slow reads, other files affected, SMART warnings). Stop touching files on that drive and address the storage problem first.
  • Re-creating the document from notes, drafts, or memory would take less time than further recovery attempts.
  • The document contains sensitive information and the only options left involve uploading it to a third-party server you don’t trust.

A document with the text recovered and formatting rebuilt is a successful outcome. Closing the laptop and re-typing from a printed copy is sometimes also a successful outcome. The only outcome you should refuse is ending the day with the same broken file you started with and no progress.

  • Word document opens blank: recovery checklist — different symptom, related causes.
  • How to recover an unsaved Word document — for documents you closed without saving rather than ones that won’t open.
  • Excel file is corrupted and cannot be opened — same family of fixes, different application.

Official references

FAQ

Should I click Yes when Word asks if I want to recover the contents?

Yes — once. Word will attempt to repair the document and open whatever it can. If you get something readable, save it under a new name immediately. If it returns garbage or fails, close without saving and try Open and Repair instead. Clicking Yes a second time produces the same result.

Why does the document open as garbled symbols after I click Yes?

Word is showing you what it could pull from the damaged file using its strictest fallback, which sometimes ends up rendering raw XML or character codes. The file is more damaged than the inline recovery can handle. Close it without saving and try Open and Repair, then Recover Text from Any File.

Can I fix this by disabling Protected View?

No. Disabling Protected View doesn’t repair the document — it just removes a security check. If the file is actually unreadable, Protected View isn’t the cause. You’d be trading off security for a fix that won’t work.

Why does the same template keep producing unreadable documents at my workplace?

The template itself is damaged — usually because a content control (drop-down, date picker, or form field) was edited in a way that left it in a broken state, and now every document created from that template inherits the problem. The .rtf round-trip technique above usually cleans it. Fix the template centrally and tell your colleagues to use the new version.

Is Recover Text from Any File worth trying?

Yes, when the document is mostly text and you’ve exhausted other options. You’ll lose all formatting and most non-text content, but you’ll get the words back. For a long manuscript, that’s often the entire value of the file. Use the recovered text as the starting point for a fresh document.

My .docx file is from 2008 — will modern Word still open it?

Almost always, yes. Office 2007 was the first version to use .docx, and the format has been backward-compatible ever since. If a file from 2008 won’t open now, the cause is corruption picked up somewhere along the way — not version incompatibility.

↑ Back to top