VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

How to Restore an Earlier Version of a File in Google Drive

Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.

To restore an earlier version of a Google Doc, Sheet or Slide, open the file on a computer and choose File, Version history, then See version history. Select the revision you want to inspect. You can restore it to the shared file or, where the option is available, make a separate copy. Check which action fits your situation before changing a document other people are using.

For a PDF, image or Word file uploaded to Drive, use Drive’s Manage versions workflow instead. An uploaded replacement has version history only when it was added to the same Drive item through the relevant version workflow. A second file with the same name may be a separate item. If the file itself was deleted, check Drive’s Trash rather than version history.

  • For a Google Doc, Sheet or Slide, use the editor’s Version history.
  • To recover one paragraph or a few cells, inspect the earlier revision and bring back the needed part.
  • Restore the whole file only when the shared document should return to that earlier state.
  • For uploaded PDFs or other non-Google files, use Manage versions on the exact Drive item.
  • Check the saved result and any later edits collaborators need to keep.

Identify whether you need an earlier revision or a deleted file

A file that opens with the wrong text still exists. Its version history may contain the earlier material. A file you cannot find may have been deleted, moved or opened under a different account. Start by identifying which problem you have. Search Drive by title or owner and check the folder if you are unsure. If you find the correct file, open it and inspect its current contents before restoring anything.

A missing paragraph is a version problem

Suppose a teammate replaces the introduction of a group report. The file opens normally and the new text is there, but you need one paragraph from yesterday. Open version history and inspect the previous revision. If the rest of the current report is correct, recover that paragraph rather than rolling the entire report back. Check the surrounding text after inserting it.

A missing file may belong somewhere else

If the report is absent from the usual folder, check your active account, Drive search, recent activity and the relevant shared location. A shortcut can disappear while the source file remains elsewhere. If the item was actually moved to Trash and you can restore it under your role, use the trash recovery route. Version history only helps when you can open or locate the actual file.

A same-name file may be a different item

Two PDFs with identical names can have different links and histories. A new upload in the same folder does not automatically give you the old file’s revisions. Check the item’s link, date and contents. If you need an earlier export, find the original Drive item or check whether the sender saved it separately.

Back to contents · Next section


Open version history in Google Docs, Sheets or Slides

On a computer, open the current file in the relevant editor. Google documents File, Version history, See version history. Choose a revision from the list and inspect its contents. The list can show dates and the people who made changes, and some revisions may be grouped. Expand a group where the interface offers it to see more detail.

Google says you need editing permission to browse earlier versions of a file. If you can only view or comment and need an earlier copy, ask the owner or an authorised editor to check. Explain what you are trying to recover, such as a particular heading or table from the previous week. The owner can choose a copy or a restore depending on the document’s needs.

Find the change by content and time

If you know when the problem appeared, start with the most recent version before it. Check the actual text or sheet cells. A time label can narrow the search, and the content confirms the revision. For a long report, look for the missing heading. For a presentation, check the relevant slide title and the speaker notes if the task uses them.

Check revisions near a known milestone

A group may have named the version submitted to a teacher or approved by a supervisor. Use that label to locate it, then compare it with the current file. A name helps identify the milestone and still needs a content check. If the history shows several changes close together, inspect the neighbouring revisions before selecting one to restore.

Expect some history to be grouped

A long editing session can produce several changes within a short period. Google notes that versions can sometimes be grouped or merged. If a precise intermediate state is unavailable, look for the nearest useful version and recover the relevant content. Check an approved exported copy if the exact state was previously submitted as a file.

Back to contents · Next section


Recover one paragraph, table or slide without rolling back the whole file

A full restore changes which content is current in the shared document. If you only need one part, make a copy of the earlier version where the option is available or retrieve the relevant content through the approved editor workflow. Keep the current version visible while you compare. This is useful when other collaborators added material after the revision you need.

Restore one section of a report

Imagine a report lost the method paragraph on Monday. On Tuesday, another student added a chart and corrected the references. The earlier Monday revision has the method and lacks Tuesday’s work. Make a separate copy of the earlier revision where allowed, open both files and copy the required paragraph into the current report. Check the heading and references around it. This preserves the chart and the corrections.

Restore a few cells in a spreadsheet

Check which sheet and range were affected. An earlier version may contain formulas and values that depend on other cells. Copy only the cells you intend to recover, and review formulas, references and totals in the current sheet. If you only need to see what a cell used to contain, Google Sheets has an edit-history option for supported cells. Google notes that some changes do not appear there, so use file history when you need a broader comparison.

Restore a slide with its context

An older slide may depend on an image, a chart or a speaker note. Check those elements in the earlier version. If you copy the slide into the current deck, verify its position and theme. A copied chart or link may need its own access or update check. Open the finished deck and review the slides before and after the repaired one.

Back to contents · Next section


Restore the whole Google file when the earlier state is the right one

Use the full restore when the shared document should return to the selected revision. Open version history, select the correct revision and use the restore option. Review any confirmation. Before proceeding, check whether the later changes should be preserved elsewhere and whether other collaborators need to finish their edits. A separate copy of the current version can be helpful when the workflow permits it.

Choose a clear stop point for collaboration

For a group report, decide who will restore and when. Check that everyone is working in the same file and understands which revision should become current. If the team needs both the current and earlier versions for comparison, make a separate copy instead. Give it a clear title and use the approved folder and sharing settings.

Inspect the result in the shared file

After restoring, reopen the document and check the relevant sections. Compare the date, title and content with the revision you intended to use. Make sure the version you are looking at is the original shared item rather than an older copy. If the restored file will be submitted, export and verify a fresh deliverable after the restore.

Name important revisions as you work

Where the editor allows it, a named version can mark milestones such as “Before section rewrite” or “Approved for submission.” Use labels that describe a meaningful point. For a team, agree who names the versions and where the accepted export is kept. A named milestone can make later recovery faster without creating many parallel working files.

Back to contents · Next section


Find earlier versions of uploaded PDFs and other files

Google Drive treats uploaded files differently from Google Docs, Sheets and Slides. On a computer, select the exact Drive item and look for Manage versions. Google’s guidance describes viewing, downloading and retaining older versions there. Use that menu for an uploaded PDF, image or other supported file when you want a previous upload of the same item.

Download the earlier upload before replacing anything

Open Manage versions and identify the revision by date or available details. Download the earlier copy using the approved controls. Give it a clear working name and open it to check the contents. If the only task is to read the old PDF, a downloaded copy is enough. If the shared item must point to the earlier file again, follow the owner’s process for adding that verified copy as the current version.

Check whether there was a version to begin with

Suppose a student uploaded Report.pdf on Monday and added the revised PDF through Manage versions on Wednesday. The earlier upload may still be available for download. If the student instead uploaded a second Report.pdf as a separate Drive item, the first file may exist in Drive independently. Search for both items and compare their dates or contents. The two workflows lead you to different places.

Retain a key uploaded version where needed

Google documents that older uploaded versions can be removed after 30 days or after 100 newer versions unless the version is marked to keep. Check the settings on a version you need to retain and follow the organisation’s retention rules. Keep approved exports in the intended storage location. Version history helps you recover changes and is not a substitute for any required recordkeeping.

Back to contents · Next section


Compare revisions when the wrong change is hard to locate

Start from the latest version that you know was correct. If the problem appeared after a review meeting, look at the file around that time. Open several nearby versions and compare the affected section. A date narrows the search, and the text or numbers tell you which copy you need. For large files, write down the slide title, sheet name or heading so you can find the same place quickly.

A report changed in three different ways

A group removed a paragraph on Monday, updated a figure on Tuesday and corrected citations on Wednesday. On Thursday, the teacher asks for the paragraph back and expects the new figure and citations to remain. Locate the last version containing the paragraph. Compare it with the current report. Restore the paragraph selectively and review the transition to the new figure and references. A full rollback to Monday would undo useful work.

If the older paragraph cited a figure number that changed during the later edits, update that reference in the current document. Recovering a paragraph does not automatically reconcile its surrounding context. Read the two paragraphs on either side and check any link or table it refers to. Export the finished report after the current file is coherent.

A formatting change hides a real content change

A style update can make the whole file look different. Identify which parts changed in substance by checking the sentences, values or slide notes that matter. If a heading has a different font and the paragraph below it is missing a sentence, recover the sentence and keep the intended style. Use the earlier version as a source, and let the current document’s layout determine how the recovered material is placed.

A collaborator edited a copy rather than the shared original

Check the file’s link before inspecting its history. The current shared file and a separately named copy may have different revisions. Ask the collaborator to identify the item they edited. If their copy contains a needed change, bring it back through the approved workflow. The shared file’s history cannot show changes that only occurred elsewhere.

Back to contents · Next section


Review formulas, charts and notes after selective recovery

A document revision can contain more than visible words. A spreadsheet can have formulas, formatting, validation rules and sheets that feed charts. A presentation can have speaker notes or linked material. Recover the feature the reader needs and check its connections in the current file. An older item might reference a page, cell or file that changed since the earlier revision.

Check the scope of a spreadsheet repair

Suppose cells D4 to D8 originally calculated totals from values in columns B and C. In the current sheet, those columns have been reorganised. Copying the old formulas directly may use the wrong inputs. Compare the current sheet’s layout first. Restore the required logic where appropriate and verify the results against known values. If you only need the old numerical results for a record, save the permitted reference copy rather than replacing working formulas.

Check the context of a copied slide

A recovered slide can inherit layout choices from its source or use the destination’s theme depending on the copy method. Look at the visible slide and any notes the presenter needs. Check linked charts or media if the audience depends on them. A deck can look complete in the editor and still fail to play or open an item under the intended account.

Keep the current work usable while you compare

If several people are editing, use a separate comparison copy where allowed. Make selective changes only after identifying the exact content to recover. Confirm with the responsible owner when the repair affects a shared deliverable. Then ask a teammate to inspect the result from the current shared item rather than from the comparison copy.

Back to contents · Next section


Fix a missing revision or an unavailable restore option

You can see the file but cannot open its history

Check your role and account. A person with reading access can see the current content and still lack permission to browse revisions. Ask an authorised editor to retrieve the relevant version. If the file is owned by a school or workplace, use that organisation’s process for access or recovery.

The revision does not contain the missing material

Check the date and any nearby grouped versions. Verify the account, file identity and folder. The paragraph might have been edited in a copy or an offline export that never became part of this item’s history. Look for the approved source or ask the colleague who made the edit. A similarly named file is a common source of confusion.

You only have a PDF export

A PDF exported from a Google Doc has its own Drive identity. Its versions can reflect uploaded replacements, while the editable document’s history records the working changes. If you need the editable text from an earlier day, find the Google Doc. If you need the exact PDF sent that day, check the accepted export or the PDF’s uploaded versions.

The earlier version was already removed

Use any permitted saved export or backup that contains the required information. If the document belongs to a managed account, contact the responsible owner or support team and describe the file and revision. The options depend on how it was stored and what retention rules apply. Keep the current file available while you investigate.

Back to contents · Next section


Protect the accepted version during a later correction

When a report has already been submitted, identify the accepted copy before you edit the working document. The live source may have changed since submission. Open the exact accepted export if available and compare it with the current source. Decide whether the correction should build on the submitted state or on newer approved work.

Keep the versions for different purposes separate

An earlier version can be useful as evidence of what was submitted. A new working version can contain the correction. Label them according to the issuer’s instructions and keep their storage locations distinct. If the portal requires the same filename, preserve the old and new copies in different folders and verify which one you select.

Follow the correction process

Re-export the repaired document and open it. Check the changed material and any affected page counts or links. Submit through the recipient’s approved correction route and keep the updated confirmation if allowed. A restore in Drive does not automatically replace a file that was already sent as an attachment or uploaded to a different system.

Back to contents · Next section


Practise choosing between copy and restore

Create a harmless test document with a heading and a short paragraph. Make one revision that changes the paragraph and a later revision that adds a table. Open version history and locate the revision with the old paragraph. Decide how you would recover it while keeping the table. A separate copy or selective recovery is the appropriate route when both pieces are needed.

Now imagine the whole document should return to its original test state. Use the restore option on the practice file and check what becomes current. Compare that result with the copy workflow. Then try the same thought exercise with two uploaded PDFs bearing the same name. Identify which version history belongs to which Drive item before changing either one.

Back to contents · Next section


Keep named milestones useful through a longer project

Choose milestones that explain why a revision matters. “Approved before data update” and “Submitted on 8 November” are easier to use than several versions labelled Final. Use the team’s naming and storage rules. If the same working file will be used for months, name major decisions rather than every small correction.

Separate revision labels from exported files

A named version in a Google editor marks a state inside that editor. A PDF handed to a portal is a separate file. Keep a permitted copy of that export and its confirmation where the organisation allows. If the team later restores the named version, verify the result against the accepted PDF before treating them as equivalent. Export settings, fonts or page breaks can affect the finished PDF even if the source text matches.

Review ownership during handovers

If the person who owns the working file changes, follow the organisation’s approved ownership or access process. Make sure the incoming editor can use the current file and any approved record of key versions. A new copy can have a different history from the original. If the team needs continuity, ask the responsible owner which item should remain the master.

Use a deliberate recovery workflow in a group

Set a time to compare the earlier revision, identify the necessary changes and decide whether to recover one part or restore the file. If a full restore is approved, let collaborators know which version will become current through their agreed process. After restoring, open the shared file and check the affected material and a recent unrelated edit. Verify that the result matches the team’s decision.

Back to contents · Next section


Plan for an earlier PDF that was never added as a version

A team might keep an editable Google Doc and export a PDF for each review. If the PDFs were uploaded as separate Drive items, each export can have its own link. Search by filename, date or folder, and open likely candidates. If an earlier PDF was sent by email or accepted by a portal, check that authorised copy. The editable document’s revision can help reconstruct it, but a reconstructed export should be identified as such when exact recordkeeping matters.

Compare two PDFs with the same title

Open both and check a feature that changed, such as a caption, page count or footer. The timestamp can help narrow the choices. The content distinguishes the revision. If one PDF was already approved and the other is a correction, keep them separately identified in the approved location. Select the appropriate copy for the task.

Keep future uploaded revisions on the intended item

When Drive’s Manage versions workflow is the correct route, choose the existing item and add the checked replacement as a new version under its allowed controls. Then open the item to verify what is current. If the recipient instead needs a fixed separately archived output, make that copy according to the requirements. The method should match how people will use the link and version history.

Back to contents · Next section


Choose which evidence to keep when versions disagree

A named version, the current Google file and an exported attachment can each show a different state. Start with the reader’s question. If they need to know what was sent, inspect the actual accepted attachment or official submission copy. If they need to recover text for new work, open the earlier source revision. If the current file is the working master, check any changes you copy into it against its latest content.

Build a small timeline for a complicated correction

Suppose a group approved a report at noon, exported it in the afternoon and corrected a footnote the next day. The approved version name and the attachment timestamp may differ. Open the accepted PDF and confirm whether it contains the footnote. Then inspect the earlier source revision if you need to reconstruct the working state. If a replacement is requested, decide with the owner whether to preserve the footnote change and use the official correction process.

Know when a copy is the right deliverable

A supervisor may ask for the previous text to compare with a revision. A separate copy gives them a reference while the team continues using the current file. Name it by its purpose and check its sharing settings. If the request is to restore the live file, inspect changes that happened after the target revision and preserve any the team needs before restoring. These are different tasks even when they start from the same version list.

Use a stable way to describe the revision

In a handoff, identify the file title, revision label or date, and the section that matters. A message saying “the previous version” can be ambiguous after several revisions. A description such as “the draft before the data update, with the method paragraph still present” gives the owner something to verify without making an unnecessary copy of the whole file.

Back to contents · Frequently asked questions


Frequently asked questions

Where is Google Docs version history?

On a computer, open the document and choose File, Version history, See version history. You generally need editing permission to browse it.

Can I make a copy of an older revision?

Google documents a copy option for supported earlier versions. Use it when you want the old material without changing the current shared document.

Can I restore one paragraph without changing the rest?

Inspect or copy the earlier version and bring back the needed paragraph. Compare the surrounding content and preserve later work.

Does the same process work for an uploaded PDF?

Use Drive’s Manage versions on the uploaded file. Google Docs editor history and uploaded-file versions are separate workflows.

Why are there two files with the same name?

They can be separate Drive items. Check the link, file details and contents before using history or replacing either one.

Does restoring a version change a submitted PDF?

Restoring the source changes the shared file’s current content. A PDF already sent or uploaded elsewhere remains its own copy unless you replace it through the required route.

What if the whole file is gone?

Check Drive Trash, search under the correct account and consult the owner or support team where needed. Deleted-file recovery is a separate task.

Where is the older PDF if Manage versions is empty?

Search for a separate upload, approved export or sent attachment. An independently uploaded file can have its own link and no history under the item you opened.

Should I restore the shared file to compare two versions?

A separate copy or the editor’s history view can support a comparison without changing the current file. Restore it only when the earlier state should become the current shared version.

Does copying an older version preserve the original file’s link?

A separate copy has its own identity and link. Verify its permissions and keep the original link when the group should continue working on the existing item.

Can a version name tell me exactly what was submitted?

It can help locate the intended state. Check the actual submitted export or confirmation when you need evidence of what the recipient received.

Why can’t I see every edit as a separate revision?

Google can group revisions. Inspect nearby entries and use any approved export or record when you need a precise state.

When should I check an older upload’s retention settings?

If the earlier uploaded version is needed as a record or reference, check its settings before relying on it. Use the applicable retention process for a managed account.

Can I compare an older version on my phone?

For the editor and uploaded-file workflows described here, use a computer as documented by Google. Check the active account and open the original file before looking for its history.


Helpful reading

Recover the change you need and verify the current file

Use a separate copy for comparison or selective recovery. Restore the shared document when the whole team needs the earlier state, then reopen it and check the intended content.