Contact forms give customers, readers, and potential clients a way to contact you without publishing your email address. A simple form may need only a name, reply address, and message. A quote request or booking form may need conditional fields, file uploads, or integrations.
The right plugin depends on what you need to collect, whether submissions should be saved in WordPress, and how you will make sure notifications arrive. The options below are a practical shortlist, not a ranking based on hands-on testing. Free and paid features can change, so check the current plugin listing and plan details before installing.
What to check before choosing a plugin
- Fields and workflow: Decide whether you need a basic contact form or extras such as conditional questions, payments, file uploads, or connections to other services. Avoid collecting fields you do not need.
- Notifications: A form plugin usually hands mail to WordPress; that alone does not guarantee delivery to an inbox. The WordPress
wp_mail()reference explains the mail function. Send test submissions to an address you can access, check spam folders, and configure a reliable mail service if your host’s default delivery is unreliable. - Submission storage: Decide whether a copy should be kept in the site’s database or sent only by email. Stored messages can help recover missed notifications, but they also create data that needs access controls, retention limits, and a deletion process.
- Spam and privacy: Use proportionate spam controls and review whether features send visitor data to an outside service. The WordPress privacy guide explains the site’s responsibility to disclose what it collects and shares. You may also want our guide to anti-spam plugins for WordPress.
- Accessibility and compatibility: Use visible, descriptive labels and instructions; check keyboard operation, validation errors, success messages, zoom, and a narrow screen. The W3C forms tutorial explains how labels identify controls. Check the plugin’s current WordPress and PHP requirements before activating it.
Contact Form 7
Contact Form 7 is a free option for a straightforward form when you are comfortable editing its form and mail settings. Its tag-based setup offers control without requiring a visual drag-and-drop builder. The tradeoff is that you need to understand the fields and notification configuration you create.
Contact Form 7 does not save submitted messages by default. If you need a local copy, its companion plugin Flamingo stores submissions in the site’s database. That can help when email fails, but it means the site now retains personal information. The Contact Form 7 plugin listing links to its privacy notices; review them before enabling integrations such as anti-spam or CAPTCHA services, which may send data to third parties. For conditional fields, the separate Conditional Fields for Contact Form 7 plugin is one option, and should be checked for compatibility like any add-on.
WPForms Lite
WPForms is a visual builder for people who prefer arranging fields in an editor instead of writing form markup. The WordPress.org listing describes the free Lite plugin and features available with its paid version. Before choosing it, compare the exact current Lite and paid feature lists, especially for submission storage, integrations, and fields you plan to use. Treat email notifications as something to test on your own site rather than an automatic guarantee of delivery.
Jetpack Forms
If Jetpack is already connected to your site, its Form block is a convenient way to add a basic form in the WordPress block editor. Jetpack says the block is free on Jetpack-connected sites. It is a good starting point when you want to avoid adding another form-builder plugin; it is less compelling if you do not use Jetpack or need a specialized workflow. Check the current guide and plugin listing for the editor and form features it supports.
Fluent Forms
Fluent Forms offers a drag-and-drop builder and a broader set of form fields than a basic contact form needs. Its current WordPress.org listing describes free features including conditional logic, email notifications, entry exports, and several spam-protection integrations; other fields and integrations are listed as Pro features. Confirm the current free-versus-paid boundary before building a form around a feature you may later need to upgrade for.
Forminator
Forminator is another visual builder to consider if you want forms alongside polls or quizzes. Its WordPress.org listing describes a free plugin with several form types and integrations. Check the current listing and settings for the specific fields, spam controls, payment features, and data handling you need; a long feature list does not mean every service or integration is appropriate for a simple contact form.
HTML Forms
HTML Forms takes a developer-oriented approach: you write the form’s HTML, and the plugin handles submission processing and configured actions. Its plugin listing says submissions are saved by default and can trigger actions such as email notifications. This gives you control over the markup, but you are responsible for making labels, validation, errors, and the submitted-data lifecycle usable and accessible.
Other options from the earlier list
The original article also linked to Formidable Forms, Kali Forms, and weForms. Their WordPress.org listings were available when this article was reviewed. They are alternatives to evaluate, not a feature-by-feature ranking here; compare their current free and paid limits, updates, support, and data-handling details against your requirements.
The previous list included two options that need extra caution for a new site. WordPress.org currently says Visual Form Builder is closed and unavailable for download pending a review. The FormCraft directory plugin says it has not been tested with the latest three major WordPress releases. Do not treat either as a current recommendation without confirming its status and compatibility with the maintainer.
Choosing between free and paid versions
Start with the least complex option that meets the form’s real requirements. A basic contact form rarely needs payment fields, a marketing automation suite, and multiple anti-spam services. Consider a paid plan only when a specific requirement—such as conditional workflows, file uploads, integrations, or support—justifies its cost. Confirm whether the payment recurs, what happens to forms and stored entries if a license expires, and whether the plan covers the sites where you will use it.
The source article also included these paid marketplace links. They are retained from the earlier version for continuity, not presented as current endorsements. Check each listing for the latest release, support status, license terms, compatibility, and total cost before buying. The links are affiliate links.
Quform
View the retained Quform marketplace listing.
eForm
View the retained eForm marketplace listing.
MagicForm
View the retained MagicForm marketplace listing.
FormCraft Premium
View the retained FormCraft marketplace listing.
Test the form before relying on it
- Make a backup or use a staging site before installing or replacing a form plugin.
- Submit a test from a keyboard and a phone-sized screen. Check field labels, required-field instructions, validation errors, and the success message.
- Confirm that the notification reaches the intended mailbox and that replies go to the submitter when expected. Do not put the visitor’s address in the sender field; use an address on your own domain and configure mail delivery for your site.
- If submissions are stored, confirm who can view them, how long they are kept, and how a person can request a copy or deletion. Remove test entries afterward.
- Add only the spam controls you need. Check the privacy notices for any CAPTCHA, analytics, or marketing integration that sends information to another service.
For a small site, the simplest useful choice is often Jetpack Forms if Jetpack is already in use, Contact Form 7 if you want a lightweight configurable form, or a visual builder such as WPForms Lite, Fluent Forms, or Forminator if you prefer an editor. Developers who want to control the HTML can also evaluate HTML Forms. Whichever you choose, test delivery and decide deliberately whether visitor messages should be stored.