Word can expose earlier revisions when a document was saved in OneDrive or SharePoint, when AutoRecover captured an interrupted session, or when the computer already had a backup system running. These sources solve different problems. Version history helps after a saved change; AutoRecover helps after a crash; File History or Time Machine helps when the file was local.

Before restoring: duplicate the current document and save any promising historical version under a new name. An older copy can recover a missing section while the current copy still contains later work.

Define the revision you need

Do not begin with “the old one.” Establish a narrow target:

  1. Record the document's current path and storage account.
  2. Estimate when the wanted text last existed.
  3. Name one distinctive item to verify, such as a clause, table total, comment, or citation.
  4. Note who edited the file around that time.

This evidence distinguishes a useful revision from a familiar-looking draft. It also helps when several versions were created within minutes.

Preserve the current document

Close Word if you can do so without another save. Copy the live file into a new, nonsynced holding folder and name it current-before-version-recovery.docx. If the document is shared, tell collaborators not to edit briefly while you inspect history.

Do not rename or move the live cloud file merely to make the search tidier. That can create additional sync activity and make paths harder to explain.

Retrieve a cloud revision

For OneDrive or SharePoint documents, open the correct file and choose File > Info > Version History. In some Microsoft 365 builds, selecting the filename in the title bar also reveals version history.

  1. Open the revision immediately before the unwanted change.
  2. Check the distinctive content you recorded.
  3. Save or download that revision into the holding folder.
  4. Include the source and revision time in its filename.
  5. Inspect one adjacent revision if the edit window is uncertain.

The Restore command promotes an older revision to the current version. It does not need to be your first action. Saving a separate copy gives you a chance to compare before changing what everyone else sees.

Word version recovery diagram showing historical versions, a copied document, and restore.
Word version recovery diagram showing historical versions, a copied document, and restore.

Recover from Word after a crash

If Word closed unexpectedly and the revision was never successfully saved, reopen Word and inspect the Document Recovery pane. On Windows, also check File > Info > Manage Document > Recover Unsaved Documents. The AutoRecover path configured under File > Options > Save can reveal additional candidates.

Open the candidate and immediately use Save As to place a normal .docx copy in the holding folder. AutoRecover files are temporary working material, not a durable archive. Their timestamps may reflect the recovery snapshot rather than the exact moment each paragraph was typed.

Use a device backup for local files

Cloud version history cannot help a file that never entered that cloud account. For a local Windows document, inspect Properties > Previous Versions on the file or parent folder if File History was enabled beforehand. On macOS, enter Time Machine while viewing the original folder.

Browse to the target date and recover into a separate location when possible. Never restore an entire project folder over newer work just to retrieve one document.

Compare the historical and current copies

Desktop Word provides Review > Compare > Compare. Choose copies of the older and current documents; Word produces a third comparison document rather than altering the originals. Review:

  • inserted and deleted text;
  • comments and tracked-change authors;
  • headers, footnotes, fields, and citations;
  • tables, images, section breaks, and page layout.

If the historical file contains only the missing passage, copy that passage into a new merged document. If it is clearly the complete intended revision and the current file adds nothing valuable, a full restore may be reasonable after review.

Match the symptom to the source

What happenedMost relevant sourceWhat to keep
A saved edit removed good contentOneDrive or SharePoint version historyDownloaded historical revision
Word crashed before the last saveDocument Recovery or AutoRecoverNewly saved DOCX copy
Local file changed days agoFile History or Time MachineRestored copy outside the live folder
Two authors produced competing draftsWord CompareBoth sources and a merged third file
File is missing rather than changedRecycle Bin or cloud recycle binOriginal path and deletion record

Avoid misleading version clues

A timestamp can change after download, migration, or synchronization. A larger file may merely contain embedded media. A revision listed under another editor may still hold your text. Open each candidate and verify the exact content rather than ranking files on metadata alone.

Office files sent through email or chat may be detached copies with no shared version history. Search the original storage location before assuming the attachment is authoritative.

Escalate high-value documents early

For contracts, court filings, financial approvals, or regulated records, do not perform a blind restore. Preserve the current file, historical candidates, screenshots of the version list, account name, path, and approximate event time. An administrator may have retention or audit tools unavailable to an ordinary user.

Complete the recovery

Open the selected result after restarting Word and verify the target passage plus comments, fields, links, and pagination. Give the recovered file a new name until its owner approves it. Keep the source copies and a short recovery note until the document has been backed up successfully.

Sources and further reading