Version history can recover a deleted paragraph, an overwritten section, or a draft from before a collaborator's broad edit. The safest default is not a full restore. Preserve today's document, make a copy of the older version, and transfer only the material you need.
Fast route: Name the current version, open File > Version history > See version history, select the older state, and use its More > Make a copy command. Restore the whole version only when the complete older document should become current.
1. Confirm the correct document and permission
- Verify the Google account in the browser.
- Open the document from Drive and check its URL.
- Confirm the owner and containing folder.
- Make sure you have edit permission.
- Write down the missing heading, phrase, or section.
Google requires edit permission to browse version history. A viewer or commenter should ask the owner or an editor to inspect it. A same-name copy has a different file ID and an independent history, so title alone is not proof.
2. Preserve the current document
- Select File > Version history > Name current version.
- Use a descriptive name such as “Before contract clause recovery - 2026-08-21.”
- Select File > Make a copy for an additional independent fallback.
- Keep the original current version open in one tab.
Naming creates a visible checkpoint inside the same file. Making a copy gives you another document that remains available if collaborators continue editing the original during recovery.

3. Find the moment before the unwanted change
- Open File > Version history > See version history.
- Select timestamps in the right panel.
- Expand grouped versions for finer detail.
- Use edit colors and collaborator names to identify the change.
- Compare the exact paragraph, heading, table, comment context, or formatting.
The most recent older timestamp is not automatically the best. Choose the version where the required content and surrounding structure are both intact.
Google may merge some revisions. Named milestones are easier to locate, but they must have been created before the problem.
4. Make a historical copy for selective recovery
Google officially supports copying an earlier version:
- Select the historical version.
- Open the More menu beside that version.
- Choose Make a copy.
- Give the copy a name that includes its timestamp.
- Choose a Drive folder and whether to share it with the same people.
Open the historical copy beside the current document. Transfer only the missing paragraphs, table, or section. Reapply comments or suggestion context deliberately rather than assuming every collaborative detail transfers exactly through ordinary copy and paste.
5. Restore when the whole earlier draft is superior
A complete restore is appropriate after a mass deletion, wrong-template replacement, or destructive restructuring that affected most of the document.
- Verify the named current checkpoint and fallback copy.
- Select the correct historical timestamp.
- Review the beginning, middle, and end of the document.
- Choose Restore this version and confirm.
- Reopen version history and confirm the pre-restore state is still identifiable.
Tell collaborators what was restored and why. Otherwise someone may reapply the change that triggered recovery.
6. Check the details that text comparison misses
After selective recovery or restoration, inspect:
- heading hierarchy and document outline;
- tables, footnotes, links, and images;
- comments and resolved discussions;
- suggestion-mode edits;
- headers, footers, and page setup;
- sharing roles and publishing settings.
Search for a unique phrase from the recovered section. Then close and reopen the document URL to confirm the change remains saved.
Understand common history gaps
| What you see | Likely reason | Next action |
|---|---|---|
| Version history command is absent | No edit permission | Ask owner or editor |
| History begins after an import | New file ID was created | Find the original Drive file |
| Older entries look grouped | Revisions were grouped | Expand the timestamp |
| Offline edits are missing | They may not have synced | Preserve original device and profile |
| History was intentionally deleted | Deletion is permanent | Use copies, exports, or backups |
| Whole document is absent | File-level loss | Search Drive and Trash |
The owner can manage historical content, and Google warns that deleting version history cannot be undone. Workspace retention policy may also affect organizational records.
Choose a proportionate recovery method
| Scope of loss | Preferred action |
|---|---|
| One paragraph or table | Make historical copy and transfer it |
| Several related sections | Merge from a historical copy |
| Nearly all current content is wrong | Preserve current state, then restore |
| The document file was deleted | Restore through Drive, not editor history |
| Unsynced offline text is missing | Reconnect the original browser profile |
Create useful milestones
Name versions before review rounds, legal approval, major imports, or structural rewrites. Labels such as “Client approved copy” or “Before policy merge” are more useful than “Final 3.” For high-value documents, keep dated exports outside the live file as an additional recovery layer.