Comparisons between form builders usually go badly wrong in the first paragraph, because they treat three tools as three competitors bidding for the same job. In practice two of them arrive attached to software you already pay for, and the third is bought deliberately when those two have run out of road. The real question is rarely which is best. It is which of these you already have, and whether what you are building has outgrown it.
This comparison covers Jotform, Google Forms and Microsoft Forms across the things that actually decide the outcome: build speed, branding, conditional logic, payments, signatures, approvals, integrations, data handling and cost. It also covers the case none of them handle well, which is more common than any of the three would like to admit.
No winner is declared, because there is not one. There are four or five distinct jobs and a fairly clean allocation between them.
The Short Answer
| If this describes you | Start with |
|---|---|
| You need a survey, poll or sign-up sheet by lunchtime | Google Forms |
| Your organisation runs on Microsoft 365 and the form is internal | Microsoft Forms |
| The form must take payment, a signature or an approval | Jotform |
| The completed document is the point — signed, printed, filed | Fillable PDF Forms |
| You have outgrown a free tool but cannot say exactly how | Audit the form first, then decide |
That last row is not a joke. A significant share of migrations we are asked to carry out turn out to be unnecessary — the existing tool was capable, and the form was simply built badly.
What Each Tool Is Actually For
Google Forms
A free, fast, deliberately simple form builder tied to a Google account. Its design philosophy is that most forms are questionnaires, and it optimises ruthlessly for that. You can build something usable in ten minutes without reading any documentation, responses land in a linked spreadsheet, and collaboration works the way the rest of Google Workspace does. It has section-level branching, response validation, file uploads and quiz marking, and it stops fairly abruptly after that.
Microsoft Forms
The equivalent inside Microsoft 365. Similar simplicity, similar speed, similar limits — but with one decisive advantage in the right context: it lives inside your tenant. Responses stay under your organisation's Microsoft administration, results flow into Excel, identity is already handled for internal respondents, and Power Automate sits alongside it for workflow. If your organisation is a Microsoft organisation, that integration is worth more than a longer feature list elsewhere.
Jotform
A commercial form platform built on the assumption that a form is often part of a process rather than the whole of it. Field-level conditional logic, payment processing, e-signatures, approval routing, generated PDFs, extensive branding control and a large integration catalogue. It is more capable and, correspondingly, more work to configure well — capability you do not use is just complexity you are paying for.
Head to Head
| Capability | Google Forms | Microsoft Forms | Jotform |
|---|---|---|---|
| Time to build something simple | Fastest | Fastest | Moderate |
| Learning curve | None | None | Real, but manageable |
| Branding control | Header, colour, font | Theme and image | Full, including CSS |
| Conditional logic | Section-level | Section-level | Field-level |
| Calculations in the form | Via add-ons only | Limited | Built in |
| File uploads | Sign-in required | Sign-in required | Open to anyone |
| Take payment | No | No | Yes |
| E-signature | No | No | Yes |
| Approval routing | No | Via Power Automate | Built in |
| Formatted PDF per response | No | No | Yes |
| Results destination | Google Sheets | Excel | Built-in tables, plus export |
| Automation | Apps Script, add-ons | Power Automate | Native integrations |
| Embed on your own site | Basic iframe | Basic iframe | Seamless embed options |
| Submission limits | Effectively none | Generous per tenant | Capped by plan tier |
| Cost | Free with an account | Included in Microsoft 365 | Free tier, then paid plans |
Where Google Forms Wins
Speed and friction. For surveys, feedback, event sign-ups, internal polls, simple registrations and quizzes, it is very hard to beat and impossible to beat on setup time. The linked spreadsheet is genuinely powerful once you know what to do with it, collaboration is effortless, and there is no submission cap to plan around.
It also wins on adoption, which is underrated. Nobody needs training, nobody needs a licence, and a colleague can pick up a form you built and understand it immediately. We cover what it does well in detail in the complete Google Forms guide for small businesses.
Where it stops: no payments, no signatures, no approvals, no calculations without add-ons, limited branding, and file uploads that require the respondent to sign in to a Google account — which quietly rules the feature out for public-facing forms.
Where Microsoft Forms Wins
Context. If your organisation runs on Microsoft 365, an internal form built here inherits identity, permissions, administration and data governance from a tenant your IT team already controls. That is a compliance and procurement argument as much as a feature one, and in regulated or larger organisations it usually settles the matter without a feature comparison happening at all.
Results in Excel, integration with Teams for distribution, and Power Automate for workflow round it out. Power Automate deserves particular mention: it fills much of the approvals gap, so a Microsoft organisation can build routed processes without buying a third tool.
Where it stops: much the same place as Google Forms on the form itself — modest branding, section-level logic, no payments, no signatures. External respondents are workable but less natural than internal ones, and the polish available on a public-facing, customer-visible form is limited.
Where Jotform Wins
Everything that happens around the questions. Payments at the point of submission, a captured signature, an approval chain with a recorded decision, a formatted PDF of every response, field-level logic detailed enough to model a real process, and branding thorough enough that the form does not look like it came from somewhere else.
The two situations where it is not really a close call: taking money as part of a form, and producing a document from a submission. Neither free tool does either.
Where it stops: it costs money, the free tier caps monthly submissions, and it takes longer to build well. There is also a maintenance dimension people underestimate — elaborate conditional logic left undocumented becomes a form nobody in the organisation dares to modify a year later.
Where None of the Three Wins
All three are web forms. When the completed document is the deliverable — a signed agreement filed in a record, a consent form with governance-approved wording, an inspection sheet completed with no connection, anything that will be printed and kept — a fillable PDF form is the correct instrument, and no amount of feature comparison between the three changes that.
The distinction is simple enough to apply quickly: do you want the answers, or do you want the artefact? Web forms give you answers with a document as a by-product. PDF forms give you a document, with the answers extractable afterwards. We work through the trade-offs in Jotform vs Microsoft Forms vs fillable PDF forms and, from the other side, in Google Forms vs fillable PDF forms.
Cost, Honestly
The free options are not free
Google Forms is free with any Google account. Microsoft Forms is included with Microsoft 365, which you are already paying for. Both are genuinely no additional cost — but the price appears elsewhere, in workarounds. Chasing payments separately, retyping submissions into another system, emailing about approvals, and reconciling a spreadsheet by hand all consume staff time that nobody attributes to the form.
Jotform's model
A free tier with monthly submission and storage caps, then paid plans with progressively higher limits and more features. Because pricing and plan boundaries change, check the current plans directly rather than trusting any article — including this one — and confirm specifically which tier includes the features you are relying on, since payments, signature volume and regulated-data configurations do not all sit on the same level.
The cost nobody counts
Setup and maintenance. A simple form is a lunchtime. A form with logic, payment, an approval chain and a designed PDF output is a project, because you are encoding how the organisation makes a decision — often for the first time in writing. Budget for that, and for someone owning the form afterwards.
Data, Security and Compliance
All three are established platforms with encryption in transit and at rest, access controls and export capability. The differences that matter in practice are administrative rather than technical.
Microsoft Forms keeps data within a tenant your organisation administers, which is frequently the deciding factor for internal forms in regulated sectors. Google Forms sits within your Workspace administration on the same principle. Jotform offers regional data storage options, encrypted forms and configurations aimed at regulated sectors including healthcare — but several sit on specific paid plans and none are on by default, so confirm rather than assume.
Whichever you choose, the obligations are yours, not the platform's. State on the form what the data is used for and who sees it, add a consent checkbox where you intend to market afterwards, review who has access to the responses when staff leave, collect only what you use, and agree how long submissions are kept.
Choosing by Organisation Type
Small businesses and consultants
Google Forms for enquiries and feedback. Jotform when a deposit, a signed engagement letter or a client-facing document enters the process — which for most consultancies is at the point of winning the work, not before.
HR departments
Microsoft Forms if the organisation is a Microsoft organisation, particularly with Power Automate handling approvals. Jotform where recruitment involves public applicants, uploads and offer documents. Contracts and policy sign-off remain PDF documents either way.
Healthcare providers
Jotform for appointment requests and patient-facing forms where regulated-data configuration and branching by presenting complaint matter. Clinical records, consent and anything with governed wording stay as fillable PDF forms.
Schools and training providers
Google Forms is ubiquitous in education and adequate for most internal collection. Jotform earns its place where fees are taken at registration, since it removes the monthly reconciliation of transfers against names. Admission packs remain PDF documents.
NGOs and membership organisations
Google Forms for surveys and monitoring where budget is tight. Jotform for membership renewal with subscription payment, donations, and grant applications with supporting uploads.
Legal and professional services
Jotform for client intake, conflict checks and engagement letters with signature. Anything that becomes part of the file is a document, not a submission.
Migrating Between Them
Moving a form between platforms is rarely difficult; moving the process around it is. Before migrating, check three things: whether historic responses need to come across (usually possible by export and import), whether anything is linked to the existing form — dashboards, scripts, automations, embedded links on your site — and whether anyone still uses the old link, because a form nobody has retired keeps collecting responses nobody reads.
A migration is also the natural moment to delete the fields nobody uses, document the logic properly, and rewrite the confirmation message. Rebuilding a bad form faithfully on a better platform is the most common way a migration disappoints.
Mistakes People Make When Choosing
- Choosing on feature count rather than on the one capability that actually decides it.
- Paying for capability you never configure, which is complexity with a monthly cost.
- Assuming the free tool cannot do it — very often it can, and the form was just built poorly.
- Ignoring what your organisation already runs, and fighting procurement for a tool you did not need.
- Forgetting the file-upload sign-in requirement on both free tools until a public form fails.
- Treating a document requirement as a form requirement, and discovering the gap at signature stage.
- Not checking which plan tier includes the specific feature the decision rests on.
- Migrating the same bad form to a better platform and expecting different results.
A Decision Checklist
- Does the form need to take payment? If yes, Jotform.
- Does it need a signature that stands up? Jotform, or a PDF form.
- Does a decision get made on each submission? Approvals — Jotform, or Power Automate.
- Is the completed document the point? A fillable PDF form.
- Is it internal and are you a Microsoft organisation? Microsoft Forms.
- Is it a survey or sign-up with no money attached? Google Forms.
- Will public respondents upload files? Rules out both free tools.
- Does it need to look like part of your website? Jotform.
- Are there data residency or sector rules? Check the specific plan, not the marketing page.
- Who owns and reviews it after launch? Answer this before building.
Which Form Builder Is Right for You?
| Your need | Best choice |
|---|---|
| Simple surveys and quick internal polls | Google Forms |
| Forms inside a Microsoft 365 workflow | Microsoft Forms |
| Advanced forms, payments and automation | Jotform |
| Offline, printable or interactive documents | Fillable PDF Forms |
| Public forms with document uploads | Jotform |
| Signed agreements filed as documents | Fillable PDF Forms |
| Correcting an existing PDF document | PDF Editing |
| A branded proposal or contract template | Microsoft Word Formatting |
| Tracking, reporting and calculation | Excel Templates |
| Headers, brand assets and print-ready design | Graphic Design |
Summary
Google Forms is the right default for surveys, sign-ups and anything that needs to exist this afternoon. Microsoft Forms is the right default for internal forms in a Microsoft organisation, where tenant administration and Power Automate matter more than the feature list. Jotform is what you buy when a form has to take money, capture a signature, route an approval or produce a document — and it is worth its cost precisely and only when one of those is true.
Where the completed document itself is the deliverable, none of the three is the answer and a fillable PDF form is. That case is more common than comparison articles suggest, particularly in healthcare, education, legal work and anywhere a signature ends up in a file.
It is also worth stating the opposite view fairly: some organisations deliberately standardise on a single platform even where it is not the best fit for every form, because one tool that everyone understands, administers and supports beats three tools chosen optimally and maintained by nobody. If your constraint is capacity rather than capability, that is a defensible answer. Most organisations, though, land on two — a free tool for collection and one serious instrument for the forms that carry money, signatures or documents. If you are unsure which side of that line your form sits on, describe what it has to do and you will get a straight recommendation, including the one that costs you nothing.
