How to Limit the Number of Responses in Google Forms (2026)

Can Google Forms Limit the Number of Responses?

Yes — Google Forms can limit responses natively, a capability it added in January 2026 after years of requiring add-ons. Form owners and editors can now set the form to stop accepting submissions once it hits a chosen number, and Google documents the change in its Workspace Updates announcement on forms that stop collecting responses. The reason so many guides still say “Forms can’t do this” is that the feature is off by default and tucked inside the publish settings, so unless you go looking for it, nothing signals that it exists.

That native cap is genuinely useful, and for a lot of people it’s all they need: a workshop with a fixed number of seats, a giveaway limited to the first 100 entries, a study that stops at its target sample size. The rest of this guide shows you how to turn it on from an iPhone, spells out the real limits Google didn’t remove, and points to add-ons for the cases the native feature still can’t handle.

Set a Response Limit Natively (Step-by-Step on iPhone)

To cap responses natively, open your form’s publish settings and set the limit in the Responses tab — the whole thing works in Safari on an iPhone, no computer required. The one prerequisite that trips people up is publishing: the close rules only apply once the form is published, so a limit set on an unpublished draft quietly does nothing.

1. Open your form in Safari on iPhone and make sure it’s published (use the Publish button if it isn’t yet).
2. Go to the Responses tab.
3. Tap Set close date or response limit.
4. Choose stop accepting responses after a number of responses.
5. Enter your cap — for example, 50. If the form already has responses, set a number higher than the current count, or it will close immediately.
6. Optionally, edit the closed message respondents will see once the form is full (plain text only).
7. Save.

That’s the entire setup. From here on, Google counts submissions server-side and shuts the form off the moment it reaches your number — you don’t have to watch it. If you’re building the form itself from scratch on a phone first, our how to create a Google Form on iPhone guide covers that half, and you’d add the response limit as the last step before sharing.

The Limits of the Native Response Cap

The native response cap does one job well but leaves several gaps, and knowing them up front saves you from discovering them at the worst moment. The single most important one: you can set a count or a close date, but not both — Google’s feature treats them as mutually exclusive, so “close when full or when the deadline passes, whichever comes first” is out of reach natively.

Here’s the honest breakdown of what the built-in limit can and can’t do:

Two of these bite most often. The silent close means a form can fill and shut without you noticing until someone asks why they can’t submit — Google sends no alert. And the plain-text closed message means you can’t turn latecomers into a tappable waitlist link; you can write the URL out, but they’ll have to copy it by hand. If either of those matters for your use case, the next section is for you.

When You Need More — Add-Ons and Native App

When the native cap’s gaps get in your way, a third-party add-on or a native app closes them — each with a different strength. The classic answer is formLimiter, a free Workspace Marketplace add-on that has handled form limits for years and does the things Google’s version won’t.

• formLimiter and similar add-ons (Form Response Limiter and others) can email you when the limit is reached, evaluate a count and a date together, and in some cases set per-choice limits — the exact capabilities the native feature drops. You install and configure these in a desktop browser via the Marketplace.
• The Forms for Google Drive (by Pipiform) app manages your form’s response settings from an iPhone, so you can adjust caps and controls without switching to a laptop — its Response Limits are one of its Advanced Form Controls.

Be clear-eyed about the trade-offs: add-ons are the most powerful for notifications, combined conditions, and per-option caps, but they’re desktop-configured; the app is the phone-first way to manage settings but sits alongside, not on top of, Google’s own controls. Pick by which gap you actually need to close. Add-ons can also occasionally introduce their own quirks — if a form starts misbehaving after you install one, our Google Forms not working on iPhone guide walks through isolating the cause.

Response Limit vs Close Date vs Per-Person Timer

“Close the form” can mean three different triggers, and choosing the wrong one is a common, avoidable mistake. A response limit closes the form once it hits a number of submissions; a close date closes it at a fixed moment on the calendar for everyone; a per-person countdown timer gives each respondent their own N minutes and auto-submits when their time runs out. They solve genuinely different problems.

This guide is the count trigger. If your goal is a calendar deadline — “registration closes Friday at 5 PM” — that’s a close date, a separate native feature our how to set a close date or deadline on Google Forms guide covers in full. And if you need each person capped to a set number of minutes — a timed quiz — that’s a countdown, which our how to add a timer to Google Forms on iPhone guide walks through in full. Match the trigger to the job and the “which setting do I even use” confusion disappears.

Common Response-Limit Problems

Most response-limit trouble traces back to one of four things, and each has a quick fix. Running through them in order resolves nearly every “my limit isn’t working” report we see.

• The limit does nothing → the form was never published. Close rules only apply from the published state, so publish first, then set the limit.
• The form closed instantly → your cap was lower than the responses already collected. Set the number above the current count.
• You wanted a count and a deadline → the native feature only does one or the other. Use an add-on that evaluates both conditions.
• The cap was hit and you had no idea → native closes silently. Use an add-on that emails you, or check the response count yourself on a schedule.

The one worth repeating because it’s the most frequent: the most common “my limit isn’t working” case we see is a form that was never published — the close rules simply don’t exist until the form goes live. Publish, set, save, in that order, and the enforcement is reliable.

Which Setup Should You Use?

The right approach falls out of a single question — how simple is your cap — and it sorts into three clean cases.

• A simple one-time cap (fixed seats, first-N giveaway, a target sample size) → use the native response limit. It’s built in, free, and set in under a minute from your phone.
• You need alerts, a count-plus-date combo, or per-option limits → use a third-party add-on like formLimiter, configured in a desktop browser.
• You manage forms mostly from a phone → use the Forms for Google Drive app to adjust response settings and caps without a laptop.

For most people the native cap is the honest answer — it covers the everyday “stop at N” need without installing anything. Reach past it only when a specific gap (notifications, combined conditions, per-choice limits) actually blocks you.

Summary

Google Forms can cap responses natively as of January 2026: in the Responses tab, tap Set close date or response limit, choose to stop after a number of responses, enter your cap, and save — the form closes itself when it fills. The limits to plan around are real but narrow: you can set a count or a close date, not both, there’s no delayed-open option, the form closes silently with no alert, and the closed message is plain text only. For notifications, combined count-and-date rules, or per-option caps, a third-party add-on like formLimiter fills the gap, while the Forms for Google Drive app lets you manage response settings from an iPhone. Match the trigger to the job — count here, close date and per-person timer in their own guides — and stopping a form at the right moment stops being guesswork.