Google Forms vs “Google Sheets forms”

Last updated September 2026 · ~9 minute read

Short answer: there is no form editor inside Google Sheets, and never was — but Sheets can still start a form, and the route survives under a name most people are not looking for. It is not Insert; it is Tools › Create a new form, on a computer. Google's own wording for what happens next is the whole story: “A new sheet will appear in your spreadsheet, and your form will open.” Two files, one relationship, and the data runs one way.

“Google Sheets forms” is a search for something that does not quite exist. What exists is a Google Form with a spreadsheet destination — and once you see it that way, most of the surprises stop being surprising.

The route from Sheets still exists. It moved.

Google's page How to use Google Forms lists three places a form can begin, and one of them is a spreadsheet. Under the heading “Create a form in Google Sheets”, the documented steps are:

1. On a computer, open a spreadsheet at sheets.google.com.
2. Click Tools › Create a new form.
3. A new sheet will appear in your spreadsheet, and your form will open.

If you remember an Insert menu entry for forms, your memory is not the documentation. The command Google publishes today sits under Tools. That single relocation is responsible for a large share of the “Google removed forms from Sheets” confusion — it did not, it renamed and moved the door.

Two limits are worth reading off the same page rather than assuming. First, the instruction says on a computer. Switch that help article to its iPhone & iPad tab and the Sheets route disappears entirely: the only creation route Google documents for iOS is opening forms.google.com in a mobile browser. Second, the form that appears is a form — it opens in Google Forms. Nothing in the spreadsheet becomes a question editor. Sheets is the launcher, not the host.

“Bound” versus “linked”: what Google actually publishes

People describe a form made from a spreadsheet as bound to it, and a form connected afterwards as merely linked, as if these were two grades of attachment. Google's documentation does not support the distinction.

In the help centre, both roads lead to one article — Choose where to save form responses — which describes storing responses “in a linked Google Sheet” without ever distinguishing how the pairing was made.

The developer reference is more explicit, because it has to name the thing. In Apps Script the relationship has exactly one word: destination. A form exposes setDestination(), getDestinationId(), getDestinationType() and removeDestination(), and the only value the DestinationType enum offers is SPREADSHEET, defined as “A Google Sheets spreadsheet as a destination for form responses.” A destination is a pointer, not a parent.

Meanwhile Google does use the word “bound” — for something else entirely. In Container-bound scripts, “a script is bound to a Google Sheets, Google Docs, Google Slides, or Google Forms file if it was created from that document,” and such scripts “cannot be detached from their container.” That is code attached to a file. It is not a form attached to a spreadsheet, and borrowing the term for the form-sheet pairing imports a permanence that does not exist.

One more reference line dismantles the idea of a form owning its spreadsheet. Apps Script's Spreadsheet.getFormUrl() warns that “if multiple forms send responses to this spreadsheet, the form URL returned is indeterminate,” and directs you to Sheet.getFormUrl() for per-sheet associations. The connection is really per tab. One spreadsheet can be the destination of several forms at once, which is exactly what makes “the form of this spreadsheet” an unanswerable question.

What a spreadsheet genuinely cannot do

Not a dismissal — a list of the specific capabilities that live in the Forms editor and have no equivalent in a grid of cells.

• No question types. Google's Choose a type of question for your form is a list of things a column is not: short answer, paragraph, multiple choice, checkboxes, dropdown, file upload, linear scale, rating, multiple choice grid. A column has a format; a question has a type, with its own answer UI and its own rules.
• No Required. The same page documents a per-question Required toggle. A spreadsheet cannot refuse to accept a row because a cell is empty. What that toggle enforces, and what it leaves behind when it is off, is in required vs optional.
• No response validation. Forms documents rules such as maximum and minimum character counts on short answer and paragraph questions. Sheets has its own in-cell dropdown lists and validation, which is a genuinely useful thing — but it constrains a cell for whoever is editing the file, not an answer for someone holding a link. Our guide to Google Forms data validation covers the form side.
• No branching. Show questions based on answers documents Go to section based on answer, available on multiple choice and dropdown questions, plus per-section “which section comes next” routing. A spreadsheet has no sections to skip. See conditional logic in Google Forms.
• No separation between author and respondent. This is the quiet one. Sharing a spreadsheet for data entry hands people the whole file — every other row, every formula, the ability to overwrite a neighbour's answer. A form link exposes one blank instance of the questions and nothing else.

The direction of the data — and where Google goes quiet

Responses flow one way: form to sheet. That much is documented, and so is the fact that the sheet is a second copy rather than the original. From the Apps Script reference, stated twice for emphasis in Google's own docs: “All forms, including those that do not have a destination set explicitly, save a copy of responses in the form's response store.” And on removeDestination(): “The unlinked former destination still retains a copy of all previous responses.”

So the form's store is the record. The spreadsheet is a live copy that keeps receiving.

Now the honest part: Google publishes nothing about the other direction. No help page states what happens to a form when you edit a response cell, delete a row, sort the sheet, or insert a column. It is not documented as supported, and it is not documented as ignored. Google is silent — and silence is not permission.

This is the single most dangerous assumption people make about the pairing, because a spreadsheet invites editing in a way a database never does. The cell accepts your typing, the row vanishes when you delete it, and nothing warns you that the form's own copy is untouched. If you are correcting or removing data for a real reason — a duplicate, a test entry, a privacy request — do it in both places and treat the form as the one that counts. The full treatment of linking, unlinking, permissions and what survives each is in our guide to Google Forms responses in Google Sheets.

When the spreadsheet really is the right place to start

Sometimes the search behind “Google Sheets forms” is correct and a form is the wrong tool:

• The columns already exist. If a colleague has been keeping the data in a sheet for a year, the structure is settled. Starting from the spreadsheet via Tools › Create a new form keeps the existing file as the home and adds a collection surface to it.
• You are the only one entering data. A form is a wrapper for other people's typing. Typing twelve rows yourself is faster in a grid than in twelve form submissions, and nobody needs a link.
• The answers are an input to calculation. If what you want is a pivot table, a running total, a lookup against a roster, then the sheet is the product and the form is just the front door.
• The output must be a spreadsheet anyway. Choosing the destination up front saves the later reconciliation between a form export and a hand-maintained file.

The reverse test is just as simple. If strangers will fill it in, if answers must be validated, if some questions depend on earlier ones, or if respondents must not see each other's data — it is a form, and the spreadsheet is where the answers land afterwards. And if the answers should become records in a database rather than rows in a sheet, the comparison to read is Google Forms vs Airtable forms.

Side by side

Turning spreadsheet columns into real questions

If your starting point is a list of fields already sitting in a spreadsheet, the gap to close is columns-to-questions. Forms+ does that on iPhone and iPad: in the editor's Build tools, Import questions from CSV… takes a CSV or TSV file laid out as one row per question with up to four columns — Title, Type, Options, Required — shows a preview of everything it parsed with each row tickable, and inserts the ones you keep into the form you have open. A first row labelled “Title” or “Question” is treated as a header and skipped. Export your sheet as CSV, and the columns you already wrote become questions rather than something to retype.

Going the other way, Export to Sheets in the Responses tab sends the responses to a Google Sheet in your own Drive — the same job covered, on the desktop side, by our responses in Google Sheets guide.

Frequently asked questions

Can you create a Google Form from inside Google Sheets?

Yes, on a computer. Google documents the route as: open a spreadsheet at sheets.google.com, click Tools and then Create a new form. Google then states that a new sheet will appear in your spreadsheet, and your form will open. The form itself opens in Google Forms — Sheets starts it, it does not host it.

Is the route still called Insert and then Form?

No. The command Google documents today lives under Tools and is called Create a new form. If you are hunting the Insert menu for a Form entry, that is why you cannot find it. Google's help page for creating forms lists three starting points: forms.google.com, the Tools menu in Sheets, and New and then Google Forms in Google Drive.

Is a form created from Sheets different from a form linked to a sheet later?

Google does not publish any difference. Both are described by the same article, Choose where to save form responses, and Apps Script gives the relationship one name in both cases: a destination, set with setDestination and removed with removeDestination. There is no documented ownership, and nothing that ties a form permanently to the spreadsheet it was started from.

Can I edit a response by editing the cell in the spreadsheet?

You can type in the cell, but Google's help pages do not document any effect on the form. They are silent on it. What Google does publish is that all forms, including those that do not have a destination set explicitly, save a copy of responses in the form's response store — so the form keeps its own record and your edit changes the copy only.

Can one spreadsheet collect responses from more than one form?

Yes. The Apps Script reference for Spreadsheet.getFormUrl notes that if multiple forms send responses to this spreadsheet, the form URL returned is indeterminate, and points to Sheet.getFormUrl for per-sheet associations. The link is really per tab, so one spreadsheet can be the destination for several forms, each writing to its own sheet.