What happens when a form hits its response cap

A response cap never arrives on a quiet week. It arrives on the day the post lands, the newsletter goes out, or the workshop fills — the moment the form is doing exactly what it was built for. What happens next isn't the same across tools, and it's usually not on the pricing page.

There are two questions worth answering before you publish. What does this tool do at the limit? And what does it count as a response?

Three behaviors at the limit

Tools resolve a full quota in one of three ways:

• Close the form. New respondents see a closed or over-quota message. Anything they were part-way through is not collected.
• Keep collecting, charge for the excess. The form stays open and the overage appears on the bill.
• Keep collecting, hide the excess. Responses are stored but not visible until the plan is upgraded.

The first is the one that costs you the campaign, because the people who bounced are gone and you can't tell who they were. The third is the one that feels like a rug-pull, because the data exists but is behind a paywall you discovered after the fact.

Only the vendor can tell you which applies. What follows is what each vendor documents, checked as of 2026-08.

Typeform. Answering a question in Typeform's own community about exceeding the response limit, a Typeform community advocate explains that the form closes once the limit is reached, and that responses started after that point aren't recovered by upgrading the plan afterwards — the people who started have to be asked to submit again (community thread).

Jotform. Jotform's account-limits documentation separates monthly limits that reset from total limits that don't, and states that reaching a limit causes forms to be disabled on a scheduled date communicated by email, after which respondents see a Form over quota message (account usage and limits).

Formspree. Formspree documents a 50-submission monthly allowance on the free tier, 30 days of submission history on that tier, and notifications at 50%, 75%, and 90% of the monthly limit as well as when it's exceeded (account limits). The page doesn't state what happens to submissions received past the limit. That's a gap in the documentation, not evidence of any particular behavior — ask support before relying on it.

That short list is deliberate. Where a vendor doesn't document the behavior, the honest answer is that you have to ask them.

What counts as a response

The cap number is only half the arithmetic. The other half is the counting rule, and it varies enough to change which plan you need:

• Does a preview or a test submission count?
• Does an abandoned partial count, or only a completed submission?
• Does a respondent editing an earlier answer create a second response?
• Do spam and bot submissions count against the quota?

The last one has a nasty shape: a spam wave can consume a month's allowance and close the form to real people, so anti-spam and response caps are the same purchasing decision. If a tool counts partials, a long form with a high drop-off rate burns quota on people who never finished.

Ask for these four answers in writing before you size a plan. A 1,000-response allowance that counts partials and previews is not a 1,000-response allowance.

Evaluating a plan for a launch spike

Steady-state volume is the wrong input. Size for the spike:

1. Estimate the peak, not the average. Take the busiest single week you can plausibly have and multiply out. Launches, events, and press are lumpy.
2. Ask what happens at 100%. Closed, billed, or hidden — get it in writing, from documentation or support.
3. Check whether the limit is monthly or lifetime. A total storage limit that never resets is a different commitment from a monthly allowance.
4. Find the notification thresholds. An alert at 90% is only useful if it reaches someone who can act on a Saturday.
5. Confirm the upgrade is instant and retroactive. If upgrading mid-spike reopens the form but doesn't recover what was missed, you need headroom rather than a fast upgrade path.
6. Check the export path on the way in. If you ever need to leave, the question is whether you can take the responses and files with you.

Step 6 is the one people skip. Evaluating the exit before the entrance is the cheapest insurance in this category.

Fillo's behavior

Fillo counts completed responses only. Building a form, previewing it, and partial entries don't count — that rule is on the pricing page, not in a support thread. Save-and-resume drafts are available on every plan and a draft doesn't consume the allowance until it's submitted.

As of 2026-08, from Plans and limits:

The Everything plan meters overage rather than closing the form. That's the deliberate difference from a hard wall: a spike costs money instead of costing you the responses. Fillo is free during early access and doesn't require a card; going over the shown launch allowance won't break collection during early access, and there will be notice before billing starts.

One limit worth knowing in advance: a workspace provisioned by an agent stays capped at 10 responses until its owner claims it from the email. Claim it before putting real traffic on the form.

Related

• Plans and limits: Current allowances, schema caps, and rate limits with the date they were checked.
• Pricing: What a response counts as, and what each plan includes.
• Save and resume: Let respondents finish later without spending quota.
• Spam protection: Keep bot submissions out of the response count.
• Exports: Take responses and file references with you.
• Beta access example: A launch-shaped form you can submit right now.