Connecting a Google Form to a Google Sheet takes about ten seconds. Understanding what that connection is takes longer, and it is the part that saves time later. The form holds its own copy of every response whether or not a spreadsheet exists. The spreadsheet is a second copy that Google keeps appending to. Almost every problem people hit with this pairing comes from treating those two stores as one place, so it is worth getting the shape right before adding columns, formulas and collaborators on top of it.
Linking the form to a sheet, and the two places that do it
Open the form and click Responses at the top. At the top right there is a Link to Sheets button. Click it and Google offers two paths: create a new spreadsheet, or select an existing one. Pick the second and you will be asked which spreadsheet, and the responses arrive as a new tab inside it rather than taking over an existing tab.
The same setting lives in a second place, which is worth knowing because the button is not always where people expect it. From Responses, open the Summary tab, then More at the top right, then Select destination for responses. The choices there are the same two. The Summary tab only appears once at least one response has arrived, which is why a brand new form can look as though it is missing the option entirely.
Going the other direction works too. In a spreadsheet at sheets.google.com, Tools then Create a new form makes a new sheet inside that spreadsheet and opens a form already wired to it. That is the right move when the spreadsheet is the thing that already exists and you are adding intake to it.
Once linked, responses land as rows in the order they arrive, one row per submission, with a timestamp. The download route still exists alongside it: Responses, then More, then Download responses (.csv) gives you a point in time file that has nothing to do with the live sheet. Teams that only need a snapshot at the end of a campaign often do not need the link at all.
To break the connection, go to Responses, the Summary tab, More, then Unlink form. New responses stop flowing to the spreadsheet and the rows already there stay put. Google's own wording on this is precise: the unlinked destination still retains a copy of all previous responses. Nothing is cleaned up on your behalf.
The form keeps its own copy, and the sheet is the second one
This is the fact that explains most of the confusion, and Google states it plainly in the Apps Script reference: all forms, including those that do not have a destination set explicitly, save a copy of responses in the form's response store. Linking a sheet adds a destination. It does not move anything.
Two stores means two sets of behaviour, and they differ in ways that matter.
| The form's response store | The linked spreadsheet | |
|---|---|---|
| Exists | Always, link or no link | Only after you create the link |
| Deleting a response in the form | The response is gone | The row stays where it was |
| Editing a value | Not possible from the form side | Possible, and never sent back to the form |
| Unlinking | Unaffected | Keeps every row it already holds |
| File in Drive | Part of the form | A separate file you can delete on its own |
The deletion row is the one that catches people. Google's documentation for the scripting equivalent says it directly: deleting a response does not delete copies of responses stored in an external response destination such as a spreadsheet, though it does clear the form's summary view. Delete a test submission from the form and the spreadsheet row remains. Delete the row in the spreadsheet and the form still counts that response in its summary. Anyone doing a data cleanup has to do it twice, in both places, and confirm both.
The same separation applies to the files themselves. Google's help centre notes that you can delete the spreadsheet without deleting the form, or delete the form without deleting the spreadsheet. Neither takes the other with it.
The column you add is the thing that breaks
A response sheet starts out as pure output. It does not stay that way for long, because the moment a team starts working the responses, someone needs somewhere to write down what happened. A column called Status. A column called Who is handling this. A formula that pulls the applicant's region out of a postcode.
Those additions are where the friction begins, and it comes from a structural mismatch rather than a bug. New responses are appended at the bottom. Anything you type by hand sits in a specific cell on a specific row. Any change to the form's questions changes the shape of the columns. Sort the sheet to group by status, and the visual order no longer matches the arrival order that the next batch of responses will be written against.
The safest arrangement is to treat the response tab as read only in practice, even though Google will happily let you type in it. Put your own columns on a separate tab and pull the responses across, either with a formula range or with IMPORTRANGE if the working file should be a different spreadsheet entirely. Google's own best practice note on IMPORTRANGE is to restructure and condense the result before importing, and to limit the number of receiving sheets, because every receiver reads from the source.
Filters deserve a specific warning, because they look private and are not. Google's help is explicit: when you add a filter, anyone with access to the spreadsheet will find the filter too, and anyone with permission to edit can change it. One person narrowing the view to this week's submissions changes what everyone else sees. Filter views are the per person alternative, and they exist for exactly this reason.
Access to the form and access to the sheet are separate grants
This is the trap with real consequences, and it is documented rather than folklore. When you create a new response spreadsheet, the form's collaborators automatically get access to it. After that, Google says, further changes to the permissions of the form will not synchronise automatically, and to change or remove access you must update permissions on both the form and the linked sheet separately.
Read that again with a departure in mind. Remove someone from the form and they may still be able to open the spreadsheet with every response in it. Google's page on managing responses repeats the point: if you want to remove a collaborator, you have to remove them from the form and the spreadsheet separately.
Sharing the sheet has its own consequence, which is that Drive's roles are per file and not per row. A Viewer can open and download, but cannot comment or edit. A Commenter can comment. An Editor can edit and, by default, can also share the file and change permissions, though the owner can switch that off. There is no role that means "can see rows 1 to 40 only". Protected ranges are not that either: Google's own note on protecting sheets and ranges says it should not be used as a security measure, because people can print, copy, paste, import and export copies of a protected spreadsheet, and there is no password option.
If that mismatch is the problem you are actually trying to solve, it is worth looking at what per person, read only access to responses looks like when it is built in rather than assembled from Drive roles. How access is handled for a team is a different question from how a spreadsheet is shared.
The ceilings, and which one you meet first
None of these limits arrive early, but knowing them stops a guess turning into a false diagnosis when a sheet gets slow.
A Google Sheets file created in or converted to Sheets holds up to 20 million cells or 100 MB. That is the hard wall. Note that it is cells, not rows, so a form with 60 questions burns through the allowance more than thirty times faster per response than a form with two. Practical slowness usually arrives long before the ceiling, and formulas across the whole column are the usual cause.
On the sharing side, a single file can be shared with up to 600 individual email addresses. A Sheets file can be edited on up to 100 open tabs or devices at once, and beyond that only the owner and some users with edit permission can edit.
On the form side, the relevant limits are the ones you set yourself. Under Published, you can turn off Accepting responses, or set a close date, or set a maximum number of responses. One detail in that setting is worth reading before relying on it: if multiple people respond at the exact same time, the form accepts responses regardless of the response limit. A hard cap it is not.
What a spreadsheet cannot do for intake work
If the form is a one off survey, the sheet is the finish line. Answers arrive, someone reads the summary, the job ends, and everything above is trivia.
The strain shows up when responses need replies. Recruitment, enquiries, support intake, grant applications, course sign ups. Three things are missing from a spreadsheet for that kind of work, and no amount of column discipline supplies them.
There is no owner on a response, so a column has to stand in, and a column is only as accurate as the last person who remembered to fill it. There is no status, so "arrived", "being looked at", "replied" and "closed" live in a hand typed field with four spellings by month three. And there is no send box, so replying means copying an address into a mail client, after which the reply sits in one person's sent folder where nobody else can see that it happened. That last one is the expensive gap: it produces the applicant who gets two different answers and the applicant who gets none.
Notifications do not close the gap either, though they help. Responses, then More, then Get email notifications for new responses tells everyone that something arrived. It says nothing about who is dealing with it.
What a spreadsheet does well is analysis, reporting and handing data to another system. Tools built for the reply side keep the answers, the history and the send box on one screen, and some of them still write each response to a sheet as a row so the reporting side keeps working. That combination, rather than a choice between the two, is usually what the situation actually calls for, and the shapes of intake it suits are fairly easy to recognise.
What to change first
Do one thing this week: stop typing into the response tab. Move every hand maintained column to a separate tab that reads from it, and check right now whether anyone who left the form still has access to the linked spreadsheet, because Google does not revoke that for you. If the work after submit is the part that hurts rather than the spreadsheet itself, see what a form tool with response management handles on one screen.
Q1. Why are my Google Form responses not showing up in the sheet?
Check first whether the spreadsheet is still linked, because unlinking stops new responses without removing old rows. Then check whether you are looking at the right tab, since linking to an existing spreadsheet adds a new tab rather than writing into one you already use. If the link is intact, confirm the response actually reached the form by opening the Responses tab, as a form that has stopped accepting responses records nothing at all.
Q2. If I delete a row in the spreadsheet, does the response disappear from the form?
No. The two stores are independent. Google's documentation states that deleting a response from the form does not delete the copy in an external destination such as a spreadsheet, and the reverse is also true: a deleted row leaves the form's own response store untouched. To remove a response completely, delete it in both places.
Q3. Can I edit a form response in the spreadsheet and have the form update?
No. Edits in the spreadsheet stay in the spreadsheet. The form's own store keeps the answer as it was submitted. If respondents need to correct their own answers, the setting for that is on the form side, under Settings then Responses, where you can turn on response editing.
Q4. How do I share the responses without giving someone edit access to my form?
Share the linked spreadsheet with Viewer access and do not add the person as a form collaborator. Be aware that Drive roles apply to the whole file, so a Viewer sees every row and every column, and that anyone who already had access to the form when the spreadsheet was created may already have access to it.
Q5. Is there a limit to how many responses a Google Sheet can hold?
The limit is on the spreadsheet rather than the form: up to 20 million cells or 100 MB for a file created in or converted to Google Sheets. Because it counts cells, a form with many questions reaches it far sooner than a short one. In practice, heavy formulas make a large response sheet feel slow well before the ceiling is anywhere close.