Considering a Microsoft Forms alternative? Compare uploads first

Most complaints about Microsoft Forms start at one place: the upload question exists, but only inside the organization. Staff handover forms work, group forms work, and then someone adds customers to the mix and the file question is gone. That is an audience rule Microsoft sets deliberately. No setting inside the product will fix it, so the search that follows is usually for a different tool rather than a workaround.

Before comparing anything, name the actual requirement. If the intake will never accept files from outsiders, Microsoft Forms likely remains the right tool, and pretending otherwise wastes a week of setup for your team.

When Microsoft Forms is still the right answer

Keep it when three things are true. The audience is staff, because upload questions are offered only when the form is restricted to people in your organization or specific people from it. The attachments can include large items, because the native question allows up to ten files with per-file choices of 10 MB, 100 MB, or 1 GB. And the records should stay where IT already governs them, because individual-form uploads rest in the author's OneDrive and group-form uploads in the group's SharePoint site.

Internal handover forms, equipment requests, and staff surveys fit that profile every day. The Microsoft Forms greyed-out guide covers the audience settings and the editor-preview confusion that look like failures but are not.

What to compare once outsiders need to attach files

The comparison should be concrete, because vague feature lists hide the differences that actually break a rollout. Here is the same external intake run through three tools:

Read one row as a genuine reason to keep Microsoft Forms: the size allowance. Thunder Forms tops out at 12 MiB per file, which suits screenshots, documents, and scans comfortably and large video files not at all. If respondents must send video, keep the Microsoft route and work within its audience rules.

Read another row as the reason people leave: the first one. There is no audience switch that lets Microsoft Forms accept a file from your customer, and there is none on Google's side either, since the upload question keeps its own sign-in requirement even on a public form. The Google Forms disabled upload guide walks that side in detail. If most of your audience holds Google accounts and you mainly want a friendlier editor, the Google Forms alternative test starts with an import trial instead of a rebuild.

Move an external intake off Microsoft Forms

1. Write the requirement down before touching any tool: who responds, what they attach, where files must land, and who reviews them.
2. Rebuild the questions manually. Thunder Forms does not import Microsoft Forms, so copy the question text, choices, and required flags by hand. For a reporting intake, the Support Ticket template ships with a screenshot upload field already in place.
3. Connect a Google Drive destination to each upload field before the link leaves your desk. Files land in that folder as respondents submit them, and the file upload forms guide explains limits and access.
4. Test with somebody outside your organization, on a phone, with a file of the real type and size. Colleagues on your own accounts cannot stand in for the audience that caused the move.
5. Give reviewers a shared view. Sync responses to Google Sheets for a list where each row carries its upload links, or use the response table and CSV export when one person reviews alone.
6. Set a closing date or response limit so the new link stops when the request period ends, and keep the original Microsoft form available in parallel until the replacement has passed the test above.

Existing answers and attachments stay in Microsoft Forms even after you stop using it. Copy whatever reviewers need into the new system, and let your retention rules decide when to delete anything.