
Forms & Surveys
Online form builders for business
Compare Google Forms, Typeform and Microsoft Forms for business intake, branching, uploads, access and response limits.
Choose an online form builder around the job the form must do: collect a simple enquiry, route respondents through different questions, accept files, or feed a business workflow. Fit depends on who must respond, what data you can ask them to provide, who can access the answers, and what happens as volume grows.
A polished editor matters less if the published form blocks a key respondent.
Start with the submission journey
Write a one-page brief before comparing products. Identify intended respondents, required fields and files, any branching rule, where answers go, who owns follow-up, and expected response volume.
Mark the fields that are genuinely required. For an external customer intake form, a sign-in requirement is a major selection constraint; for an internal staff form, it may be acceptable.
Build one representative sample in each shortlisted product. Test a normal answer, an invalid answer, an accepted file and a rejected file. Follow every branch to the confirmation screen.
Compare three plausible starting points
Google Forms
Suitable when: A team needs a straightforward survey or intake form and already works with Google tools.
Decision point: If you need many field-level conditions, sketch the full path before choosing it. Check the published form's sharing settings.
Typeform
Suitable when: The respondent journey needs tailored paths.
Decision point: Map the whole account's forecast volume and confirm current plan entitlements before committing to a high-volume public form.
Microsoft Forms
Suitable when: A Microsoft 365 team needs an internal form, especially where organisation access is desirable. Microsoft documents branching and file-upload questions for certain organisation-restricted responder settings.
Decision point: Microsoft says file upload is available only when responses are limited to people in the organisation or specified people in it. That rules it out for a public customer upload form under that configuration.
Branches only go forward to later questions or the end, so order a complex decision tree carefully. Verify the relevant contract instead of assuming one published maximum applies to every user.
For an organisation-restricted upload form, Microsoft Forms allows a maximum of 10 files per question and per-file size limits of 10 MB, 100 MB or 1 GB. Microsoft points teams seeking more advanced branding, question types and data analysis to Dynamics 365 Customer Voice.
Feature comparison: Google Forms, Typeform, Microsoft Forms
- Branching logicYes (Google), Yes (Typeform), Limited (Microsoft)
- File uploadsYes (Google), Yes (Typeform), Organisation-restricted only (Microsoft)
- Maximum file size (Microsoft)10 MB, 100 MB or 1 GB (depending on org settings)
- Max files per question (Microsoft)10
- Public form accessYes (Google, Typeform), No (Microsoft – unless specified users)
- Response limitsVaries by plan (Typeform); no public limit noted (Google); governed by organisation policy (Microsoft)
Compare the hidden costs of a form
The subscription is one cost only. Count monthly submissions across every form, file storage, extra users, integration or automation needs, and export or reconciliation work. Ask what happens at a limit: does the form close, are responses delayed, or does the bill change?
Recheck the in-product notice and current rules before planning a large intake.
Review uploaded-file handling separately. Find out who can open files, where they are stored, what a respondent must do to upload, and how files are deleted or retained.
A generic “supports uploads” check misses these practical constraints. For public intake, test the process with a respondent who has no account in your organisation.
Key response and storage limits for business forms
- Max file size (Microsoft Forms)
- 10 MB, 100 MB or 1 GB
- Max files per question (Microsoft)
- 10
- Public form submission access
- Restricted to signed-in users (Microsoft)
- Response export options
- CSV, Excel, Google Sheets (Google), Excel (Microsoft), CSV (Typeform)
Decide with a short trial
Use a representative form and a written pass/fail list: respondent access, branching, validation, upload permissions, submission confirmation, export and high-volume behaviour.
Invite a colleague unfamiliar with the form to submit it on a phone. Ask them to deliberately make an error and describe what the message tells them to fix.
Choose the product that completes the full journey with manageable limits. Document any condition that could change with a plan or policy update and recheck it before launch.
Assign someone to monitor failed submissions and response volume.
Pre-launch form testing checklist
- Respondent access (public/internal)Test with non-logged-in user if public
- Branching logic flowVerify all paths reach confirmation screen
- File upload validationTest valid and invalid file types/sizes
- Submission confirmation messageEnsure clear success feedback is shown
- High-volume behaviourCheck for throttling or failure at scale
In this guide
- Comparing conditional fields in form productsCompare conditional fields in form products by mapping and testing the exact respondent paths your form needs.
- Evaluating file-upload permissionsEvaluate form file uploads by checking respondent sign-in, staff access, storage, restrictions and failure messages.
- Testing error handling on a submitted formTest form errors and success messages with invalid entries, conditional fields, uploads and real respondent access.
- Reviewing form builder costs at higher response volumesPlan form builder costs around account-wide volume, per-form limits, busy periods and the consequence of a closed form.



