Forminator

Forminator's distinguishing feature is what it does not charge for. Conditional logic, calculation fields, payment fields, file uploads, quizzes and polls are in the free plugin, and in most competing form builders at least half of that list is behind a licence. If your requirement is a form with logic and a payment field and no annual cost, this is the short answer.

What you get

• A visual form builder with a broad field set and drag-and-drop layout.
• Conditional logic on fields and on submission behaviour.
• Calculations, which is what quote and booking-enquiry forms actually need.
• Payment fields through the common gateways, for simple one-off charges.
• Quizzes and polls, which are separate content types rather than form types.
• Submission storage, export, and email notifications.

The calculation field is the genuinely useful one. "How much would this cost" forms are a common request and are otherwise either a paid tier or a custom build.

The obligation that comes with stored entries

Entries are saved to your database by default. That is convenient — nothing is lost when email fails — and it makes you the holder of a growing store of personal data.

What that means in practice:

• Retention. Enquiries from four years ago are still there unless someone deletes them. Decide a retention period and actually apply it.
• Deletion requests. You need to be able to find and remove one person's submissions.
• Disclosure. Your privacy notice should say that submissions are stored, for how long, and why.
• Security. A database table of names, emails and messages is worth protecting — see the security checklist, and note that a compromised site exposes this table along with everything else, as fixing a hacked site describes.

None of this is Forminator-specific; every storing form plugin creates it. It is worth stating because "the entries are in the database" is treated as a feature and rarely as a responsibility.

Email is still the thing that breaks

The most common form complaint has nothing to do with the form plugin: notifications do not arrive. WordPress sends mail through PHP by default, and receiving servers increasingly refuse mail sent that way.

Stored entries protect you from silently losing enquiries, which is a genuine advantage over plugins that only email. But you still need working delivery — contact form not sending email and WordPress not sending emails cover the fix, which is an SMTP route rather than anything in the form builder.

Spam handling

Forminator supports the usual defences: honeypot, captcha services, and integration with spam filters.

Choose one. Stacking a honeypot, a captcha and a filtering service adds friction and latency for a problem one of them solves. The comparison is in adding reCAPTCHA to a form, and the third-party filtering trade-off is the same one described in CleanTalk and Akismet.

Performance, measured rather than assumed

Forminator loads its own CSS and JavaScript, and historically has been less careful than minimal plugins about loading only where a form exists. On a page with a form that is unavoidable; on a page without one it is waste.

Check what a form page loads before and after, using the approach in speeding up WordPress. A site chasing render-blocking resources should know which of its plugins contributes.

How it compares

The honest split: Contact Form 7 for a developer who wants a small footprint and will write the markup, Forminator for a site owner who wants logic and payments without a licence, and a commercial builder when integrations and support are worth paying for. The category overview is in contact form plugins.

Common mistakes

• Leaving entry storage on forever with no retention policy.
• Relying on notification email alone on a site that cannot send mail reliably.
• Building a payment flow in a form that really needs a proper checkout — for anything beyond a one-off fixed charge, see ecommerce plugins.
• Placing a form in the footer sitewide and paying its asset cost on every page for a form nobody uses.
• Three spam defences at once, which is friction without additional protection.

Deciding

Forminator is the strongest free option when you need logic, calculations or a simple payment field and do not want an annual licence. Prefer a minimal plugin when the form is three fields and the site's weight budget is tight. Prefer a commercial builder when deep CRM or marketing integrations are the point. And whichever you choose, decide how long you keep submissions before the table has four years of them in it.