WPForms
WPForms sells ease of use, and delivers it. The paid tiers are structured so that the feature you actually need is usually one level above the one you were about to buy.
WPForms competes on the interface, not the feature list. The builder is genuinely the most approachable in the category, the templates cover the common cases, and a non-technical person can build a working form in a few minutes without asking anyone. That is worth money on a site where the person maintaining forms is not a developer.
What you are buying is that experience. Everything below is about what it costs and where the boundaries fall.
The free tier, honestly
WPForms Lite gives you the builder, standard fields, email notification and spam protection. It does not store submissions.
That single omission defines the free tier. A form that only emails is a form whose enquiries vanish when mail fails — and mail failing is the single most common problem on WordPress sites, as contact form not sending email and WordPress not sending emails describe at length. Lite is adequate for a plain contact form on a site with working SMTP, and thin for anything else.
How the tiers are arranged
Paid levels stack roughly like this:
| Level | Typically adds |
|---|---|
| Entry level | Stored entries, conditional logic, file uploads, multi-page forms |
| Mid | Marketing platform integrations, payment fields |
| Higher | Surveys and polls, advanced payment options, user registration |
| Top | The full add-on set, more sites, priority support |
The pattern to notice is that the features people most often need — conditional logic, then a payment field, then one specific integration — are spread across three levels. Buying the cheapest paid tier and upgrading twice is the common outcome and costs more than choosing correctly once.
So do this before purchasing: write down the one feature that makes the free version insufficient, find the tier that contains it, and buy that. Licences are annual, and the renewal is the number that matters over a site's life.
Stored entries are an obligation
Once entries are saved, you hold personal data.
- Set a retention period and actually apply it. Four years of enquiries in a database is a liability, not an archive.
- Be able to delete one person's submissions on request.
- Say so in the privacy notice — that submissions are stored, why, and for how long.
- Protect the table as part of ordinary security; a compromised site exposes it along with everything else.
This is not WPForms-specific. Every storing form plugin creates it, and Forminator makes the same point. It is worth repeating because "entries are saved" is sold as a feature and rarely presented as a duty.
Payments in a form, and their limit
The payment fields handle one-off charges cleanly — a booking fee, a donation, a fixed-price service. They do not handle stock, tax rules, shipping, order management or refunds.
The line is simple: if the thing being sold has inventory or variable tax, it belongs in a store, per ecommerce plugins. If it is a single fixed amount attached to an enquiry, a form is the lighter answer and avoids installing a shop for one button.
Spam, and not stacking defences
WPForms includes a honeypot and supports the usual captcha services and filters. Pick one.
A honeypot plus a captcha plus a third-party filter adds friction and latency to solve a problem any one of them handles. The trade-offs are in adding reCAPTCHA and, for hosted filtering, CleanTalk and Akismet.
How it compares
| Plugin | Character |
|---|---|
| WPForms | Easiest builder, tiered licence, polished |
| Forminator | Free, includes logic and payments, heavier |
| Contact Form 7 | Free, minimal, markup-based, no storage |
The honest reading: if budget is the constraint, Forminator does most of what an entry-level WPForms licence does for nothing. If the person building forms is non-technical and their time has value, WPForms is easier and that is a real product. If you want the smallest possible footprint and will write markup, Contact Form 7 remains the light option. The category view is in contact form plugins.
Performance
Form plugins add front-end assets to pages carrying a form, and sometimes to pages that do not. On a site with one contact page that is negligible. On a site with a form in the footer sitewide, it is a sitewide cost worth measuring against speeding up WordPress.
Common mistakes
- Buying a tier below the feature you need, then upgrading twice.
- Relying on notification email alone, on Lite, on a site that cannot send mail.
- Keeping entries forever with no retention policy.
- Building a shop out of payment fields.
- Three spam defences at once.
Deciding
Buy WPForms when a non-technical person owns the forms and the interface is the thing you are paying for — that is a legitimate reason and the plugin delivers it. Choose a free alternative when the budget matters more than the polish, since the functional gap is smaller than the price difference suggests. Either way, fix email deliverability first: the best form builder in the world is useless on a site whose mail does not arrive.
Frequently asked
- A drag-and-drop builder, basic fields, email notifications and spam protection. It does not store submissions, and conditional logic, file uploads, payments and integrations are all paid — so the free tier suits a plain contact form and little else.
- Work backwards from the one feature you cannot do without — conditional logic, payments, a specific integration — and buy the tier containing it. The tiers are arranged so that guessing usually lands you one level too low.
- In the paid tiers, yes — submissions are saved to your database as well as emailed. That protects you from lost enquiries when mail fails, and it makes you the holder of personal data with retention and deletion obligations.