25 WordPress form plugins to choose according to your needs

Start with the form you actually need

You want to receive an inquiry, collect an application or calculate a quote. These three goals do not necessarily require the same tool. Before comparing templates and visual effects, write down what should happen after submission: who receives the message, where the response is stored and how your team finds it. A form that is pleasant to complete is still insufficient if no one can use its result.

First examine the features already available on your site. An installed builder, an existing plugin or your platform may already meet the need. WordPress.com, for example, offers forms among its built-in features. Checking what already exists avoids adding a second data collection process and needlessly rebuilding a page. An email delivery failure is also not sufficient reason to replace the form immediately.

This documentation-based selection brings together twenty plugins available to download free from WordPress.org and five paid products offered on CodeCanyon. Each product family is counted only once: a free edition and its professional version do not become two artificial recommendations. The order follows needs, without scores, rankings or a promise of universally better results. Contact Form 7 underwent local validation and notification capture acceptance tests, described below. The other products are compared based on their documentation; SMTP delivery and visual workflows are not validated by these tests.

• For a contact message, start with a short workflow containing a reply address, a useful subject and a message.
• For a submission or application, define the required attachments, the people authorized to view them and their retention period.
• For a quote or payment, separate the displayed calculation, acceptance of the terms and actual transaction confirmation.

Criteria that help distinguish these plugins

A useful choice rests on a few concrete constraints: how you build pages, essential fields, access to responses, protection against abusive submissions and the full budget. A product’s presence in a directory is not a security or accessibility certification. The features mentioned below come from official listings; their operation with your theme and other components still needs to be checked.

Conditional logic here means rules that show or hide a question based on an earlier answer. It avoids some unnecessary questions but also makes the workflow harder to check. A multistep form spreads questions across several screens; it does not guarantee more responses. Choose these features because your process requires them, not to reproduce a sales demonstration.

A general-purpose tool often suits several needs, while a calculation specialist or builder module fits a more specific context. Compatibility advertised by a seller does not mean all future versions are covered. Before installing, record the WordPress and PHP requirements of the version actually downloaded, its dependencies, changelog and support terms. Unverified compatibility is not presented as established.

• Prefer an existing feature when the site can already handle your request correctly.
• Then compare a suitable free solution with a more comprehensive one, using the same scenario rather than their total number of fields.
• Rule out a plugin whose dependency, license or data handling does not suit your organization.

Simple contacts and general-purpose visual builders

VS Contact Form, Contact Form 7 and Contact Form by BestWebSoft represent three approaches to a simple contact form. Happyforms and WPForms put more emphasis on visual assembly. Choose based on settings you understand and can maintain. A starting template never removes the need to review recipients, required fields and the confirmation text.

Ninja Forms, Everest Forms, Fluent Forms, WS Form LITE, weForms, IvyForms, Form Maker and Bit Form cover needs that may grow. They do not necessarily include the same features in their free versions. Before migrating, list the features actually needed: exporting responses, accepting a file or displaying a conditional question may be enough to change the project’s cost.

Do not automatically transfer all old fields to the new tool. An old request for a postal address may no longer be useful. However, keep a copy of the old forms and the responses needed for your activity. Until the new workflow has been checked, avoid deleting the old plugin and losing the only access to its history.

Stay in the editor or a builder you already use

Gutena Forms and Jetpack Forms are aimed in particular at sites working with the block editor. MetForm serves a different context: it relies on Elementor. This dependency may make sense on a site already built with Elementor, but adding a builder solely for a small form changes the decision considerably. Site consistency matters more than the appeal of an isolated template.

The form appears on a page, but its settings, responses and notifications may be managed elsewhere. Identify these three locations before handing maintenance to someone else. Also check access rights: the person editing page text does not necessarily need to view applications or export all collected contact details.

Questionnaires, quotes and complex workflows

Forminator, FormGent and Formidable Forms broaden the comparison to questionnaires, conditional workflows and using responses. Calculated Fields Form particularly targets forms whose results depend on calculations. A quote calculator remains a presentation of your business rules: neither the plugin’s name nor a plausible-looking result proves those rules are correct.

The selected CodeCanyon offerings are Quform, ARForms, eForm, FormCraft Premium and Cost Calculator by QuanticaLabs. They serve different needs: control of a complex form, presentation, surveys or estimates. A paid license does not guarantee that no additional modules are needed. Read the listing for the exact product, and do not confuse a marketplace license with an Envato Elements subscription or a download redistributed by a third party.

A booking request form does not guarantee that a slot is available. Likewise, collecting a registration does not necessarily create a member area, and displaying a total does not constitute a WooCommerce order. Whenever the need involves stock, availability, cancellations or lasting access rights, also compare a solution from the specialized category instead of relying entirely on a general-purpose form.

Understand pricing without confusing free access with no costs

The free download applies to the named plugin, not to every service it can connect. Payment providers, email services, abuse protection and marketing tools may have their own terms. Amounts for professional plans that have not been recorded remain explicitly unknown. It is better to retain this limitation than publish a promotional price without knowing what it becomes at renewal.

The CodeCanyon prices recorded correspond to the displayed Regular license in US dollars, excluding taxes and processing fees indicated by the marketplace. They are not the final amount applicable in your country. Check that the license suits your usage and intended number of sites. Time-limited support must not be confused with a promise of unlimited maintenance; a contradiction in a listing is flagged rather than resolved by assumption. eForm is marked 100% GPL: commercial support terms do not replace the software license.

Prepare checks before going live

On a working copy with its own configuration, prepare tests using fictional data. Disable real recipients, marketing signups and payments before submitting a request. A site copy may still retain production connections. You need to know who receives each notification and which service receives information before starting.

Check separately what the person sees and what the team receives. An onscreen success message is not proof of delivery to the expected inbox. When local storage is provided, find the response in the administration interface and examine access rights. When it is not, decide how to prevent an email error from losing an important inquiry.

Attachments require particular care. Limit formats and sizes to the stated purpose; determine where files are stored, how they are viewed and when they are deleted. Never treat a simple consent checkbox or a GDPR marketing claim as automatic compliance for the entire site. Collection must remain proportionate and understandable.

Finish with the mobile workflow, keyboard navigation, labels, errors and confirmations. If a field becomes invisible, the person must still understand what is being asked. Note the limitations observed with your theme. The next two sections describe a local validation and capture acceptance test with Contact Form 7. The other offerings still need to be tried on your copy.

• Keep an appropriate backup and the available form export before replacing anything.
• Validate a normal scenario, an incomplete entry and a rejected file, without real personal data.
• Check recipients, storage and connected services before authorizing launch.

Create a callback form and test the attachment

On a local copy, open Contact, then Contact Forms. Create a form called “Rappel local”. Add a required name, email address and message. Use the tags [text* your-name], [email* your-email] and [textarea* your-message] within visible labels. For the optional attachment, use [file document filetypes:pdf limit:32kb]. The 32 KB setting makes the limits easy to check with a fictional document.

In the Mail tab, set reception@example.test as the recipient. Use a sender address consistent with your copy’s domain. In the additional headers, enter Reply-To: [your-email]. Under “File attachments”, enter [document]. The form field and attachment tag must use the same name. Write the subject “Rappel [your-name]” and put [your-message] in the body.

Insert the form on a test page, then simulate five situations. An empty address must flag the email field. The TXT must flag the attachment. A small PDF must reach the notification, and a submission without a file must pass. To observe a transport failure without sending a message, deliberately return a failure from your local capture.

The acceptance test used WordPress 7.1.4 and Contact Form 7 6.2.4.1. Five multipart HTTP requests were replayed over local loopback. The two invalid inputs were rejected before the send point. The other three reached it with the expected recipient, subject and reply address. The PDF fingerprint matched the uploaded file. The simulated failure returned mail_failed. The capture hook intercepted all three notifications before any actual sending.

• Submit the form without an email address, then check the field flagged by the response.
• Try a fictional TXT and then a PDF. Check the PDF’s presence and fingerprint at the send point.
• Try without an attachment and check that the prepared email has no attached file.
• Simulate a rejection at the send point and check that the form returns a failure.

Distinguish a prepared message, a delivered message and a retrievable inquiry

The mail_sent response in this acceptance test means the local capture accepted the notification. To verify delivery on a site, open a controlled test mailbox and check the message, its folder and its reply address. If a form is blocked, compare the network response first, then the transport log. Avoid repeatedly retrying a message while the outcome of the first attempt is unknown.

If the team needs to find inquiries without email, choose a form that stores entries or an add-on designed for that purpose. Contact Form 7 alone does not retain a submission history. Flamingo is one possible add-on. Storage of responses or attachments by Flamingo is outside this acceptance test. Check the entries screen, access by an account with reduced permissions and removal of a test inquiry separately.

Also examine intermediate files. On the tested Windows copy, the PDF was still present as read-only in Contact Form 7’s temporary directory after the request. The script deleted it after observation. This result concerns the local configuration tested. On your hosting, check the temporary directory and permissions after each trial using a fictional document.

Finally, open the form on a phone and navigate it with the keyboard. Check that fields with errors can be identified and that focus remains useful. These visual checks, SMTP delivery, abuse protection and data retention remain separate tests.

• Keep separate records of the form response, captured notification and stored entry.
• Confirm on a copy who can read, export and delete an inquiry.
• Replay the form with the actual theme before exposing it to visitors.

Prepare a quote request the team can process

Consider an agency receiving requests for showcase sites and catalogs. On the Showcase page, ask for a reference or project name, a reply email, a page count and a deadline. On the Catalog page, ask for a product count instead. The team then receives the quantity relevant to its quote. Leave any pricing and commercial approval for the team’s response. If you display an estimate, explain the factors that may change it.

Before configuring notifications, write down who receives each service request and who takes over if that person is absent. Prepare two fictional records, DEMO-VIT-01 for a five-page showcase site and DEMO-CAT-02 for a thirty-product catalog. Use camille@example.test and noa@example.test and a capture mailbox. The acknowledgment must state the next step, such as a response after review. Keep the same reference in the acknowledgment and the team’s inbox.

Test two quote forms with fixed recipients

With Contact Form 7, create “Devis Vitrine” and “Devis Catalogue”. Add the fields [text* project-reference] and [email* contact-email] to both forms. For the test quantities, use [number* project-count min:1 max:30] for the showcase site and [number* project-count min:1 max:500] for the catalog. Add [select* project-deadline "Ce mois-ci" "Souple"] and keep a visible label for every field. Place each form on its service page and check the link from the service listings.

In each form’s Mail tab, enter the fixed address of the team handling the service. For the test, use vitrine@example.test and catalogue@example.test. Keep a sender from the copy’s domain and add Reply-To: [contact-email]. Insert [project-reference], [project-count] and [project-deadline] in the notification. For a separate acknowledgment, enable Mail (2), address it to [contact-email] and include [project-reference] in the subject.

On our WordPress 7.1.4 copy with Contact Form 7 6.2.4.1, both valid requests reached their team mailbox and each produced an acknowledgment in the requester’s fictional mailbox. A missing email and a zero quantity were rejected before notification. A simulated rejection at the capture point returned a failure and deposited no additional message. The mailboxes were written on the copy before any SMTP transport.

• Check that the showcase request reaches only the Showcase team and the catalog request only the Catalog team.
• Review the reference, quantity, deadline and reply address in the notification. Find the same reference in the acknowledgment sent to the requester.
• Using the actual theme, replay both pages with the keyboard and on a phone. Check the error display when a quantity is missing or outside the range.

Adapt the workflow to a single form with routing

When requests arrive on the same page, use a service selector and display the fields corresponding to the answer. In Fluent Forms Pro, the publisher documents a conditional routing setting for notifications. Configure both team addresses in the administration interface and link each rule to a precise value in the Service field. Prepare a control notification if your tool allows it, or check that any service without a rule remains identifiable in the stored entries.

On the copy, switch from Showcase to Catalog immediately before submitting. Check that the expected quantity is the catalog quantity and that the notification contains the fields for the selected service. Replay a value that does not match the options configured in the test interface. The result must allow the request to be found or the selection to be corrected. This second approach is documented by the publisher. Replay it in the edition and configuration you use.

Before launch, ask the team to find a request without starting from the email, if you have enabled entry storage. Keep a record of the reference, target mailbox and result. On a staging site connected to test transport, then open the actual control mailbox to check the final leg. If the project calculates an amount before submission, also compare the quote calculators in the preparation links.

Further reading

• Contact Form 7 rejects an attachment
• WPForms rejects a submission with corrupted post data
• Make WordPress form fields and errors understandable
• Compare WordPress quote calculators