Google Forms file upload requires sign in, and cannot be turned off

Yes, and it cannot be turned off

Google Forms requires every respondent to sign in to a Google account as soon as the form contains a file upload question, and there is no setting anywhere in Forms, Drive or Workspace that removes it. Google says so in the form editor itself: add an upload question and it tells you respondents will be required to sign in to Google.

If you are collecting from customers, applicants, parents, patients or the general public, that is not a small friction. It is a wall in front of an unknown fraction of the people you asked, and they do not tell you they hit it. They close the tab.

Below is why the requirement exists, the four things people try that do not work, and the two shapes of answer that do — plus the question that separates them, which most pages on this topic never ask.

Why the requirement exists

A file uploaded through Google Forms is written into the form owner's Google Drive. That is the feature, and it is also the reason for the gate. Google is being asked to accept an arbitrary file from an arbitrary stranger and put it inside somebody's private storage, so it insists on an identified account it can attribute the write to, scan against, and revoke.

Understanding that explains why no setting helps. The sign-in is not a privacy option attached to your form; it is a condition of the write into Drive. It also explains why the requirement is specific to the upload question. A form of nothing but text questions asks Google to store the answers in its own responses table, which is a different operation with a different risk, and it happily takes those anonymously.

The four things that do not fix it

These come up constantly in the Google Docs help forums, and all four are dead ends.

• Making the form public. There is no "public" that overrides it. A form anyone can reach still demands an account at the upload question.

• Turning off "Collect email addresses". Setting this to verified does force sign-in on its own, so switching it off is a reasonable guess. It removes that reason for sign-in and leaves the upload question's reason untouched.

• Turning off "Limit to 1 response". Same story. This setting genuinely does require sign-in, so people who have both switched on assume it is the culprit. Removing it does not help while an upload question remains.

• Changing the Workspace sharing or organization restrictions. Relaxing "Restrict to users in your organization" widens who may respond. It does not remove the requirement that they be somebody.

The reliable way to confirm this on your own form is to delete the upload question and open the live link in a private browsing window. The sign-in prompt goes with it, which tells you where the requirement was coming from.

Answer one: keep the form, move the file out of it

If Google Forms suits you otherwise, take the file out of the form and collect it separately. Replace the upload question with a short text field asking people to send the file, and give them somewhere to send it.

What Drive itself offers here is thinner than people expect. Drive has no public upload link of the kind Dropbox has; sharing a folder with edit rights requires the other person to have an account, and Workspace visitor sharing, which does let a non-Google user in, needs a paid Workspace plan, an emailed invitation and a PIN each visitor verifies. That is a workable route for a named collaborator you already know. It is not a route for a stranger arriving from your website.

The honest version of this answer is that you accept a two-step process — they answer the form, then they send the file by some other means — and you accept the reconciliation work of matching the two up afterwards. For a low volume of submissions that is genuinely fine and costs nothing.

Answer two: collect on a form that does not have the constraint

The constraint belongs to Google Forms, not to Google Drive. A form on your own site, posting to a service you have authorized against your own Google account, can accept a file from an anonymous visitor and put it in your Drive, because the write into Drive is being made by you rather than by them.

That is the whole trick, and it is not exotic. The visitor gets a short-lived, single-purpose address to send exactly one file to — one that is bound to their submission, expires quickly, and cannot be pointed at anything else in your Drive. They never authenticate, never see a folder, and never hold anything reusable. On your side the file arrives in a folder you own, under your account, subject to your own retention rules.

You also stop losing the context. Because the file arrives as part of a submission rather than on its own, it lands filed against the answers that explain it, so the record and the attachment point at each other instead of being two separate piles to reconcile.

The question to ask before you pick a tool

Search this problem and you will find a row of products promising uploads without sign-in. Most of them deliver exactly that. The thing to check, which their landing pages tend not to lead with, is where the file ends up.

There are two different products being sold under one promise:

• The file lands in the vendor's storage. You get an upload page and a dashboard, and you retrieve files from their system. Removing Google from the flow is how they removed the sign-in. If they close, raise prices, or have an outage, your files are inside that.

• The file lands in your Google Drive. The tool holds an authorization against your Google account and writes on your behalf. The files are yours, in your Drive, from the moment they arrive.

Both are legitimate. They are just not the same thing, and if you came here because you wanted files in Drive without a sign-in, the first kind has solved half of your problem and quietly abandoned the other half. Ask the question directly, before you migrate anything.

The narrower version of the same question: what can the tool see? An authorization limited to files the tool itself creates cannot read the rest of your Drive. A broader one can. It is worth two minutes on a permissions page.

When the sign-in requirement costs you nothing

Stick with Google Forms and its upload question if the people filling in your form are inside your own organization, or are a school community, or are anyone else who reliably already has a Google account and is already signed in. For them the requirement is invisible — no extra step, no prompt — and you get file uploads into Drive for free, with no third party involved and nothing to maintain. Adding anything to that arrangement is work with no return.

It is also worth keeping if you actively want the identity. For an internal request queue, a staff expense claim or a student submission, knowing which account uploaded a file is a feature, and Google Forms gives it to you without you building anything.

The requirement is only a problem when your respondents are strangers. It happens to be a very common case, and it is the one Google Forms was never built for.