Google Forms File Upload on iPhone: The 2026 Guide

Can Google Forms Collect File Uploads?

Yes — Google Forms collects files through a dedicated File upload question type, and it works for photos, PDFs, documents, spreadsheets, audio, and video. You add it like any other question, respondents get a picker, and everything they send lands in a folder in your Google Drive, sorted into subfolders by question. Google’s own question type documentation covers the basics of the field and its settings.

The catch is one sentence long and it shapes everything else in this guide: respondents have to sign in to a Google account to upload anything. That single requirement decides whether file upload is the right tool for your situation. Collecting assignments from students who already have school Google accounts? Perfect fit. Collecting ID photos from the general public, half of whom use Outlook? You are about to lose a lot of submissions at a sign-in wall. Everything below assumes you’ve read that sentence twice.

How to Add a File Upload Question (on iPhone)

Adding a file upload question from an iPhone takes about thirty seconds in Safari — the flow is the same as on desktop, just tighter on screen. Open your form in the editor, add a question, switch its type to File upload, and accept the notice Google shows you about sign-in.

Two settings deserve a moment’s thought rather than a default. File types are your first line of defence against a folder full of screenshots when you asked for PDFs — restricting the type turns a soft request into an enforced rule. Maximum file size ranges from 1 MB up to 10 GB; picking a modest ceiling like 10 MB keeps a single 4K video from swallowing your Drive quota, but set it too low and iPhone photos — which are large by default — start bouncing.

If you’re building the form on a phone regularly, this is exactly the part our iOS app smooths out: Forms for Google Drive (by Pipiform) lets you add file upload questions natively and import content by taking a photo, picking from your library, browsing a folder, or pasting from the clipboard, plus insert math formulas for quiz-style forms — these are paid features, and the app includes a 3-day free trial so you can test the workflow before subscribing. It changes the creator’s experience, not the respondent’s; the sign-in requirement below is Google’s and stays exactly as it is.

The Sign-In Requirement (The Limit Everyone Hits)

The sign-in requirement is absolute: adding a file upload question forces every respondent to authenticate with Google before submitting, and it applies to the whole form, not just the upload question. There is no toggle, no setting, and no supported workaround inside Google Forms — a point third-party guides like FileRequestPro’s 2026 breakdown make just as bluntly, because it’s the number one reason people go looking for alternatives.

What the requirement actually means depends on the account that owns the form:

• Personal Google account — respondents must sign in with any Google account. Broad, but still a wall for anyone without one.
• Google Workspace account — adding file upload also switches on “restrict to users in your organization”, so only people inside your domain can respond at all. Great for a school or company; fatal for collecting files from clients, parents, or the public.

That second case catches teams off guard: a Workspace form that used to accept outside responses quietly stops doing so the moment an upload field appears. And this is also the answer to a question we hear constantly — why does my form suddenly require sign-in? Nine times out of ten someone added a file upload question, which is worth checking before you go hunting through settings. If your form is misbehaving in other ways too, our Google Forms not working on iPhone guide walks the rest of the diagnostic tree.

If you truly need sign-in-free uploads, be honest with yourself early: Google Forms cannot do it, and no add-on changes the underlying rule. Tools built for that job — Formfacade’s file upload, Jotform, and similar services — replace the upload step with their own authentication-free flow. That’s their capability, not ours and not Google’s, and choosing them means moving the collection off Forms.

Fixing Photo Uploads from iPhone (Library Fails, Camera Works)

Here’s the iOS-specific quirk almost nobody documents: uploading a photo straight from the iPhone photo library often fails, while the “Take Photo” option in the same picker works fine. It’s not your form and it’s not the respondent doing something wrong — it’s a long-standing iOS behaviour with web form uploads, documented plainly in public upload guidance such as Charnwood Borough Council’s, which tells residents that some library images won’t upload but that Take Photo “will upload without any problems.”

The iPhone upload failure people email us about is almost always this one, and the fix is the same every time: tell them to use Take Photo, or to route the existing photo through Files first. That second path takes about ten seconds:

If the photo still won’t go, work down three other suspects in order. Connection — uploads need a stable link for the whole transfer, and a phone drifting between Wi-Fi and cellular mid-upload will drop it silently. File type — if you restricted the question to PDFs, an iPhone photo (HEIC or JPEG) is rejected without much explanation. Storage — if the form owner’s Drive is full, uploads fail no matter what the respondent does. A good habit when you send an upload form to a phone-heavy audience is to put one line in the question description: “If a photo won’t upload from your library, use Take Photo or save it to Files first.” It prevents most of the support messages before they happen.

Storage and File Limits to Plan Around

Every uploaded file counts against the form owner’s Google Drive storage, not the respondent’s — the most consequential limit in this whole feature. Fifty students uploading two 5 MB photos each is half a gigabyte out of your quota, and a video assignment can hit that with a single submission.

This matters beyond housekeeping, because a full Drive doesn’t degrade gracefully: uploads stop working and submissions fail. If a form that worked last week suddenly refuses files, check your storage before you check anything else — it belongs in the same mental bucket as forms that stop accepting responses for other reasons, which our Google Forms response limit guide covers.

Plan around the numbers rather than discovering them. If you’re collecting photos from a class, cap file size at 10 MB, allow images only, and set the file count to what you actually need — three photos, not ten. Tight limits protect your storage and cut the failure rate at the same time, because smaller files survive shaky phone connections far more reliably.

Where the Form Has to Live

A file upload question only works if the form lives in your personal My Drive — putting it in a shared drive disables file upload entirely. This is the reason behind the most-searched complaint on the topic (“File upload is greyed out”), and it’s usually solved in one move: put the form back in My Drive, or rebuild it there, and the option comes back.

The trade-off is worth stating plainly, because it’s an organisational risk rather than a technical one. A form in My Drive is owned by one person. If that person leaves the organisation or their account is deleted, the form and the destination folder holding everyone’s uploaded files can go with them. Teams that collect files at any scale should decide deliberately who owns the form, keep a second admin with access to the folder, and export or move important files out of the upload folder rather than leaving them as the only copy.

Managing Upload Forms from Your iPhone

Forms for Google Drive is a native iOS app for building and managing Google Forms on iPhone and iPad, and its file upload support (a paid feature, with a 3-day free trial) is aimed squarely at the creator’s side of this workflow: adding file upload questions without wrestling the web editor on a small screen, and getting content into a form by taking a photo, choosing from your library, browsing a folder, or pasting from the clipboard, plus inserting math formulas when you’re building quiz-style forms.

The boundary matters more than the feature list, so here it is straight: the app does not remove the sign-in requirement for respondents. That’s Google’s rule, it applies to every form with an upload question, and no iOS app can bypass it — anyone telling you otherwise is selling something. What the app changes is your side of the work: building and editing the form, and reviewing what comes in.

For teachers running assignment hand-ins — the single most common use of file upload — our Google Forms for teachers on iPad and iPhone guide covers the classroom workflow around it, and when you need a clean record of who submitted what, our convert Google Forms responses to PDF guide handles the paperwork side from a phone.

Summary

Google Forms can collect files and photos through a File upload question, and you can add and configure one from an iPhone in Safari — but the feature comes with rules you have to design around rather than fight. Respondents must sign in to a Google account, always; on Workspace accounts the form also locks to your organisation. Files consume the form owner’s Drive storage, and a full Drive stops submissions cold. You get at most 10 files per question, a configurable size cap from 1 MB to 10 GB, file-type restrictions worth using, and the form must sit in My Drive — a shared drive greys the option out. On iOS specifically, the fix that saves the most time is the simplest: when a photo won’t upload from the library, use Take Photo or Save to Files first. Match the tool to the audience, and file upload is genuinely useful; expect it to work for people without Google accounts, and it never will.