Copy an earlier Google Docs version without restoring

To copy an earlier Google Docs version, select the historical state in version history and create a separate copy. This guide helps you produce a clearly named reference document and a check record while keeping the current working document separate.

Updated: 19 October 2026.

What should you finish with?

Suppose a small agency is revising a project brief. The team needs the current brief for ongoing work, but a producer wants an older paragraph available for reference. Rolling the shared document back would answer the wrong question. The desired deliverable is a separate historical reference, not a replacement for the working brief.

The scenario here is a synthetic exercise, not a report of work performed for a client or a firsthand implementation by Anar. We have not run an account-level interface, save, reopen or timing test for this article. Instructions describe a reader workflow; expected results must not be mistaken for results we observed.

Aim to finish with two identifiable documents and one short record. The record should tell another person which link is current, which link is historical and what text you actually found in each. A filename saying “old version” is not enough. Someone picking the files up tomorrow should not need to guess which one remains the working source.

Prepare an unmistakable practice example

Use a harmless practice document on a computer. You need permission to edit the document to browse its earlier versions. Avoid a live client proposal for your first attempt. A practice exercise does not need personal data, confidential prices or an important deadline. If you lack the required access, record that dependency rather than experimenting with other people’s files.

Without a harmless file containing suitable history, open docs.google.com with an existing permitted account, create a blank document and name it “History practice.” Type “The brief covers one product page” and wait for online saving. Open Last edit, then use that state’s More > Name this version to name it “Earlier text.” Select Back, replace the sentence with “The brief covers three product pages” and wait for saving. Check that history contains the named earlier state and the changed current state. If either is absent, stop and record it. These are fictional control sentences, not project terms; do not select Restore.

Write down the current document link before opening history. Also note the old wording you are trying to locate. Do not rely on a tab title, because similar titles can make two different files look alike. If your practice file does not contain the intended earlier state, pause: the example does not establish that every historical state will be available.

Create the separate historical document

Google’s official history instructions describe this route: open the document on a computer, open version history through the last-edit indicator, and find the desired historical state. Beside that version, use More, then Make a copy. Enter a name, select a destination and click OK. This is the history-specific copy action, not the restore action.

Use a name that describes the job, such as “Brief practice | historical reference | not working copy.” That is a suggested naming convention, not a Google requirement. Do not label the file “approved” unless approval has been established through a separate process. A recovered paragraph does not prove that anyone accepted its terms.

Sharing the copy with the same people is a separate option. Leave it unselected when it is unnecessary for the practice exercise. Before sending any link later, inspect the copy’s actual access settings. Creating a reference does not require distributing it. Do not switch to restore or delete-history commands when the copy command is hard to find.

Check the copy and the current file independently

Open the new copy and look for the older control sentence. In the synthetic example, that means the sentence about one product page. Then return through the original link you recorded and check for the current sentence about three product pages. These are expected checks, not evidence that your own run succeeded.

Record both links as separate entries. Opening the same document in two tabs is not evidence of a separate copy. Read the surrounding heading and one nearby control sentence as well: finding a single familiar phrase does not establish that you selected the intended historical state. If anything is inconsistent, retain the uncertainty instead of filling the record from memory.

Google documents automatic saving while working online. Your completion check should still include reopening both documents from their recorded links. Verify the historical wording in the reference and the current wording in the working file. We did not perform this reopen test. The reader should enter an observation only after actually viewing the files again.

Be careful with a working document that other people are editing. A later difference may reflect their ongoing changes, not the copying action. Note what you saw and when you saw it without inventing a cause. If you cannot establish which state is current, mark the comparison unresolved and ask the document’s responsible editor before treating the reference as ready.

Use this copy-and-check worksheet

Open a new Notepad document from Windows Start, or TextEdit > File > New on Mac, using Format > Make Plain Text if needed. Copy the fields below and record both document links and your observations. When finished, save history-copy-check.txt in Documents using Windows File > Save As or Mac File > Save; add a date if the name exists. Close and reopen that note to check both links and unperformed-check statuses. It is an operational record, not a certified audit trail or immutable archive.

Working document name and link: ___. Intended historical state label or time: ___. Older control sentence to locate: ___. Reference copy name and link: ___. Text actually seen in the reference: ___. Text actually seen in the working file: ___. Reopen result for each link: ___. Check time and checker: ___. Unresolved issue and next action: ___.

For example, an unfinished reopen field should say “NOT RUN; next action is to open both recorded links.” Do not paste the expected old sentence into the observed-text field without checking it. When handing the note to a colleague, include the current link as well as the historical one. Otherwise a useful reference can accidentally become the file someone edits next.

You can also add a short handling instruction: “Reference only; propose changes in the working document after review.” This is a team convention you choose, not a technical restriction placed on the file by its title. If reference-only access is important, review actual permissions separately rather than assuming the words in the filename enforce it.

When should you stop instead of guessing?

Stop if the historical state you need is missing. Google notes that revisions can sometimes be merged. Selecting a nearby date and calling it the requested version would create a misleading reference. Write “intended state not found” in the worksheet. This workflow does not promise recovery of text that is absent from the available history.

Stop if the copy contains unexpected text, if the two recorded links lead to the same file, or if you cannot identify the current working document. Do not fix the uncertainty by restoring a version. That changes the task. Keep the incomplete record and resolve the specific issue with the person responsible for the document.

For a first short work session, keep the goal small: one practice file, one historical state, one separate reference and an honest record. The checklist gives you something concrete to do immediately, but it is not a measured completion-time promise. Access problems or unavailable history may prevent completion; a precise next-action note is still more useful than an unsupported success claim.

Finally, distinguish this job from nearby document work. Producing new wording with an AI assistant, comparing two supplied Word files and matching a document to an approval reference are different tasks. Complete the historical-copy check first. Decide separately whether any old wording should be brought back into the current brief, and who has authority to make that decision.

Related workflows

• Our artificial intelligence guide explains the broader context; AI is not required here
• Drafting and refining text with Gemini in Docs
• Checking an exact document approval reference
• Comparing two existing Word versions
• A separate workflow for receiving documents through Forms