Resources · 11 Sept 2026

Every Google Forms alternative meters the response

Most guides to Google Forms alternatives compare the form. The operators who actually switched talk about something else: the response limit on the tool they moved to, and the campaign that stopped in the middle.

See what we have built

How to create a Google Form, and where it runs out

If you came here to make a form, make it in Google Forms. It's free, it takes four minutes, nobody needs an account to fill it in, and for most of what people use forms for that is the end of the decision. Reaching for something heavier before you have a reason is how people end up paying for a tool they use twice.

So here is the four-minute version, with the ceiling marked on each step. Every one of them has a point where it stops, and knowing where in advance beats finding out on day two of a launch.

#What you doWhere it stops
1Open a blank form and type your questions.Nothing stops here. This part really is four minutes, and it is the part every competitor is also good at.
2Set a type for each question, and turn on response validation.Validation is the only logic there is. Everyone sees the same questions in the same order, whatever they answer.
3Open Settings and decide about email addresses.There is no third option. Collect them and you know who answered. Leave it off and you do not.
4Decide whether one person gets one answer.It needs the switch above. You cannot count someone once without also asking who they are.
5Press Send, then read the Responses tab or link a spreadsheet.A spreadsheet is the end of the line. Nothing downstream knows a response arrived unless you tell it.
6If you accept file uploads, watch your Drive.They land in your storage and count against it, and the form can close itself when that runs out.

Steps three and four are one decision wearing two labels, and it is the decision the whole rest of this page follows from. Collecting email addresses is what makes limiting responses possible, so a form is either anonymous and unlimited or identified and controlled. There is no setting for both.

None of that is a criticism of the tool. It's a free product that does the common job well, and if your job is the common job you can stop reading here.

The rest of this piece is for the cases where one of those ceilings arrives early, because that's when people go looking for an alternative, and what they find is not quite what they expected.

The two switches that decide everything elseSettingsRESPONSESCollect email addressesOff by default. Nobody has to sign in to answer.Do not collectLimit to 1 responseNeeds a respondent you can recognise.Turning the second one on turns the first one on. There is no third option.A simplified recreation. The real panel carries more switches; these two decide what the rest of this page is about.

What people are actually switching away from

Google Forms is the default because it's free, it takes four minutes, and nobody has to make an account to answer it. The complaints are specific rather than general. They cluster in five places.

File uploads. An illustrator taking commissions described a form that shut itself after a few hours because submissions hit the storage ceiling she'd set, and said raising it again didn't look worth the trouble. A second creator running a giveaway found a default cap on how many images one person could submit, and only found out when entries started bouncing.

Limiting responses without collecting identity. This one is structural. To accept one response per person, the form has to collect email addresses. An operator running a public sign-up put the objection plainly: people won't hand their email to a stranger just to be counted once.

Spam. A voice-acting organiser closed a casting form after the first thirty responses because bots had found it. Nothing about the form was wrong. It was just open, and open means unprotected.

No running total and no payment. A mail-order seller explained the trade in one line: the free form has no cap on orders, but it also can't show a buyer what their order comes to. Anyone selling through a form ends up doing the arithmetic by hand, then chasing payment separately.

No conditional logic or integrations. Everything looks the same to everybody, and the answers land in a sheet instead of in the system that needs them.

Every one of those is real. None of them is why people come back.

The response cap nobody mentions until you hit it

The guides all say roughly the same thing. The form looks dated, the logic is thin, the design is generic. All true, and all about the product rather than about what happens when you actually move.

What operators describe on the way back is a meter. A fund opening a closed beta said its form tool stopped at a hundred registrations, so the sign-up moved to Google Forms to keep the round open through the weekend. A designer running a pre-order hit their limit under demand and posted a replacement link. A self-storage operator, in a thread about pricing, said they'd used one of the polished tools for a while, cancelled, and gone to Google Forms. A seller running a mail order said they were on the free form this time because the alternative had a limit.

The tools people move to meter the exact thing that makes a form worth having, which is the response.

The numbers aren't hidden. Typeform's own pricing page, read on 11 September 2026, lists its cheapest paid plan, Basic, at 25 EUR a month including 100 responses a month, with a maximum of 750. The next plan up is 49 EUR for 1,000. So a form that's free and uncapped gets compared against one that costs 25 EUR and stops at 100, and the comparison articles rarely put those two facts next to each other.

Price isn't really the problem. The ceiling arrives mid-campaign, and nobody budgets for a cap they meet on day two of a launch.

Some of the returns are about reliability rather than volume. Two group-order organisers, four years apart, described rolling back to the free form mid-order after the tool they'd moved to lost their product list. One reported refunding buyers who had already paid, because the orders never reached the system at all.

How to choose, and what we did not rank on

A ranked list is only useful if the criteria are stated first, so here are ours.

  • What happens at volume. Not the headline price. The response allowance at the tier you'd actually buy, and what happens on the response after the last one.
  • Whether the tool knows who submitted. Anonymous is a feature for a public survey and a defect for anything you have to follow up.
  • Where the answers land. A spreadsheet is a destination. A record the rest of the business can read is a different thing entirely.
  • What it costs to leave. Forms accumulate. The question is whether the responses come with you.
  • What else the subscription buys. A form tool is rarely the only thing a business is paying for, and the bill is the stack, not the line item.

We didn't rank on design, because everything in this category looks fine now, and we didn't rank on question types, because those differences stopped mattering years ago.

One disclosure, since it changes how you should read the rest. Clawnify is a platform for building the tools themselves, so the last group below is the one we're in. We publish open-source alternatives to specific products and run them as apps in your own workspace: a HubSpot alternative, a Clay alternative, a Canva alternative, a DocSend alternative, a scheduling tool, a field service tool. A form builder is the same shape of thing and it isn't in that catalogue yet. You wouldn't be prompting it into existence yourself either: you ask for it, and an agent builds it against the same patterns the published ones were built from. The last section says plainly when the established tools are still the better answer.

Four kinds of answer, not one ranking

The tools people name fall into four groups, and the groups matter more than the order inside them.

The polished form builders

Typeform, Jotform, Tally and Fillout. One question at a time, conditional logic, a form that looks designed. These are what people move to, and the group where the response meter lives. A marketer who switched named her reasons precisely: the conditional logic, and the fact that it connected to the other systems she used. That's an honest account of what you gain.

The free and uncapped default

Google Forms, with Microsoft Forms alongside it. Unlimited responses, no account needed to fill one in, answers in a spreadsheet. Weak on logic, weak on appearance, no payment, and anonymous unless you ask for an email. It's the fallback for a reason. It doesn't stop.

Form plus payment

This group exists because selling through a form is common and no plain form does it. An operator taking orders described building a form page with payment attached, and said the point was to stop buyers sending their address by direct message. Anyone running a pre-order or a paid sign-up is in this group whether they planned to be or not.

Owning the tool instead of renting it

The fourth group isn't a product you sign up for. It's the form tool as software you run, alongside the other tools you run, so responses land in your own database next to your own customer records and nobody meters them. Self-hosted options have always existed here, and they were always a project: someone had to build and maintain the thing.

What changed is who does that. You describe the tool you want and an agent builds it, working from the patterns of tools it has already built. The part that used to be a quarter of engineering time is now a conversation, which is why this group is worth listing next to three products you can buy this afternoon.

Two things follow from owning the code that don't follow from renting the product. The feature you want is a change, not a plan. Conditional routing, a field type nobody offers, a rule specific to how you work: in a subscription those live behind a tier, on a roadmap, or nowhere. In code they're an edit. A surprising amount of what sits behind a premium plan is an afternoon of work once you can open the file.

And a new tool arrives knowing about the old ones. Built in the same workspace, it can already read the apps that are there, use the integrations already connected, be driven by the agents already running, and follow whatever brand the rest of your tools follow. Compare that to a form product you connect to a CRM you connect to an invoicing tool, where every join is glue somebody maintains and every tool holds its own half-copy of the same customer.

The gap none of them fill, and when a plain builder still wins

Line the four groups up against the two things people ask for and the pattern is hard to miss.

Google Forms is unlimited and anonymous. Take ten thousand responses for nothing, and you won't know who sent any of them unless you ask, which is the request people say respondents refuse. The polished builders are identified and capped. They'll recognise a respondent, route on the answer and push it onward, and they price by the response.

Nobody selling a form subscription offers unlimited and identified, and the reason is structural rather than stubborn. Metering responses is how the business works, and identity means collecting an email address, which is a question you have to ask.

Software you run yourself has neither constraint. There's no meter because nobody is charging per response, and there's no identity question when the person filling it in has already signed in. The submission arrives attached to a customer, a job or an account. The one-response rule enforces itself. The bots that found the open form never get that far.

A consultant described the version of this he wanted for client intake: rather than a static form, a flow that asks the right follow-up based on what was answered, so that by the time he opened the submission he knew the prospect's stack, their timeline and their budget. More question types would never have got him that.

The arithmetic that actually decides it

A form tool is almost never the only subscription on the bill. It sits next to a CRM, a scheduler, a document tool and an invoicing tool, each one metered on something different, each one holding a slice of the same customer.

That is the case for owning them instead. Once you're already running your CRM as your own software, adding a form tool is another app in the same workspace rather than another monthly line item, and the responses land in the database the CRM is already using. The first one has to justify itself. The tenth is close to free.

When a subscription is still the right answer

Often, honestly.

If the form is public and the respondents are strangers, you don't want identity and shouldn't build for it. A contact form, a conference call for papers, an anonymous survey, a school sign-up: that's what Google Forms and the polished builders are for. If you send one form a quarter, the free one is correct and this comparison isn't worth your afternoon. And if a form is genuinely the only tool you need, one subscription for one tool is the simplest thing that works.

Owning software is also owning it. Nobody else is on call for it, and a tool you never change is a tool you were right to rent.

The case changes when three things are true together. The people filling it in are already your customers, clients or staff. The answers have to reach something other than a spreadsheet. And you are already paying for three or four other tools that hold pieces of the same customer.

At that point the form is the last four minutes of the build. What you're actually shopping for is everything behind it.

Only software you run yourself does bothGoogle Formsthe free defaultUnlimited responsesyesKnows who submittednoTypeform, JotformTally, FilloutUnlimited responsesnoKnows who submittedyesSoftware you runyour app, your databaseUnlimited responsesyesKnows who submittedyesMetering responses is how a form subscription works, which is why the third column is not one