FormDB vs Netlify Forms

Netlify Forms is part of Netlify hosting. FormDB is a separate form backend for any host. Compare validation, uploads, limits and integrations.

Netlify Forms is a feature of Netlify hosting that collects submissions from forms on sites Netlify deploys. FormDB is a standalone form backend: you point a form on any website at a FormDB URL, whichever host serves the page.

At a glance

Feature

FormDB

Netlify Forms

Free plan allowance

250 submissions a month

Unlimited on credit-based plans, 100 per site a month on legacy plans

Data retention

30 days on Free, unlimited on paid plans

Not stated

Server-side validation rules

Yes, on every plan

Not stated

Spam protection

Honeypot, keyword filters and custom rules, country and language filters, duplicate detection, IP blocking, built-in captcha or your own keys

Akismet, optional honeypot, optional reCAPTCHA 2

File uploads

Every plan, 10 MB to 250 MB per file depending on plan

Supported, 8 MB per request, one file per field

Integrations

Webhooks, Slack, Discord and Telegram on every plan, Google Sheets, Notion, Airtable, Stripe and Zapier on paid plans

Email, webhook and Slack notifications, Zapier, n8n, functions

API access to submissions

REST API with keys on paid plans

Yes, through the Netlify API

Auto-responder emails

Paid plans

Not stated

Pricing model

Free plan plus paid subscription plans

Included with Netlify hosting plans

Where FormDB is different

It is not tied to your host

FormDB works with a form on any site: a static page, a site builder that allows custom HTML, or an app hosted anywhere. Netlify's documentation says forms are detected at deploy time from HTML marked with data-netlify="true", and forms rendered by JavaScript need a hidden static copy. If you move your site to another host, a FormDB form keeps working without changes.

Server-side validation rules

In FormDB's builder you attach rules to each field, such as length limits, patterns, allowed email domains, number ranges and file types. The server checks every submission and returns an error per field. Netlify's forms documentation did not describe server-side validation rules when we checked.

JSON and larger uploads

FormDB accepts URL-encoded, multipart and JSON submissions, so a fetch call can post JSON directly. Netlify's documentation states that Netlify Forms does not support JSON form data. For files, FormDB allows 10 MB per file on Free and up to 250 MB on Business, and a small script can send large files straight to storage. Netlify lists an 8 MB request limit and one file per field.

Direct database integrations

Paid FormDB plans can write each submission to Google Sheets, Notion or Airtable and link Stripe payments, with no automation tool in between. Netlify Forms offers email, webhook and Slack notifications, and connects to other tools through Zapier, n8n or your own function. FormDB also has webhooks, Slack, Discord and Telegram on every plan, and a REST API and Zapier integration on paid plans.

Where Netlify Forms is the better choice

  • Your site is already on Netlify. There is no second account or vendor. You add an attribute to your form and deploy.
  • No submission limit on credit-based plans. Netlify's documentation says form usage is free and unlimited on its credit-based plans. FormDB plans have monthly limits. Note that Netlify's legacy plans include 100 submissions per site a month, and that a team that runs out of credits has its projects paused, which stops form submissions too.
  • Akismet spam filtering. Netlify runs Akismet on all submissions. FormDB uses its own classifiers and rules, set per form, and does not use Akismet.
  • Functions on the same platform. Netlify can trigger a serverless function on each verified submission. With FormDB you point a webhook at code you host somewhere else.

Which should you choose?

Choose FormDB if your site is not on Netlify or may move, if you want field rules checked on the server, if you post JSON, or if you want submissions written straight to Notion, Airtable or Google Sheets.

Choose Netlify Forms if your site is deployed on Netlify, simple notifications are enough, and you would like forms handled by the same platform as your hosting.

Switching from Netlify Forms

  1. Create a form in FormDB and copy its endpoint. The quickstart explains how.
  2. Remove the data-netlify="true" attribute and set the form's action to https://api.formdb.io/f/your-form-id with method="POST". See HTML forms.
  3. Replace any netlify-honeypot field with a hidden text input named _gotcha. If your action pointed to a success page, set that address as the redirect URL in the FormDB form settings.
  4. Deploy, send a test submission and check your FormDB inbox.

Past submissions are not imported. Netlify offers a CSV export of verified submissions, so download a copy first if you need the history. For FormDB prices, see our pricing page.

Details about Netlify Forms come from their public pricing and documentation pages as of November 2026 and may have changed. Check their site for current information.

Your form can be livebefore your coffee is cold.

Create a form, paste one URL and send yourself a test. The Free plan covers 250 submissions a month, with no credit card required.