Somebody opens a sign up form for a workshop with 30 places. Two weeks later it has 46 responses, the deadline passed on Friday and nobody remembered to switch it off, and now the awkward part of the job is writing to 16 people who believe they have a place. The search that follows is usually some version of formlimiter for a google form, and the advice it returns was largely written before Google shipped this as a setting.
That is the thing worth knowing first. The situation has changed recently enough that most of the guidance still in circulation is solving a problem the product now solves itself.
What "formLimiter" refers to now
There is no longer a single canonical add on by that name. Searching the Google Workspace Marketplace for formlimiter today returns several separately published tools with closely similar names and overlapping descriptions.
The three most installed, as the Marketplace lists them today, are LIMIT IT: Form Response Limiter from AddonForge, rated 4.7 with more than 6 million installs and 1,549 reviews, with a listing updated on September 25, 2026; Form Response Limit, Form Limiter, FormLimiter from Everest Web Deals, rated 4.8 with more than 2 million installs; and Form Limiter: Response Limit and Choice Eliminator from Skyfield, rated 4.9 with more than 1 million installs. The same publishers also list timer variants aimed at quizzes.
This matters for a practical reason rather than a pedantic one. A colleague who says "just install formLimiter" is naming a category, not a product, and the thing you install after that search is a decision about which third party gets access to your account. Google also notes on those listing pages that it does not verify reviews or ratings, so the star figures are a signal about popularity rather than an audit.
Anyone following a tutorial written a few years ago should also expect the screenshots not to match. The Google Forms interface has changed, and so has the set of add ons available.
The setting that arrived in January 2026
On January 12, 2026 Google launched the ability to close a form automatically, and described the gap it filled in plain terms: previously, form creators had to stop a form from accepting new responses manually. With the launch, form owners and editors can set a specific date and time to close the form, or set a number of responses that triggers the form to close automatically.
Three details about the rollout are worth knowing, because they explain why a colleague might not see it.
It is available to all Google Workspace customers, to Workspace Individual subscribers, and to people using personal Google accounts. So this is not a paid feature and not a business only feature.
It is off by default, and it is switched on by the form creator after a form has been published. A form still in its unpublished state has nothing to close.
There is no admin control for it, which means an organization cannot turn it on centrally or turn it off centrally. Each form is configured by whoever owns it.
Google's help documentation describes the controls as sitting with the publishing status of a form, alongside the manual switch for accepting responses, with an option to set a close date or response limit and to edit the message that responders see once the form is closed. The default message is that the form is no longer accepting responses, and it can be replaced with something more useful, such as a note about when the next round opens.
What a response limit actually promises
This is the part that a tutorial will not tell you and that matters most when real capacity is at stake.
Google documents two constraints on the response limit. The first is that if the form already has responses, the number entered has to be greater than the number already received. So the setting cannot be used after the fact to cap a form that has already overrun. It is a control you set before the rush, not a rescue after it.
The second is more consequential. Google states that if multiple people respond at the exact same time, the form accepts responses regardless of the response limit. A cap of 30 is therefore a cap of approximately 30. For a research survey where the number is a target, that is irrelevant. For a workshop with 30 chairs, a ticketed event, or anything where the count is a promise to named people, it means the number still has to be reconciled after the form closes.
A close date behaves more predictably, because time is not contended in the same way. If only one of the two rules can be trusted to the unit, it is the date.
There is a further distinction between the two ways of switching a form off. Turning off accepting responses leaves the form published, so the link still resolves and anyone who follows it reads the closed message you wrote. Unpublishing the form is a stronger action, since Google documents that responses cannot be accepted in an unpublished form at all and that responders with the link cannot access it. For a deadline that people were emailed about, the first behavior is the kinder one, because a link that explains itself generates far fewer questions than a link that appears to be broken.
There is also a third, quieter way to stop a form, which is worth knowing because it solves a different problem. Responder access itself can carry an expiration date, set when the form is shared, and removed again later. That closes off access for the people invited rather than closing the form for everybody.
When an add on still earns its place
The native setting covers the common case, which is closing a form. Several things the add ons offer are not part of it.
Opening a form on a schedule is the clearest example. The AddonForge listing describes a start date as well as an end date, so that a form can be prepared well in advance and go live at a chosen hour without anyone present. Registration that opens at nine on Monday morning is a real requirement, and the built in controls act on a published form rather than publishing one for you.
Notifications are another. That listing describes an email when a form opens at its start date, when it closes at its end date, and when it closes because the response limit was reached. Knowing that a form hit its cap at 11:40 on Tuesday is operationally different from discovering it on Thursday.
The same listing also describes QR code sharing in a chosen size and states that rules run on Google's servers rather than in a browser, so a tab does not need to stay open. The timer variants published by the same companies aim at a different job again: a per respondent countdown for a quiz rather than a form wide deadline.
| Built in close settings | Third party add on | |
|---|---|---|
| Close on a date and time | Yes, since January 12, 2026 | Yes |
| Close after a number of responses | Yes, with simultaneous submissions accepted regardless | Yes |
| Open a form on a schedule | Not part of it | Described on the AddonForge listing |
| Email when the form opens or closes | Not part of it | Described on the AddonForge listing |
| Access to your account required | None beyond the form itself | Authorization, detailed below |
| Availability | All Workspace customers, Workspace Individual and personal accounts | Marketplace listing terms, with a free of charge trial on the AddonForge listing |
What an add on asks for in return
An add on is not a setting. It is a third party application authorized against your Google account, and the Marketplace publishes exactly what each one requests. It is worth reading the list before installing rather than clicking past it.
The AddonForge listing states that the add on will need access to view and manage forms that the application has been installed in; to see, edit, create and delete all your Google Sheets spreadsheets; to display and run third party web content in prompts and sidebars inside Google applications; to connect to an external service; to run when you are not present; to send email as you; to see your primary Google Account email address; and to see your personal information, including anything made publicly available.
None of that is unusual for an add on that has to run on a schedule and send you a message, and every item has an obvious purpose. It is still a wider grant than most people expect from a tool whose job is to switch a form off. Two items deserve deliberate thought in particular: access to all of your Sheets spreadsheets rather than the one linked to this form, and the ability to send email as you.
The practical guidance is ordinary and worth stating anyway. If the built in close date and response limit do what you need, they cost nothing in access. If a start date or an open and close notification is genuinely required, choose one add on, read its permissions, and remove it when the project it was installed for is over.
What closing a form does not fix
Closing a form on time solves one problem cleanly. It does not touch the problem that made the deadline stressful in the first place.
When a form closes at 30 responses, there are usually people behind those 30 who should be on a waitlist, and the form has no idea which of the 30 have actually been confirmed. Nothing in a Google Form records that response 12 was withdrawn, that response 19 never replied to a confirmation, or that response 27 is being handled by a specific colleague. Those facts live in a column somebody added to the linked spreadsheet, or in an email thread nobody else can see.
A response limit caps arrivals, not commitments, which is why the count that closed the form is rarely the count that ends up attending. The gap between the two is handled by hand on almost every team, and it is the work that actually consumes the week after a deadline. A form tool built for the work after submit keeps the owner, the status and the reply attached to each response, so a cancellation frees a place and the next person on the list can be moved up without anyone recounting a spreadsheet. Whether that matters depends on the kind of intake being run, and it is worth deciding before the next cycle rather than during it.
What to change first
Before installing anything, open your form and look for the close date and response limit options on the published form, since the feature rolled out to every account type in January 2026 and switches on per form. If it is there, use the date rather than relying on the count, and confirm the final number by hand afterwards. If the harder problem is that the count closing the form and the count of confirmed people are two different numbers, the thing to change is where responses are handled, which is what Halict is built around.
Q1. Do you still need an add on to limit responses to a Google Form?
Usually not. Since January 12, 2026 Google Forms has built in options to close a form on a specific date and time or after a set number of responses, available to Workspace customers, Workspace Individual subscribers and personal Google accounts. An add on is still the option if you need a form to open on a schedule, or to be emailed when the form opens or closes.
Q2. Will a response limit stop the form at exactly that number?
Not guaranteed. Google states that if multiple people respond at the exact same time, the form accepts responses regardless of the response limit. It is dependable enough for a soft cap and not dependable enough for fixed seating, so the final count should be checked after the form closes.
Q3. Can the limit be set after a form has already gone over?
No. Google documents that if the form already has responses, the number entered must be greater than the number already received. A form that has overrun has to be closed manually by turning off accepting responses, and the excess dealt with separately.
Q4. Which formLimiter add on is the original one?
There is no single original still listed under that name. A Marketplace search for formlimiter returns several separately published tools, the most installed being LIMIT IT from AddonForge, a Form Response Limit tool from Everest Web Deals, and a Form Limiter from Skyfield. Google also notes that it does not verify the reviews or ratings shown on those listings.
Q5. What access does a form limiter add on need?
More than the form. The AddonForge listing, for example, requests permission to manage the forms it is installed in, to see, edit, create and delete all of your Google Sheets spreadsheets, to connect to an external service, to run when you are not present, and to send email as you. Each item has a purpose, and the list is worth reading before installing.