Google Forms file upload limits

Last updated September 2026 · ~10 minute read

Short answer: Google publishes no numbers. Its help pages document four controls — file types, maximum number of files, maximum file size, and a maximum size for all files collected via the form — and give a value for none of them. What Google does state plainly is the expensive part: “For the form owner, uploaded files are stored in a new folder on Google Drive.” The responder's storage is untouched. Yours pays for every upload.

This page covers the consequences of a file upload question, not the mechanics of adding one — for those, see how to add a file upload question to Google Forms. Everything below is quoted from a Google page and linked to it; where Google says nothing, so does this page.

What Google publishes, and what it does not

Google's Choose a type of question for your form page (checked 14 September 2026) lists what you can do with a File upload question, verbatim:

• “Specify which file types responders can upload.”
• “Set up the maximum number of files responders can upload.”
• “Choose the maximum file size responders can upload.”

Google's Tips to customize your forms page in the Workspace Learning Center adds a fourth: “Set a maximum size for all files collected via the form.”

Four settings, zero figures. Google's Forms API reference is equally reticent: maxFiles is “Maximum number of files that can be uploaded for this question in a single response” and maxFileSize is “Maximum number of bytes allowed for any single file uploaded to this question” — neither with a documented range. A confident table of Forms upload limits was not copied from Google.

The per-file size limit and the number of files

People mean two things by “the limit”; Google documents one of them.

The ceiling you choose. Both the file count and the per-file size are settings the owner picks. Google's wording — “Set up the maximum number of files responders can upload” — makes it a rule you impose on respondents, not one Google imposes on you.

The hard ceiling above it. Google never states one for Forms. What it does state, for Drive as a whole, is that a single file can be “Up to 5 TB” (Files you can store in Google Drive) — a bound the Forms editor sits nowhere near. The editor presents a short fixed menu of sizes rather than a free-text box, so the top entry of that menu is the real ceiling, and Google commits to it nowhere. Note too that the file-count cap applies per response: ten respondents allowed ten files each is a hundred files. If a number is load-bearing for your project, open the question in the Forms editor and read the menu — that is the only figure true for your account today.

The total-storage ceiling for the form

This is the limit that actually stops a form, and the one most guides skip. Google lists it as a setting: “Set a maximum size for all files collected via the form.” It is a form-wide ceiling across every response ever submitted, not a per-response one — so a form that worked for a month can start refusing uploads with nothing having changed.

Google publishes neither the values available, nor the default, nor what a responder is shown when the ceiling is reached. It is also silent on whether deleting files out of the Drive folder frees the form's allowance back up. Do not assume it does.

Whose Drive, and whose storage quota

Here is the fact most pages get backwards. Google words it three ways across two pages, all pointing the same direction:

• “For the form owner, uploaded files are stored in a new folder on Google Drive.” (Choose a type of question for your form)
• “The files are copied to your Google Drive account, so you can view them anytime in Google Forms.” — addressed to you, the owner (Tips to customize your forms)
• “In Drive, there's a folder for each form. Files from respondents are stored by question in subfolders.” (same page)

And Google's storage rule settles the billing question: How your Google storage works states that files “only consume the cloud storage quota of the original file owner, never the recipient.” Copies made into your Drive are yours; you own them, so you pay for them.

A respondent uploads a 400 MB video and loses nothing; you gain 400 MB of consumption in an account that, on a personal plan, Google describes as having “up to 15 GB of storage which is shared among Drive, Gmail, and Photos” (Manage your storage in Drive, Gmail & Photos). Thirty-odd videos and a free account is full. Uploads are not the only thing a form puts on that 15 GB either — which of a form's Drive files is billed to whom is worked through in Google Forms and Drive storage.

What happens when the owner's Drive is full

Google is unambiguous, and it is worse than “uploads stop”:

“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.”

A form collecting files can therefore take down your email. Two follow-on facts before you go hunting for space:

• “Files in your Trash still count towards your storage until they are permanently deleted” (Delete files in Google Drive) — emptying the folder is not enough, you have to empty the Trash too.
• “If you're over your storage quota for 2 years, we might delete your content across Gmail, Drive, and Photos.”

What Google does not publish is what a responder sees when uploading into a full owner's Drive — whether the submission fails, fails silently, or is accepted without the file. It is silent, and this page will not invent an answer.

Sign-in is mandatory, and that is a limit too

The one restriction Google states in absolute terms: “To answer this question, responders need to sign in to a Google Account.” No setting disables it. Adding a file upload question converts an open form into a sign-in-only one, silently, for everyone who already has your link.

For an anonymous survey this is fatal rather than inconvenient: respondents without a Google account, or signed into a work account that cannot reach your form, simply cannot answer. If anonymity is the point, collect a link instead of a file — see how to make a Google Form anonymous for what the word actually means in Forms.

Two further blockers, in Google's wording: you cannot use the question type if “The form is stored in a shared drive” or if “Your administrator turns on Data Loss Prevention”. The Learning Center repeats the first flatly: “This feature is not supported using shared drives.”

Which file types you can restrict to

Yes, the owner can restrict them, and by default does not: “Turn on Allow only specific file types and select the types.” The categories are published — not in the help centre, but in the Forms API reference, whose FileType values are ANY, DOCUMENT, PRESENTATION, SPREADSHEET, DRAWING, PDF, IMAGE, VIDEO and AUDIO.

Note what that is not: a list of extensions. You can require “Document”, but not “.docx only”. If you need a precise format, say so in the question text and check on arrival. Each of those nine values, and what Google does and does not publish about what happens when a responder picks a disallowed file, is in which file types a Google Form can accept.

Copies and deletions: where Google is silent

Two questions get asked constantly and Google answers neither.

Does an upload question survive “Make a copy”? Google's Learning Center documents copying a form in general terms and never mentions file upload questions, the Drive folder, or what the copy points at. There is no published statement. If you use a form as a template, test a throwaway copy with a real file before trusting it.

What happens to the files if the form is deleted? Also unpublished. The uploads live in an ordinary Drive folder and the form is a separate Drive file, but Google does not state whether deleting one touches the other — its delete page covers only the general case. Copy anything you need out of the folder before deleting a form.

When a form is the wrong tool

A file upload question is excellent for one small attachment alongside answers — a receipt, a photo, a signed slip. Above a handful of files, a shared Drive folder is the better instrument, for a reason that falls out of Google's storage rule quoted above: in a shared folder each contributor's uploads consume their quota, because each is the original owner of what they upload. Through a form, every byte is yours.

A shared folder also has no form-wide size ceiling and no per-response file cap. What you lose is the structure: the files arrive without the answers attached. It still needs a Google sign-in to contribute, so it buys you nothing on anonymity.

Doing this from an iPhone or iPad

Forms+ is a native client for your real Google Forms and handles these settings directly: add or convert a File upload question, set the allowed file types, the maximum number of files and the maximum file size, and jump to the Drive folder the uploads land in. File answers reach the Responses tab as Drive links and carry into CSV, Excel and PDF exports.

Two honest limits. The form-wide “maximum size for all files collected via the form” is not exposed in Forms+ — set that one in the Google Forms web editor. And Forms+ is an editor and response client, not a responder app: submitting a file as a respondent happens on Google's own form page, signed in.

Frequently asked questions

What is the maximum file size for a Google Forms upload?

Google does not publish a number. Its help page says only that you can “Choose the maximum file size responders can upload”, and the Forms API reference describes maxFileSize as the “Maximum number of bytes allowed for any single file uploaded to this question” without stating a range. The editor offers a fixed menu of sizes rather than a free-text field, so the top entry of that menu on the day you look is your effective ceiling. Treat any figure you read elsewhere as observed, not guaranteed.

How many files can someone upload to a Google Form?

As many as the owner allows, up to a maximum picked from a menu. Google's wording is “Set up the maximum number of files responders can upload.” No Google page states the values in that menu, and the Forms API reference defines maxFiles as the maximum “for this question in a single response” without giving a range. The cap is per response, per question, not per form.

Is there a total storage limit on a Google Forms upload question?

Yes. Google's Workspace Learning Center lists it as a setting you control: “Set a maximum size for all files collected via the form.” It is a form-wide ceiling across every response, and once it is reached the form stops accepting uploads. Google does not publish the available values, the default, or what a responder sees when the ceiling is hit.

Whose Google Drive storage do Google Forms uploads use?

The form owner's. Google states that “For the form owner, uploaded files are stored in a new folder on Google Drive”, and the Workspace Learning Center puts it in the second person: “The files are copied to your Google Drive account.” Google's storage rule is that files consume “the cloud storage quota of the original file owner, never the recipient”, so responders give up none of their own space.

What happens when the form owner runs out of Drive storage?

Google states that “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.” A full account therefore breaks Gmail, not just Forms. Google does not publish what a responder sees when they try to upload into a full owner's Drive, so we will not guess.

Can people upload files without signing in to Google?

No. Google's help page states “To answer this question, responders need to sign in to a Google Account.” No setting turns it off, so a form with a file upload question cannot be anonymous or open to the general public.

Which file types can a Google Form accept?

Any type by default. Google lets the owner restrict them: “Turn on Allow only specific file types and select the types.” The categories are published in Google's Forms API reference as ANY, DOCUMENT, PRESENTATION, SPREADSHEET, DRAWING, PDF, IMAGE, VIDEO and AUDIO. They are broad categories, not a list of file extensions, so you cannot allow .docx while blocking .odt.