A response cap usually arrives on launch day, when the form is doing its job. This page covers what form tools do at the limit, what they count as a response, and how to size a plan for a spike.
Four behaviors at the limit
| Behavior | What respondents see | What you lose |
|---|---|---|
| Close the form | A closed or over-quota message | Everyone who arrived after the limit, with no record of who they were |
| Keep collecting and bill the excess | The form as normal | Money, on the next invoice |
| Keep collecting and hide the excess | The form as normal | Access to responses until you upgrade |
| Keep collecting and ask for an upgrade | The form as normal | Nothing, until you choose a larger plan |
Only the vendor can tell you which applies. Checked on 2026-09-27 against each vendor's own docs:
| Tool | Documented behavior at the limit |
|---|---|
| Typeform | Forms go into private mode at 100% of the limit and reopen next month or after an upgrade. Warning emails go out at 90% and 100%. Free includes 10 responses a month. |
| Jotform | Monthly submission limits reset each cycle. Reaching a limit disables forms on a date given by email, and respondents see "Form over quota". Starter includes 100 submissions a month. |
| Formspree | Free includes 50 submissions a month and 30 days of history. Notifications go out at 50%, 75%, and 90%, and when the limit is exceeded. The page doesn't say what happens to submissions past the limit. |
Where a vendor doesn't document the behavior, ask their support in writing.
What counts as a response
The counting rule changes which plan you need. Ask these four questions:
- Does a preview or test submission count?
- Does an abandoned partial count, or only a completed submission?
- Does editing an earlier answer create a second response?
- Do spam and bot submissions count?
Spam matters most. A bot wave can use a month's allowance and close the form to real people, so spam protection and response caps are one buying decision. If partials count, a long form with high drop-off burns quota on people who never finished.
Size a plan for a launch spike
- Estimate the busiest week you could have, not the average.
- Ask what happens at 100%: closed, billed, hidden, or an upgrade request.
- Check whether the limit is monthly or a lifetime total.
- Find the notification thresholds and who receives them.
- Confirm an upgrade reopens the form and recovers what was missed.
- Check you can export responses and files if you leave.
If an upgrade mid-spike doesn't recover missed respondents, buy headroom instead of relying on a fast upgrade.
What Fillo does
Fillo counts accepted submissions. Building, previewing, saved drafts, partial entries, and submissions caught by the spam checks don't count, and the pricing page says so. Updating an existing response counts as a submission, and deleting a response doesn't give the count back.
| Free | Everything | |
|---|---|---|
| Completed responses included | 200 per month | 5,000, 25,000, or 100,000 per month |
| Above the allowance | The form keeps collecting | The form keeps collecting |
| Save and resume, response limits, webhooks, exports | Included | Included |
Going over the allowance never closes a form, drops a submission, or adds a charge, on any plan. At 80% and 100% of the monthly allowance, workspace owners get an email and an in-app note suggesting a larger volume.
A workspace created by a coding agent is a capped preview. It accepts 10 responses until its owner claims it from the email. Claim it before real traffic arrives. Current figures live in Plans and limits.
Related
- Beta access example: A launch-shaped form you can submit right now.
- Plans and limits: Current allowances, schema caps, and rate limits.
- Spam protection: Keep bot submissions out of the response count.
- Exports: Take responses and file references with you.