For years, the best-known fact about Netlify Forms was its pricing cliff: 100 submissions a month free, then $19/month per site the moment submission 101 arrived. Whole blog posts, Reddit threads and alternative-hunting sessions - some of the search traffic that lands on this very site - exist because of that cliff. So it is worth saying clearly: as of Netlify's move to credit-based pricing, the cliff is gone. Their pricing page meters deploys, compute, bandwidth and requests; forms are not billed as a separate line at all. We verify competitor pricing before writing about it, and this held on September 3, 2026.
What actually changed
Netlify's plans used to meter Forms as its own add-on with levels: free to 100 submissions and 10MB of uploads monthly, then paid levels per site. The credit model replaced per-feature add-ons with a shared pool - the Free plan gets 300 credits, Personal 1,000, Pro 3,000, and features draw from the pool at published rates. Form submissions ride on the requests and bandwidth you were already paying for; there is no forms meter to trip. For a portfolio site with a contact form, this is strictly better than the old deal, and if that is your situation you can stop reading here: keep Netlify Forms, it is fine.
The limits that remain are not about counting submissions
What the pricing change did not touch is the architecture, and the architecture is where the remaining limits live:
- Build-time detection. Forms are discovered by scanning deployed HTML, so JavaScript-rendered forms still need the hidden-static-copy workaround, and a form change still means a redeploy.
- Spam is Akismet's opinion. There is no threshold to tune, no blocklist to edit, and marking false positives teaches nothing you control.
- Notifications stop at email, Slack and a webhook - per site, not per form. No Discord, no Telegram, no per-destination delivery log to check when a notification silently fails.
- No delivery evidence. When a submission does not show up where you expected, there is no per-attempt record showing what was tried and what the receiving end said.
- Host coupling. The quiet one: your form backend is your host. Moving the site means migrating forms, which is exactly the kind of chore that keeps sites where they are.
The honest decision table
- Static site on Netlify, one contact form, low stakes: stay. The old reason to leave was the cliff, and the cliff is gone.
- Form is operational - leads, intake, anything where a lost submission costs money: the limits above are the real ones, and they are architectural, not priced away.
- Site might leave Netlify someday: a host-independent form endpoint now saves a migration later. A WebForms form is one action attribute and works from any host.
- Framework-rendered forms (React, Vue, Next): the hidden-static-copy dance never stops being annoying. A POST endpoint does not care how the form was rendered.
If you land on switching, the field-by-field walkthrough - data-netlify attributes out, action and _gotcha in, what happens to your old submissions - is in the migration guide linked below. And if you were only ever here to find out whether the 100-submission limit still exists: no, and any post still telling you otherwise was written before the credit plans.