Netlify Forms review (2026): free, built in, and tied to Netlify

How Netlify Forms works

Netlify Forms is not a separate endpoint you sign up for. You add a data-netlify="true" or netlify attribute to a form in your site's HTML, turn on form detection in the Netlify UI, and redeploy. Netlify's docs say its build system parses the HTML of your site when the build completes, strips the attribute and injects a hidden input named form-name, and from then on Netlify accepts submissions for that form.

Because detection happens on Netlify's deploy pipeline and submissions are handled by your Netlify site, it is designed for sites deployed to Netlify. The docs do not describe using it from a page hosted somewhere else, so moving the site to another host means moving the forms to another backend too.

After a submission, visitors see a generic Netlify success page unless you set the form's action to a path on your own site, such as /thanks, or submit with AJAX and show your own message.

• Turn on form detection under Forms in the Netlify UI, then redeploy
• Every input needs a name attribute
• Custom success page: action="/your-path", relative to the site root
• Changing detection settings only takes effect after the next deploy

The JavaScript-rendered form gotcha

The most common Netlify Forms problem is a form that never shows up. If a form is rendered only in the browser by React, Vue or another framework, Netlify's build system will not find it in the pre-built files. The docs give two fixes: add a hidden static HTML form with the same name and the same input names, or add a hidden form-name input to the JavaScript form.

For Next.js on Netlify's v5 runtime, the troubleshooting docs say you need to put form definitions in a dedicated static HTML file and submit with AJAX rather than a full-page navigation.

AJAX submissions must send a URL-encoded body; the setup docs state that Netlify Forms does not support JSON form data. File uploads can use multipart, and Netlify recommends letting the browser set the Content-Type header in that case.

Is Netlify Forms free? Pricing and limits in 2026

Yes, on Netlify's credit-based plans. Netlify's Forms usage and billing docs say that for credit-based plans, Forms are free and unlimited, and the April 14, 2026 changelog says form submissions became free across all credit plans; before that, each submission cost 1 credit. Every Netlify account created since September 4, 2025 is on a credit-based plan.

Netlify does not sell Forms on its own. The pricing page lists Free ($0, a 300-credit limit), Personal ($9/month, 1,000 credits), Pro ($20/month, 3,000 credits) and Enterprise (custom). Credits pay for the rest of the hosting platform, such as deploys and bandwidth. On the Free plan, a site that exceeds its monthly limits pauses until the next billing cycle or an upgrade, and the billing FAQ says paused projects do not receive form submissions.

Accounts created before September 4, 2025 can still be on legacy plans. Netlify's legacy plan table lists 100 form submissions per site per month on Free and Starter and on Pro, with legacy Pro charged from $19 when exceeded. The legacy billing FAQ's example of the entry Forms level includes 100 submissions and 10 MB of uploads a month. On the legacy free tier, reaching 100% of a metered limit pauses all sites on the account until you add a payment method and upgrade.

Spam protection

Netlify's spam filter docs say every submission is checked with Akismet. Submissions that pass appear under Verified submissions; ones Akismet flags go to a Spam submissions list, and you can move a submission between the two.

Two extra layers are opt-in. A honeypot is set with a netlify-honeypot attribute that names a hidden field, and Netlify quietly rejects any submission that fills it in. reCAPTCHA 2 is added with data-netlify-recaptcha="true"; Netlify's built-in CAPTCHA is limited to one per page, and you can supply your own reCAPTCHA keys for more. Submissions rejected by the honeypot or reCAPTCHA are not kept in the spam list.

On legacy plans, the usage page counts verified submissions, so spam caught by Akismet is not what the meter tracks.

File uploads

Add an input with type="file" and Netlify stores the upload with the submission. The setup docs list three limits: the whole form request can be at most 8 MB, uploads time out after 30 seconds, and each field takes one file, so multiple files need multiple fields.

If uploads may contain personal information, Netlify's docs say they need additional security configuration and recommend the Very Good Security integration. After a form is deleted, its uploaded files stay reachable by direct URL for 24 hours because of caching.

Notifications and integrations

Under Forms, Submission notifications, you can send verified submissions to email or webhooks, for one form or for every form on the site. Slack notifications run through the Netlify App for Slack, and Netlify also documents Zapier and n8n apps and functions triggered by form submissions.

Notification emails come from [email protected]. Add an input named email and Netlify sets it as the Reply-To, so you can answer the visitor directly. The subject line can be set in the UI or in a hidden subject field, with variables such as the form name, site name and submission ID. The docs list no plan restrictions for notifications.

Data, export and privacy

Submissions live in your site's Forms tab. Verified submissions can be downloaded as CSV, single or bulk submissions can be deleted permanently, and the Netlify API can list verified or spam submissions and delete submissions or forms. Netlify does not publish a retention period for submissions; its docs recommend exporting and deleting submissions regularly if they contain personal information.

If you rename or change a field, the Netlify UI only shows fields from the last deployed version of the form, although older data is still available through the API. Deleting a form deletes its submissions, and later posts to it return a 404.

Netlify, Inc. (101 2nd Street, San Francisco) runs the service. Its privacy statement says it acts as a processor for customer-submitted personal data, publishes a DPA, and relies on the EU-U.S. Data Privacy Framework and standard contractual clauses for international transfers.

Support

Netlify's pricing page lists priority email support on Personal (and so on Pro, which includes everything in Personal) and 24/7 dedicated support on Enterprise; it lists no support tier for the Free plan. Netlify's support page points everyone to its docs, community forums and an AI assistant, with a contact option for the support team.