How to limit responses in Google Forms: per option, in total, and by date
Google Forms has no built-in way to limit responses. You can force one response per person (which requires a Google sign-in) and you can flip the form to stop accepting responses by hand. That is the whole native toolkit. Everything people actually ask for, a cap per answer, a total cap, a close date, needs an add-on, and the add-ons differ in one way that matters a lot when a form is popular.
This guide covers the four kinds of limit, which tool does each, and the one trap to know about before you trust any of them with a sign-up that fills in minutes.
The four limits people mean by "limit responses"
When someone types "limit responses google form" they usually want one of these:
- One response per person. Nobody signs up twice.
- A total cap. Close the form after 50 responses.
- A date or time. Open Monday 9:00, close Friday 18:00.
- A cap per answer. Pottery has 12 seats, Painting has 8, and a full option should disappear.
The first one is native. The other three are not, and the fourth is the one that causes the most trouble, because it is the one where timing matters.
1. One response per person (native)
Open the form, go to Settings, and turn on Limit to 1 response. Google then requires respondents to sign in with a Google account, which is fine inside a school or company and annoying for the general public. If your audience may not have Google accounts, leave it off and turn on Collect email addresses instead. You lose the hard block, but you can see duplicates in the responses, and some add-ons use that email to replace a person's earlier answer with the new one instead of counting both.
2. A total response cap
There is no native cap. You get a notification email per response if you want, and a switch to stop accepting responses. People do run forms this way, watching the count and flipping the switch at 50, and it works for a slow form. It does not work for anything that fills fast or overnight.
Add-ons that close the form at a number: Form Limiter by Skyfield, CAPY, the original formLimiter, and Form Slots. One honest note that applies to every tool, including ours: a total cap is checked after a response arrives, so the form can only close once the 50th submission exists. If 53 people press Submit in the same minute, a couple of extra responses land before the form closes. For a total cap that is usually acceptable. For a cap per seat it is not, which is the next section.
3. Open and close on a date
Also not native. Scheduling add-ons exist on their own and most limiter add-ons bundle a close date. Two details worth checking before you pick one:
- Granularity. Some schedulers run on an hourly trigger, so "close at 18:00" can happen anywhere up to an hour later. Skyfield's documentation describes a one-hour window. Form Slots runs its schedule on a server job, so the close lands within a few minutes of the time you set.
- Open time, not only close time. If a sign-up is competitive, opening the form at a fixed moment is what makes it fair. Few tools offer a scheduled open. Form Slots does, with a custom message shown while the form is closed.
4. A limit per answer (the one that bites)
This is the sign-up sheet case: a question with one option per slot, each with a capacity, and full options vanishing so nobody picks them. Google calls nothing in the product by this name, so people search for "choice eliminator", "choice limiter", "limit choices" and "option limit". They all mean the same thing.
Here is how almost every add-on in this category works, and why it occasionally fails. The add-on installs a Google Forms trigger that runs after a response is submitted. The trigger counts responses for each option and, if one reached its limit, edits the form to remove that option. On a quiet form this is fine. On a busy one, the sequence looks like this: 9:00:00 the form opens, 9:00:04 the twelfth person books Pottery, 9:00:05 the trigger starts, 9:00:06 two more people submit Pottery because the option was still on the form, 9:00:09 the trigger removes it. You now have 14 bookings for 12 seats and an awkward email to write. Reviews of the popular limiters mention "one or two over" regularly, and the maker of the oldest one describes it as suitable for light use.
The fix is to decide the booking before it is confirmed, on a server, one at a time per form, so the twelfth seat can only be granted once. That is what Form Slots does. The form, the link and the QR code stay exactly as Google gives them to you. The difference is where the decision happens.
Setting up a per-option limit with Form Slots
- Install Form Slots from the Google Workspace Marketplace and open your form.
- Click the Add-ons (puzzle) icon, then Form Slots, then Configure slots.
- Pick the multiple-choice, dropdown or checkbox question that holds the slots.
- Type a capacity next to each option, or use "Set all slots to" once.
- Turn on the waitlist if you want latecomers queued instead of turned away. This needs Collect email addresses on in the form's settings.
- Click Save & activate. Share the form as usual.
When an option fills, it is removed from the live form, usually within a minute. If a response is deleted or you raise the number, it comes back. People on the waitlist move up in arrival order and get an email, without you doing anything. "Go to section based on answer" routing keeps working while an option is hidden, which is a known breaking point for other tools.
Which tool for which limit
| Need | Native Google Forms | Trigger-based add-ons (CAPY, Skyfield, Everest, Choice Eliminator family) | Form Slots |
|---|---|---|---|
| One response per person | Yes, with Google sign-in | Same native setting | Same native setting, plus: with email collection on, a second answer replaces the first instead of taking two seats |
| Total cap | Manual switch only | Yes (closes after the Nth response lands) | Yes, same limitation, with a custom closed message |
| Close on a date | No | Yes, often hourly granularity | Yes, open and close, minute-level |
| Cap per answer | No | Yes, checked after the response is saved, so busy forms overbook | Yes, decided server-side before confirming, no overbooking |
| Waitlist with automatic promotion | No | No | Yes, with emails to the respondent |
| What it can access | n/a | Varies: some ask for all your Sheets and all your forms | Only the form it is installed in; a Sheet is created only on reset |
| Price | Free | Free tiers with paid upgrades | Free for one live form; Pro $6/month or $49/year |
If you only need a total cap on a slow form, any of the trigger-based tools is fine and Skyfield's is the cleanest about permissions. If you need a cap per answer on anything that fills fast, read the comparison of the five choice eliminator add-ons before choosing, and this troubleshooting guide if you already have one and it is letting people through.
Two limits people confuse with these
"Google form time limit" usually means a countdown for a quiz, not a close date. That is a different kind of add-on (quiz timers) and nothing in this guide applies to it. "Character limit" and "file upload limit" are per-question validation settings inside the form itself, under the three-dot menu of a question, and need no add-on.
A fair launch, in practice
For a sign-up that will fill in minutes, the limits are only half of it. Set a scheduled open time so everyone starts together, write the rule in the form description ("first come first served, 12 seats per session"), keep email collection on so the waitlist works, and put the QR code where people will be at that moment. There is a longer walkthrough in how to run a first-come-first-served sign-up in Google Forms, and a template-style guide in how to make a sign-up sheet in Google Forms.
Questions people ask
Can Google Forms limit the number of responses?
Not on its own. Google Forms only offers Limit to 1 response (which forces a Google sign-in) and a manual Accepting responses switch. Capping the total, closing on a date, or limiting each answer all need an add-on.
How do I limit each option in a Google Form?
Install a choice limiter add-on. Open the form, pick the multiple-choice, dropdown or checkbox question, give each option a capacity, and save. Full options are removed from the live form. Form Slots does this with a server-side check so two people cannot take the last seat.
How do I close a Google Form after 100 responses?
Use an add-on with a total response limit. Form Slots, Skyfield Form Limiter and CAPY all have one. Note that any tool can only close the form after the 100th response arrives, so a burst of submissions can land one or two extra before the form closes.
How do I make a Google Form close on a date?
Google Forms has no scheduled close. Add-ons do it: set a close date and time and the form stops accepting responses then. Form Slots also lets you set an open time, so a sign-up starts for everyone at the same moment.
Why does my limiter let a few extra responses through?
Most limiter add-ons run on a Google Forms trigger that fires after the response is already saved. On a busy form, several responses arrive before the trigger removes the option. Only a tool that decides each booking on its own server before confirming it avoids this.