Web3Forms Alternative: When to Keep It and When to Leave

Web3Forms is a form backend for static sites. You paste an access key into a plain HTML form and submissions arrive as email, with no PHP and no WordPress required. A Web3Forms alternative is worth looking at when that 250-submission free cap, the paid-only file uploads or the fact that the data lives on someone else’s server starts to matter.

I build Core Forms, which is one of the options below, so you should know whose table you are reading. I’ll still say where Web3Forms is the better tool, because for a lot of static sites it is.

There are generally three ways people handle this.

You can stay on the free plan forever and treat 250 submissions a month as a hard ceiling. That works until a launch week, a spam wave or a file field shows up.

Or you can jump to another hosted backend the moment a limit appears, and keep paying per month for email that a WordPress site you already own could have stored.

But being extreme isn’t a good idea at all. Web3Forms is a good HTML form to email service. It is wise to keep it when the site is static and the volume is small, and to move when you need storage you control, file uploads on every plan or a form that has to live past the next SaaS price change.

The form is yours. The question is who owns the inbox after submit.

Web3Forms is the free endpoint. The alternative is about volume, files and where the row is stored.

What Web3Forms Costs Right Now

Prices below are from Web3Forms’ pricing page in September 2026, with yearly billing shown first because that is how they sell Pro and Agency.

• Free: 250 submissions a month, unlimited forms, unlimited domains, hCaptcha, a custom redirect, 30 days of dashboard history and 1 email recipient. Free forever, until they detect abuse.
• Starter: $49 a year, 5,000 submissions a month, limited paid features. No file uploads and no autoresponders. They call this a special plan for students, early startups and non-profits.
• Pro: $12 a month when billed yearly ($149 a year), or more on monthly billing. 10,000 submissions, file uploads with 5 GB included, autoresponders, webhooks, Google Sheets, Notion, Slack, up to 5 recipients, 1 year of history and 3 team seats.
• Agency: $33 a month billed yearly ($399 a year). 20,000 submissions, 10 GB of file storage, 10 seats, 20 linked emails and dedicated support.

The number that actually moves the decision is the monthly cap. Hit 100% and Web3Forms stops accepting new submissions until the next month. They warn you at 90% and again at 100%. There is no overage bucket. The form goes quiet.

File uploads, autoresponders and webhooks sit on Pro and Agency. The free plan is email plus spam protection, which is enough for a contact page and not enough for a job application.

Where Web3Forms Is Still Better

Before the alternatives, the honest list.

The free plan is real. 250 submissions a month, forever, with unlimited forms and domains, is more generous than Formspree’s 50 and more honest than a 14-day trial wearing a free badge. For a personal site, a docs site or a client brochure that gets a handful of messages, this is the whole product.

Setup is one attribute. The form posts to https://api.web3forms.com/submit with a hidden access_key. No build plugin, no netlify attribute, no WordPress. That is why static-site people search for it.

Spam protection is on the free tier. hCaptcha and a honeypot ship without an upgrade. Plenty of hosted backends hide that behind Pro.

If those 3 things are why you chose Web3Forms, and 250 a month is more than you will ever see, the sensible advice is to stay.

Where a Web3Forms Alternative Wins

The case for leaving is the same product seen from the other side.

The cap is a hard stop. A contact form on a quiet site never hits 250. A launch, a directory listing or a bot that learned the endpoint will. When the form refuses new mail, the visitor sees a failure, not a “please upgrade” screen you control.

Files and auto-replies are paid. A job application, a reimbursement claim or a bug report with a screenshot needs input type="file". An autoresponder that says “we got this” needs Pro. Those are ordinary forms, not agency features.

The row is not on your server. Submissions live in Web3Forms’ dashboard, retained up to 3 years on free and Starter, unlimited on Pro. For a hobby contact form that is fine. For anything involving employees, students, health or the EU, you now have a processor to name in the privacy policy.

Integrations stack on the paid plan. Sheets, Slack, Notion and webhooks are Pro. If the form is supposed to create a CRM row, you are already off the free tier.

Web3Forms vs the Usual Alternatives

If the shortlist is already down to “keep the HTML, change the endpoint,” these are the tools that actually replace Web3Forms. Core Forms is the WordPress-shaped answer in that list, not a second hosted key.

The right pick is the one whose limit you will not hit and whose storage model you can defend.

The Formspree alternative and Netlify Forms alternative pieces go deeper on those two. The HTML form backend roundup covers Formspark, Formcarry and the rest without repeating this table.

Which Alternative Fits Which Site

The table is the summary. The hosting is the decision.

You have a static site and under 250 messages a month

Stay on Web3Forms. The free plan is the product. Moving to another key for the same email is busywork.

You have a static site and you need files, webhooks or a higher cap

Formspark’s one-time 50,000-credit bundle is the cleanest “I do not want a subscription” path. Formspree Professional is the cleanest “I want a dashboard and plugins” path. Formcarry Starter is the cheapest recurring HTML endpoint if 500 a month is enough.

None of those put the row on a server you admin. If that is the actual requirement, the next heading is yours.

You already run WordPress, even on a different domain

Core Forms is the Web3Forms alternative that stops being a SaaS. The HTML can live on Astro, Next.js or a static host. The submit POST goes to WordPress. The submission, the spam filters, the email actions and the file sit in WP-Admin.

That is the job the WordPress form backend post walks through, and the headless WordPress forms guide is the same idea from the other direction: a Core Forms form rendered off-WordPress.

I bundled file uploads, autoresponders, Slack, HubSpot, Sheets and webhooks into one price because “which tier has my integration” is a question I never wanted people to ask. The catch is real: you have to keep WordPress updated, and the ecosystem is smaller than Formspree’s plugin list.

You are on Netlify already

Use Netlify Forms until you leave Netlify. On their credit-based plans, form submissions are unlimited and free as of April 2026. The lock is the host, not the invoice. The moment the site moves to Cloudflare Pages or a VPS, the data-netlify attribute is dead markup.

How a Web3Forms Form Looks

The markup is the whole pitch. This is the pattern their docs teach, with labels added because a form without labels is a problem you should not copy.

<form action="https://api.web3forms.com/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
  <p>
    <label for="w3-name">Name</label>
    <input id="w3-name" type="text" name="name" autocomplete="name" required>
  </p>
  <p>
    <label for="w3-email">Email</label>
    <input id="w3-email" type="email" name="email" autocomplete="email" required>
  </p>
  <p>
    <label for="w3-message">Message</label>
    <textarea id="w3-message" name="message" rows="6" required></textarea>
  </p>
  <button type="submit">Send message</button>
</form>

A Core Forms HTML form looks the same on the page. The action points at your WordPress REST submit URL instead of api.web3forms.com, and the access key is an API key you issue in WP-Admin. The HTML form to email post covers the mailto trap that people reach for before either of these.

The Limits

Web3Forms is not a form builder. There is no drag-and-drop, no multi-step UI, no calculated fields and no WordPress inbox. If you wanted those, you searched the wrong product.

It is also not a CRM. Sheets and Slack on Pro are pipes, not a record you can moderate, mark as spam or assign.

And the 7-day refund on paid plans is a review, not a guarantee. Their own FAQ says refunds are approved when a good-faith effort was made and the limitation is on their side.

Core Forms is not a static-only tool. If there is no WordPress install you are willing to maintain, it is the wrong Web3Forms alternative. Use Formspark or Formspree instead.

What Quietly Ruins It

Leaving the access key in a public repo and then rotating nothing when the form starts eating spam. The key is a secret in HTML, which means it is not a secret. Domain restriction on Pro exists for this reason. On free, a honeypot and hCaptcha are the whole fence.

Treating 250 as “unlimited for me” without a plan for the month a directory links you. The form does not degrade. It stops.

Putting a file input on the free plan and debugging why nothing arrives. Uploads are Pro. The field will submit. The backend will not store the file.

Using Web3Forms as long-term storage for applications, invoices or anything you would be sad to lose in a dashboard retention sweep. Export if the row matters. Better, store it somewhere you back up.

Final Remarks

A Web3Forms alternative is not a better access key. It is a decision about the month you go over 250, the first PDF someone attaches and whether you want that row on a server you already pay for.

If the site is static and quiet, keep Web3Forms. If the site is static and busy, pay Pro or buy Formspark credits. If WordPress is already in the stack, point the same HTML at Core Forms and stop renting the inbox.

The form markup barely changes. The ownership does.