What Happens When You Exceed Your Form Submission Limit

Your contact form has worked fine for weeks, and then one day a submission never lands in your inbox. On a hosted form backend, the most common cause is quietly hitting your monthly submission limit, and a static site has no built-in way to warn you when that happens. SimpleForm is a hosted form backend for static websites: you point a form's action attribute at a SimpleForm endpoint, and it delivers each submission by email, dashboard, and webhook. A submission limit is the maximum number of form submissions a plan accepts and stores within a billing period — go over it, and the extra submissions are neither emailed nor saved.

This matters more than most static-site owners assume, because a missed submission usually means a missed lead, and nothing on the page tells the visitor their message failed to arrive.

A static site has no server log to check and no error page to notice, so a form that quietly stops delivering can go unfixed for weeks. The visitor sees the same confirmation message whether the submission was stored or dropped, because the browser has no way to know the account behind the endpoint has run out of monthly capacity. The only place that gap shows up is the dashboard, and only if someone thinks to look there.

What Counts as a Submission Toward Your Limit?

Every POST request that reaches your SimpleForm endpoint and clears spam filtering counts as one submission, regardless of whether the browser sent it as multipart/form-data, JSON, or a standard URL-encoded post. The format does not change how it is counted.

SimpleForm's built-in honeypot field and per-IP rate limiting — a cap of 10 submissions per IP per hour per endpoint — are there to catch obvious bot and scripted traffic at the edge. Filtering that traffic out before it reaches your inbox is the main way to keep your monthly allowance available for real visitors instead of junk.

Because any standard HTML form with a POST method and an action attribute works, the same endpoint can sit behind a contact form, a newsletter signup, or a quote request without any code change on your side. Each of those forms draws on the same account-level monthly count, so a site running several forms reaches its cap faster than a site running one.

Why Does SimpleForm Return a 402 Response Over the Limit?

Once a plan's monthly count is used up, further submissions to that endpoint get an HTTP 402 response instead of being stored. 402 is the "Payment Required" status in the HTTP specification, and SimpleForm uses it literally: the request was valid, but the account has run out of included capacity for the period.

A 402 response does not take your form offline. Submissions that arrive before the cap is hit, and any that arrive after the count resets on the first of the month, are processed normally. Only the submissions between hitting the cap and the reset are dropped, and they are not queued or retried automatically — there is no record that they were ever sent.

The practical effect is that you find out about a 402 response only by checking usage yourself or by a visitor complaining their message never got a reply. Neither is a good way to discover it mid-month, which is why treating the dashboard count as something to glance at occasionally, rather than only after something seems wrong, catches the problem before a real inquiry is lost.

How Do the Free, Pro, and Agency Limits Compare?

The three SimpleForm plans differ mainly in how many submissions they include per month and which delivery options come with them.

Free also includes 3 forms and 7 days of submission history, at no cost and with no credit card required to start. Full billing details, including annual pricing, are on the pricing page.

Retention scales with plan too. Free keeps each submission visible in the dashboard for 7 days before it ages out, while paid plans hold data for longer — up to 365 days, depending on the plan. That gap matters if you export submissions into a spreadsheet or CRM only occasionally, since a 7-day window can close before you get to it.

What Should You Do Before You Hit the Limit?

The cap is easiest to manage before you cross it, not after a lead has already vanished into a 402 response. None of these steps require touching your form's HTML — they are account and dashboard changes only.

1. Check your submission count in the SimpleForm dashboard a few days before the billing period resets, especially after a traffic spike.
2. Let the honeypot field and the 10-per-hour IP rate limit filter obvious bot traffic before it can eat into your real allowance.
3. Upgrade before the count is likely to bind, not after — plan changes take effect immediately, with billing prorated for the switch.
4. Once you are on Pro or Agency, add a webhook so submissions reach Slack, Discord, or a CRM the moment they arrive, independent of the dashboard's retention window.

If you are still setting a form up for the first time, the integration docs walk through pointing a form's action attribute at your endpoint and checking usage from the dashboard once submissions start arriving.

Is Paying to Raise the Limit Actually Worth It?

The honest objection to upgrading is cost: paying anything monthly feels unnecessary if you only brush against the free plan's 100-submission cap once in a while. That objection holds right up until it doesn't — a form that sits under 90 submissions for months can spike past 100 the week a page gets linked from somewhere with real traffic, and every submission past the cap during that spike is one you never see.

Pro runs $9 a month, or $90 billed annually, for 5,000 submissions plus webhooks and file uploads — roughly the price of one missed lead for most businesses that rely on their contact form. Annual billing on Pro works out to two months free compared with paying monthly, which is worth taking once you know you will stay above the free tier. Agency scales further to 25,000 submissions a month at $29 a month, or $290 annually, for teams running forms across several client sites. Neither plan requires migrating your existing forms; the same endpoint URL keeps working after you upgrade.

The alternative some teams consider is writing a small backend of their own instead of paying for a higher tier. That trades a monthly fee for ongoing work: standing up an endpoint, handling spam without a honeypot already built in, storing submissions somewhere durable, and maintaining all of it as traffic grows. For a form that generates real business inquiries, the maintenance hours usually cost more than the $9 or $29 a month they were meant to avoid. If you are unsure which plan fits your traffic, the team behind SimpleForm answers plan questions directly through the contact page.

Start on a Plan That Matches Your Traffic

Create a free SimpleForm account and check today's submission count against the limits above before your next traffic spike arrives — it takes a couple of minutes and the Free plan needs no credit card to try. Sign up for SimpleForm and point your existing form's action attribute at the endpoint it gives you.

Frequently asked questions