Google Forms and Drive storage

Last updated September 2026 · ~11 minute read

Short answer: a form is three Drive objects, not one, and each is billed to whoever owns it — never to the people filling it in. The surprise is the first one: since 1 June 2021 the form file itself consumes quota. Google lists “Files created or edited in collaborative content creation apps like Google Docs, Sheets, Slides, Drawings, Forms, Recorder, Vids, and Pics” among the things that count against your storage. What Google never answers is the question everyone actually asks: whether a respondent is blocked when the owner's Drive is full.

This page is about storage, not about upload caps — for the size and file-count settings on a File upload question, see Google Forms file upload limits. We looked in five places: Google's help centre, the Apps Script reference, the Forms REST reference, the Forms API v1 discovery document (revision 20260909), and Google's own code samples. Everything below is quoted from a Google page and linked to it; where Google says nothing, so does this page.

Three files, three bills

What people call “a form” is up to three Drive objects, each charged to its own owner.

The third row is already well documented: Google's Choose a type of question for your form page states “For the form owner, uploaded files are stored in a new folder on Google Drive”, and the Forms API names that destination as a folderId and returns each answer as a Drive fileId. The size and count caps on those files are covered in file upload limits. The first row is the one almost nobody expects.

The form itself counts — but only since 2021

Google's How your Google storage works page (checked 14 September 2026) lists what consumes an account's 15 GB. Forms is on the list by name, with a date attached:

• “Files created or edited in collaborative content creation apps like Google Docs, Sheets, Slides, Drawings, Forms, Recorder, Vids, and Pics.”
• “Files created or edited after June 1, 2021 count against your quota.”
• “Files uploaded or last edited before June 1, 2021 don't count against your quota.”

So a form you have not touched since May 2021 is genuinely free — and stops being free the moment you edit it. Google does not publish what a form's recorded size is computed from: question count, embedded images and revision history are all plausible, none documented.

Two Google references disagree about whether a form has a size

The Drive API v3 file reference defines size as “Size in bytes of blobs and Google Workspace editor files” and quotaBytesUsed as “The number of storage quota bytes used by the file. This includes the head revision as well as previous revisions with keepForever enabled.” Editor files have a size, and it is billed.

Apps Script says the opposite. Its Class File reference documents getSize() as: “Gets the number of bytes used to store the File in Drive. Note that Google Workspace application files do not count toward Drive storage limits and thus return 0 bytes.”

Both are current Google documentation. Our reading — an inference, not something Google states — is that the Apps Script note simply predates the June 2021 change and was never revised, because the help centre and the Drive API agree with each other and carry the date. The practical consequence is concrete: a script that audits your Drive with getSize() reports zero for every form and sheet it finds. Use quotaBytesUsed.

The response spreadsheet is a second bill

Google is unambiguous that the sheet is its own file. From Choose where to save form responses: “If you store responses in a spreadsheet, you have a separate file in Google Drive. You can delete the spreadsheet and not delete the form, or you can delete the form and not delete the spreadsheet.” The Forms API agrees by omission — the REST reference exposes it only as linkedSheetId, “the ID of the linked Google Sheet which is accumulating responses from this Form”, output-only, a pointer at a file it cannot touch.

Google's own code samples make the ownership question visible. In the Apps Script Form class, the response-destination samples make the file first — “// Creates a spreadsheet to use as the response destination.”, then SpreadsheetApp.create(), then form.setDestination(). The destination is a file that somebody creates, under some account — and Drive's rule is that a file consumes “the cloud storage quota of the original file owner, never the recipient”. Google never states who owns a response sheet created from the Forms editor by a collaborator rather than by the owner. Unlinking does not help either: “New responses won't be sent to the spreadsheet, but your current data remains intact” — the file, and its bill, stay.

If there is no linked sheet, responses live with the form, and Google does not publish whether they grow the form's recorded size. None of the five sources answers it.

What actually breaks when the owner's Drive is full

Google's over-quota list is specific, and Forms is on it by name:

• “You can't create new files in collaborative content creation apps like Google Docs, Sheets, Slides, Drawings, Forms, Vids, and Pics. Until you reduce your storage usage, nobody can edit or copy your affected files.”
• “When your account reaches its storage limit, you won't be able to upload or create files in Drive, send or receive emails in Gmail, or back up photos or videos to Google Photos” (Manage your storage in Drive, Gmail & Photos).
• “If you're over your quota for 2 years or longer … all of your content in your Google Account may be removed”, after at least three months' notice.

Read the first one twice: a full Drive does not only stop you making new forms — it stops your collaborators editing the forms you already own. One fact before you go hunting for space: trashed files still count, because “Until you permanently clear items in these folders, they count against your storage limit”.

Can a respondent be blocked by a full Drive? Google does not say

The question the whole topic turns on, and all five sources come back empty.

• The help centre addresses the over-quota consequences to the account holder. Nothing on either storage page mentions incoming form responses.
• Google's page for respondents, Fix common errors while you respond to a Google Form, is where a storage failure would have to be documented. It lists the sign-in requirement, the owner's file restrictions and “You can't upload a file from a shared drive” — and no storage reason at all.
• The REST reference has no storage or quota field on a form or a response.
• The v1 discovery document (revision 20260909) does not contain the word “storage” once; its only uses of “quota” are the generic quotaUser and API-key parameters every Google API carries.
• Google's code samples for a form's response destination create a Drive file without checking a quota first.

So nobody outside Google knows whether a submission into a full owner's account fails, fails silently, or succeeds without its attachment. Any page that tells you confidently is reporting an observation, not a published rule.

Where you can actually read the numbers

Not in Forms. The only published figures live in Drive's own API: about.storageQuota returns limit, usage, usageInDrive and usageInDriveTrash, all in bytes. One caveat most tools ignore: “For users that are part of an organization with pooled storage, information about the limit and usage across all services is for the organization, rather than the individual user.” On a Workspace plan you may be reading your employer's number, not your own.

Doing this from an iPhone or iPad

Forms+ is a native client for your real Google Forms, and it reads the same Drive figures. In Settings ▸ Data & Storage ▸ Google Drive storage it fetches your account's quota and draws it as a single bar split into Google Drive, Other (Gmail, Photos & more), Trash and Free space, above an “X used of Y” line. Empty Trash appears when there is anything in it, alongside Manage storage and Get more storage. That screen is free, with no PRO gate in front of it.

Two response-side features are PRO, and both are ones that touch Drive: Link to Google Sheets, which creates a real Google Sheets file on your Drive — the second bill described above — and View File Uploads, which opens a respondent's uploaded file from the Responses tab. Reading responses is free (free accounts wait out a refresh interval between fetches).

Three PRO automations that add files of their own

They belong on a storage page rather than a features page, because each one adds an object to the three-file list above, billed to the account you signed in with. All three sit in the editor's tools menu under Automate, each is PRO, and each is off until you switch it on, per form.

• Back up responses to Drive… writes timestamped copies of the responses into a “<form> — Backups” folder in your Drive on a schedule — Daily, Every 3 days or Weekly — as JSON or CSV. Each run writes a fresh complete copy, so this is the one thing described here that grows your usage on a timer rather than once. The app is blunt about what that copy is for: restoring means downloading it, since Google Forms cannot re-import responses.
• Sync to a sheet… creates an app-managed Google Sheet in your Drive on the first response and appends a row per submission — Timestamp, Email, then one column per question — so you can add your own Status or Score columns beside them. That is a different file from the linked response spreadsheet in the table above; Google's stays separate, so running both means two sheets and two bills. It does not backfill: submissions made before you switched it on are not written.
• Append to a Doc… creates a Google Doc on the first response and appends each new one as a dated entry — a running log, and one more file on the same quota.

One privacy consequence follows from the storage one. The app's Redact personal info on export switch masks files that leave the device; it does not apply to the Drive backups or to the synced Sheet, and both screens say so, because those are complete copies written on Google's side rather than exports.

That is not an exhaustive list of either tier — only the parts this page's subject touches.

One honest limit. Forms+ shows the account total, never a per-form figure — the Forms API publishes no size for a form, so no client can. Per-file bytes live in Drive's own storage view, which Manage storage opens.

Frequently asked questions

Do Google Forms count against your Google Drive storage?

Yes, since 1 June 2021. Google's storage page lists, among the things that consume your quota, “Files created or edited in collaborative content creation apps like Google Docs, Sheets, Slides, Drawings, Forms, Recorder, Vids, and Pics”, and adds that files “created or edited after June 1, 2021 count against your quota” while files “uploaded or last edited before June 1, 2021 don't count against your quota”. A form you have not touched since May 2021 is still free; edit it and it starts counting against its owner's 15 GB.

Does the responses spreadsheet use extra storage?

It is a second file with a second bill. Google states that “If you store responses in a spreadsheet, you have a separate file in Google Drive” and that you can delete either one without deleting the other. Sheets appears on the same list of apps whose files count against quota, so the spreadsheet consumes the storage of whoever owns it, which is not necessarily the form owner. Google does not publish who owns a response sheet created by an editor rather than by the form owner.

Whose storage do file upload answers use?

The form owner's. Google states that “For the form owner, uploaded files are stored in a new folder on Google Drive”, and its storage rule is that files consume “the cloud storage quota of the original file owner, never the recipient”. Respondents give up none of their own space. The Forms API names both halves: a file upload question carries a folderId, “the ID of the Drive folder where uploaded files are stored”, and each answer comes back as a Drive fileId.

What happens to a Google Form when the owner's Drive is full?

Google states that over quota “You can't create new files in collaborative content creation apps like Google Docs, Sheets, Slides, Drawings, Forms, Vids, and Pics. Until you reduce your storage usage, nobody can edit or copy your affected files.” So you cannot make a new form and your collaborators cannot edit the forms you already own. Gmail is hit at the same time, and after two years over quota Google may delete the content, with at least three months' notice.

Can a respondent be blocked by the form owner's full Drive?

Google does not say, in any of the five places we checked. The over-quota list is addressed to the account holder and never mentions incoming responses. Google's own page for respondents, Fix common errors while you respond to a Google Form, lists sign-in, owner-set file restrictions and shared drives as reasons an upload fails, and no storage reason at all. The Forms REST reference has no storage field, the v1 discovery document does not contain the word storage once, and Google's code samples create Drive files without checking a quota. Treat any confident answer you read elsewhere as observed, not documented.

How much storage does one Google Form use?

Google publishes no figure and the Forms API exposes no size field, so the only honest answer comes from Drive. The Drive API reports quotaBytesUsed per file, “the number of storage quota bytes used by the file”, including previous revisions kept forever, and about.storageQuota reports the account totals. Be careful with Apps Script: its File.getSize() documentation still claims Google Workspace application files return 0 bytes, which contradicts both the Drive API and the help centre.