How to Create a Google Form With File Upload (+ Better Options)

Google Forms supports file uploads. You can add a file upload question to any form and let respondents attach documents, images, spreadsheets, or any other file type. For internal teams already using Google Workspace, it works fine. But there is one requirement that kills it for most external-facing use cases: every respondent must sign in with a Google account to upload a file.

No Google account, no upload. No workaround. No toggle to disable it.

This single requirement causes massive drop-off on job application forms, customer support intake forms, vendor onboarding questionnaires, and any other form where you cannot guarantee that every respondent has a Google account. This guide walks you through exactly how to set up file uploads in Google Forms, explains the limitations you will hit, and covers the alternatives that do not force your respondents to log in.

How to Add File Upload to a Google Form

Setting up file uploads in Google Forms takes about two minutes. Here is the step-by-step process.

Step 1: Create or Open Your Form

Go to forms.google.com and create a new blank form, or open an existing form you want to add file uploads to. You must be signed in to a Google account to create forms.

Step 2: Add a File Upload Question

Click the "+" icon in the floating toolbar on the right side to add a new question. Click the question type dropdown (it defaults to "Multiple choice") and select File upload from the list.

The first time you add a file upload question, Google Forms will display a warning: "Respondents will be required to sign in to Google." You must click "Continue" to proceed. This requirement cannot be disabled.

Step 3: Configure File Type Restrictions

After adding the file upload question, you can optionally restrict which file types respondents can upload. Toggle on "Allow only specific file types" and select from the available categories:

• Document -- .doc, .docx, .pdf
• Spreadsheet -- .xls, .xlsx, .csv
• Presentation -- .ppt, .pptx
• Drawing -- images created in Google Drawings
• Image -- .jpg, .png, .gif, .bmp, .tiff
• Video -- .mp4, .avi, .mov, .wmv
• Audio -- .mp3, .wav, .ogg
• PDF -- .pdf specifically

If you leave this toggle off, respondents can upload any file type.

Step 4: Set the Maximum Number of Files

Below the file type selector, set the maximum number of files each respondent can upload per question. The options are 1, 5, or 10. The default is 1. If you need respondents to upload multiple documents (e.g., a resume and a cover letter), set this to the appropriate number or use separate upload questions for each file.

Step 5: Set the Maximum File Size

Set the maximum file size per file. The options are 1 MB, 10 MB, 100 MB, 1 GB, or 10 GB. The default is 10 MB. Choose the smallest size that accommodates your use case -- larger limits eat into your Google Drive storage faster.

Step 6: Publish and Test

Click the "Send" button to share your form. Before distributing it widely, test the form yourself by opening the link in an incognito window. You will immediately see the Google sign-in prompt, which is exactly what your respondents will experience.

File Upload Limits in Google Forms

Google Forms file uploads are stored in the form owner's Google Drive. This has direct implications for storage and limits.

The total storage limit is the one that catches people off guard. By default, a form allows 1 GB of total uploads across all respondents. Once that limit is hit, the form stops accepting file uploads. You can increase this to 10 GB in the form settings, but it still draws from your Google Drive quota. If you have a free Google account with 15 GB of storage, a single form collecting large files can consume a significant portion of your available space.

For Google Workspace accounts, storage is pooled across the organization, which gives more breathing room. But even then, a popular form collecting video files or high-resolution images can burn through storage quickly.

The Google Sign-In Requirement: The Real Problem

This is the number one reason teams abandon Google Forms for file uploads. When you add a file upload question, Google Forces every respondent to sign in with a Google account before they can submit the form. Not just before they can upload a file -- before they can submit the form at all.

Here is why this is a dealbreaker for most external-facing forms:

Drop-off rates spike. When an external respondent hits a Google sign-in wall, a significant percentage will leave. They do not want to create a Google account to submit a job application. They do not want to sign in to report a support issue. They do not want to authenticate with Google just to send you a screenshot. Every unnecessary friction point reduces completion rates, and a mandatory login is one of the highest-friction barriers you can add to a form.

Not everyone has a Google account. This seems obvious, but it is frequently overlooked. In enterprise environments, many employees use Microsoft 365 exclusively. In some countries and industries, Google account penetration is lower than you might assume. Requiring a Google account excludes these respondents entirely.

Privacy concerns. Some respondents do not want to link their Google identity to a form submission. This is especially relevant for anonymous feedback forms, whistleblower reports, or any form where the respondent expects anonymity. The sign-in requirement makes true anonymity impossible.

Mobile friction. On mobile devices, the Google sign-in flow can be especially disruptive. If the respondent is not already signed in to a Google account on their mobile browser, they have to navigate a multi-step authentication flow, potentially including two-factor authentication, before returning to the form.

There is no native setting to disable this requirement. Google enforces it because uploaded files are stored in the form owner's Google Drive, and Google needs to track who uploaded what for storage management and abuse prevention. The sign-in requirement is architectural, not a policy choice.

The Shared Drive Gotcha

There is a second, less-known issue. If your Google Form is stored in a Shared Drive (formerly Team Drives), the file upload question type is greyed out and cannot be added. Google does not support file uploads on forms owned by Shared Drives.

This catches teams that have migrated their organizational files to Shared Drives for collaboration. They create a form in the Shared Drive, try to add a file upload question, and find the option is unavailable. The workaround is to create the form in your personal "My Drive" instead, but that means the form and all uploaded files are owned by an individual, not the organization -- which creates its own problems for teams.

Workarounds for File Upload Without Google Sign-In

If you are committed to using Google Forms but need file uploads without the sign-in requirement, here are the available workarounds. None of them are ideal.

Workaround 1: Formfacade Add-on

Formfacade is a third-party Google Forms add-on that replaces the standard Google Forms UI with a custom front-end. When respondents fill out a Formfacade-powered form, they do not see Google's interface and are not prompted to sign in.

Formfacade supports file uploads without requiring Google authentication. Uploaded files are stored in the form owner's Google Drive, but the sign-in requirement is bypassed because Formfacade handles the upload server-side using its own credentials.

Limitations:

• Paid. Formfacade starts at $9.99/month. The free tier exists but does not support file uploads without sign-in.
• 10 MB file size limit. Regardless of what you set in Google Forms, Formfacade caps uploads at 10 MB per file.
• UI replacement. You lose the native Google Forms interface. Formfacade's styling is functional but limited. You cannot use Google Forms' built-in themes or visual customization.
• Dependency risk. You are adding a third-party layer between your respondents and Google Forms. If Formfacade goes down or changes its pricing, your forms break.

Workaround 2: Google Apps Script with Base64 Encoding

Developers can build a custom HTML form that uses Google Apps Script as the backend. Instead of using Google Forms' native file upload, respondents upload files through the custom form, which encodes the file as base64 and sends it to a Google Apps Script endpoint. The script then decodes the file and saves it to Google Drive.

Limitations:

• Technical complexity. This requires JavaScript, HTML, and Google Apps Script knowledge. It is not a no-code solution.
• 6 MB payload limit. Google Apps Script has a maximum URL Fetch payload of 50 MB, but the base64 encoding adds roughly 33% overhead, and execution time limits further constrain file size in practice. Large files will fail.
• Execution time limits. Google Apps Script has a 6-minute execution time limit (30 minutes for Workspace accounts). Processing large files can exceed this.
• No native form features. You lose Google Forms entirely -- validation, multi-page forms, response collection, and the Sheets integration all need to be rebuilt manually.

Workaround 3: Use a Different Tool

The most straightforward workaround is to stop using Google Forms for file uploads and switch to a form builder that handles them natively without requiring sign-in. This is the approach we recommend, and we cover the options in the next section.

Google Forms File Upload vs. Alternatives

For a full breakdown of pricing across all these platforms, see our form builder pricing comparison. For a head-to-head on Buildorado, Tally, and Fillout specifically, see Buildorado vs Tally vs Fillout.

How Buildorado Handles File Uploads

Buildorado was built for external-facing forms where you cannot control who your respondents are. File uploads work without any login requirement -- respondents drag and drop files or click to browse, and the upload starts immediately. No authentication, no Google account, no friction.

No Login Required

Respondents upload files without signing in to anything. The form is public, the upload is public, and the file is securely stored. This is the default behavior, not a workaround or a premium feature.

Drag-and-Drop with Progress Indicators

The upload interface supports drag-and-drop and shows a per-file progress bar. Respondents can see exactly how much of their file has uploaded, which is especially important for larger files on slower connections. Google Forms shows a basic spinner with no progress indication.

Custom File Type Validation

You can restrict uploads to any file extension, not just the broad categories Google Forms offers. Need to accept only .ai and .psd files for a design submission form? Set the allowed extensions to exactly those types. Need .dwg files for architectural drawings? Add it to the list. You are not limited to Google's predefined categories.

Secure Cloud Storage

Uploaded files are stored in Buildorado's secure cloud storage backed by S3. Files are accessible through signed URLs with time-limited access, ensuring that uploaded documents are not publicly accessible to anyone with a direct link. For organizations that need to control where their data lives, the storage infrastructure is designed with security and access control in mind.

Use Cases: When You Need File Uploads on Forms

Job Applications with Resume Upload

Applicants submit their resume, cover letter, and portfolio samples through a single form. You need file uploads that work without login because candidates come from everywhere -- they use Outlook, Yahoo Mail, iCloud, or corporate email systems that have nothing to do with Google. Requiring a Google sign-in to apply for a job is a guaranteed way to lose qualified candidates.

In Buildorado, you can set up separate upload fields for each document type, restrict file types (PDF and DOCX for resumes, PDF and JPG for portfolio pieces), and use conditional logic to show the portfolio upload field only when the applicant selects a creative role.

Customer Support with Screenshot Uploads

Support ticket forms need to collect screenshots, error logs, and diagnostic files. Your customers are frustrated before they even open the form -- making them sign in to Google to submit a bug report adds insult to injury. The upload process needs to be as frictionless as possible.

Event Registration with Document Uploads

Conference registration forms that require proof of student status, professional certifications, or organizational affiliation need document uploads. Attendees may be submitting from mobile devices in a hurry, and a Google sign-in wall during mobile registration is a conversion killer.

Vendor Onboarding with Compliance Documents

Procurement teams collecting W-9 forms, certificates of insurance, business licenses, and signed contracts need a secure upload process that does not require vendors to have Google accounts. Many vendors operate in environments where Google Workspace is not used. Forcing them into a Google sign-in flow delays onboarding and creates unnecessary back-and-forth.

Other Google Forms Limitations to Consider

If you are hitting the file upload wall, you are likely running into other Google Forms limitations as well. The sign-in requirement is part of a broader pattern -- Google Forms is a free survey tool, not a full-featured form builder.

• No native payments. Google Forms cannot collect payments without third-party workarounds.
• Limited conditional logic. Branching is section-level only, restricted to multiple choice and dropdown questions. See our full guide on conditional logic in Google Forms.
• Limited integrations. Native integrations are restricted to Google Sheets. Anything beyond that requires add-ons or Zapier.
• No branding control. You can change the header image and accent color. That is the extent of visual customization.
• No workflow automation. There are no built-in triggers, notifications beyond basic email, or multi-step processes after submission.

These limitations compound. A form that needs file uploads also probably needs conditional logic, custom branding, and post-submission workflows. Google Forms cannot deliver on any of those.

Build File Upload Forms Without the Login Wall

Google Forms' file upload feature works for internal teams that are already in the Google ecosystem. For everyone else -- job applicants, customers, vendors, event attendees, or any external audience -- the mandatory Google sign-in is a dealbreaker.

You should not have to choose between collecting files and losing respondents. Buildorado handles file uploads the way they should work: drag and drop, no login required, custom file type validation, virus scanning, and configurable storage. All on the free tier.

Get started with Buildorado free and build your first file upload form in under five minutes. No credit card required. For a walkthrough of the platform, see our getting started guide.