How to see Google Forms version history

Last updated September 2026 · ~9 minute read

You cannot — there is none. Google's help page on finding what changed in a file names the editors it covers, and Forms is not one of them: “You can see changes that have been made to a document in Google Docs, Sheets, Slides, or Vids.” There is no published Forms equivalent, no restore-this-version command, and nothing from Google that tells you which collaborator changed what. The only recovery control Google documents for the Forms editor is Undo, in the session you made the edit in.

That is the short version, and it is not in dispute. The useful part of this page is the rest: what Google actually does publish, what Drive can and cannot tell you about a form, and which substitutes hold up when somebody has already flattened a question you needed.

The absence, stated precisely

Docs, Sheets and Slides all carry a File → Version history menu that lets you scroll back through named revisions and restore one. Google's page for that feature opens by listing exactly which editors it applies to, and the list is four items long: Docs, Sheets, Slides, Vids. We re-checked it in September 2026. Forms is still not on it, and Forms appears nowhere else on the page.

There is a detail here that is easy to miss and worth knowing, because it explains why this feels like an oversight rather than a design decision. Google's own Forms API does track revisions of a form internally. Its write-control options are built on one: “The revision ID of the form that the write request is applied to. If this is not the latest revision of the form, the request is not processed and returns a 400 bad request error.” So a form has revision IDs. What the API reference does not publish is any method to list them, or to fetch a form as it stood at one. The version exists; the door to it does not.

What Google gives you instead

Undo, and only within the session

The Forms help page on editing a form documents one recovery control, in one sentence: “If you want to undo a recent change: At the top right of your form, click Undo.” That page says nothing about version history and nothing about saving. Undo is a live editing affair — close the tab and the thing you undid is no longer undoable.

Continuous saving, which is the reason the gap stings

The Docs Editors page on creating and viewing files — which lists Forms among the file types it covers — puts the saving model in two sentences: “When you're online, Google automatically saves your changes as you type. You don't need a save button.”

Put the two together and you have the whole problem. Every keystroke commits, immediately and permanently, to a live form; and the only thing standing between you and a bad edit is an Undo stack that evaporates when the tab closes. Docs has the same saving model but a full history behind it. Forms has the saving model on its own. (The responder side of saving — the 30-day draft response — is an entirely separate mechanism, covered in autosave and drafts.)

Who changed what on a shared form

This is the question that brings most people here, and it deserves a blunt answer rather than a hedge. Google publishes nothing about seeing which collaborator edited a form.

We looked for it. Google's page on sharing your form with collaborators covers granting editor access, setting expiry on that access, transferring ownership, and the fact that collaborators also reach the linked response spreadsheet. It does not contain a sentence about edit history, attribution, or tracking changes. Neither does the Forms editing page, which mentions no such thing anywhere.

On a form that three colleagues can edit, that silence is the answer. If a question's wording changed overnight, Google offers you no way to find out who changed it or what it said before. The practical consequence is that a shared form needs a convention instead of a feature: agree who restructures it, and take a copy before anyone does. Our guide to sharing a form with collaborators covers the access side.

Does Drive help? Partly, and less than you would hope

The activity panel

Drive has an activity panel, reached from the Info button in My Drive. Google describes it as a record of “changes made to your files in Drive” that lets you “keep track of who made those changes”, and lists the events it notices: someone “edits or comments in a file”, “renames a file or folder”, “moves or removes a file or folder”, “uploads a new file to a folder”, or “shares or unshares an item”.

Two qualifications, and both matter more than the feature does:

• It is file-level by construction. Even taken at its most generous, an activity entry says a file was edited and by whom. It does not say which question was reworded, which option was removed, or what the form looked like before. It is a timestamp with a name on it, not a diff.
• Google's page never mentions Forms. It speaks of “your files in Drive” generically. We could not establish from Google's own documentation whether, or how completely, an edit to a form's questions surfaces in that panel — so we are not going to tell you it does. Open the panel on your own form and look; that is a five-second check, and it beats anything we could reason out in public.

“Manage versions” is a different feature than it sounds

Drive's Manage versions command looks, from its name, exactly like the thing you are searching for. It is not. Google's Check activity & file versions page frames it as a store of uploaded file versions — the flow is More → Manage versions → Upload new version, with per-version Keep forever and Download actions, and a retention rule that “a version might be permanently deleted after 30 days or if there are 100 newer versions.”

The same page draws a line between the two worlds in its own words: “Version history for Google Docs, Sheets, and Slides is different than history for .pdf files, images, and other files stored in Drive.” Forms is named in neither half of that sentence. What we can say is what the feature does: it swaps one uploaded file for another and keeps the old bytes. A Google Form's questions are not a file you hold on your disk and re-upload, so there is nothing there that would reconstruct last week's wording. What we cannot say — because Google does not publish it — is exactly what the Manage versions dialog does when you point it at a form.

A third-party option: the Forms History add-on

Google Forms itself shows no version history, but a free add-on can browse the revisions Google keeps behind the scenes. Forms History, by Martin Hawksey, is free on the Google Workspace Marketplace and lets you see whether a form has changed and make a copy of an earlier version. Its own help page states the limits plainly:

• You need permission to edit the form.
• It cannot roll the original back — it creates a copy of the past version.
• Google sometimes merges revisions to save storage, so not every edit is there.
• Changes to responses, such as deletions, are not in the data Google provides.

So it is a way to recover an earlier form, not a record of who did what to your answers — for that, the sections above still apply.

What to do instead

Since Google will not keep the history for you, the job is to create restore points deliberately. In order of how much they save you:

1. Duplicate the form before a big edit. Make a copy first, and name it with the date. The copy freezes the questions as they stand and costs you ten seconds — how to duplicate a form. This is the only real rollback point Google can give you, and it is the habit worth building.
2. Keep the questions somewhere outside the form. Print the form to a PDF, or paste the question wording into a document, before a restructure. Once a question is gone from a form, the form itself is no longer evidence that it existed.
3. Reach for Undo immediately. It is session-bound, so its value decays to zero the moment you close the tab. If you have just done something wrong, do this before anything else.
4. Agree a convention on shared forms. With no attribution and no history, the only control available is social: one person restructures, everyone else comments.

Your responses are a separate question

Worth separating the two things people mean by “losing a form”, because only one of them is the subject of this page. The form's structure — its questions, their wording, their order — is what has no history. The responses are a different body of data, and Google does not publish a statement about what editing a form does to submissions already collected.

What Google does publish on the subject is about drafts in progress: if the owner deletes a question, “your answer to that question is deleted” — a sentence about an unsubmitted draft, not about your collected data. Because Google is silent on the submitted case, do not take anybody's word for it, ours included: check the response count before a restructure and again after it.

A history of your own saves, on iPhone

Forms+ is a native iPhone and iPad client for your real Google Forms, and it has a Revision History screen. Be clear about what it is before you rely on it: it is not Google's missing version history, and nothing can be. It is a record of saves you made in the app, kept in the app's own storage on that device, under the account you were signed in as. Edits made in Google's web editor, or by a collaborator, or on your other iPad, are never captured — the app can only snapshot a save it performed itself.

Within that boundary, it does the job Google leaves undone. Each save in the app adds a snapshot; identical saves are skipped rather than filling the list with duplicates; the app keeps the twenty most recent versions per form, and bounds the total it stores across all forms so history cannot grow without limit. From a version you can see what it contained, restore the form to it, or pull individual questions out of it into the form you are editing now. Revision History is a PRO feature in Forms+.

Frequently asked questions

Can I restore an earlier version of a Google Form?

Not through Google. Its page on finding what changed in a file covers Docs, Sheets, Slides and Vids, and Forms is not on that list. Google publishes no Forms equivalent and no restore command. Undo, within the editing session, is the only recovery control the Forms help pages document.

Can I see which collaborator edited a Google Form?

Google publishes nothing about attributing a change to a collaborator on a form. Its page on sharing a form with collaborators covers access, expiry and ownership transfer, and says nothing about edit history or who changed what. On a form several people can edit, that silence is the whole answer.

Does Google Drive activity show what changed in a form?

Drive's activity panel is file-level. Google describes it as a record of changes to your files and who made them, listing events such as editing, renaming, moving and sharing. Even at its most generous that tells you a file was edited, not which question was reworded. Google's page never names Forms, so we cannot establish from Google's documentation what a form shows there.

Do edits to a form change the responses I already collected?

Google does not publish an answer to this. The one statement it makes about a deleted question — that “your answer to that question is deleted” — describes an unsubmitted draft response, not data already collected. Since Google is silent on the submitted case, duplicate the form before a restructure and check the response count before and after.