Forminator is unusually generous for a free WordPress plugin. Payments through Stripe and PayPal, conditional logic, repeatable field groups, multi-file uploads, quizzes and polls: all of it ships in the version on the plugin directory, with no upgrade prompt blocking the field you actually need. That is why it keeps turning up on shortlists, and why the honest question about it is not whether the free tier is real. It is.
The question worth asking is what happens on the tenth submission of the week, when someone has to work out which ones have been answered, who is answering them, and what was said. That part is not a form building problem, and it is where the shape of this plugin starts to matter.
What the free plugin actually covers
Forminator is published by WPMU DEV and sits at 600,000 or more active installations on the WordPress plugin directory, with a 4.8 out of 5 rating across 2,131 reviews. Version 1.57.3 was released on 17 September 2026, requires WordPress 6.4 or higher and PHP 7.4 or higher, and has been translated into 23 locales.
The free feature list is long enough to be worth reading properly rather than skimming. Payments are the headline: Stripe and PayPal integrations are included at no cost, both built to follow the EU Strong Customer Authentication rules, and the Stripe Dynamic Payment Element exposes more than 40 payment methods including Apple Pay, Google Pay and Klarna. Most plugins put card payments behind a licence. This one does not.
Beyond payments, the free build includes conditional logic, calculation fields, a field group feature that lets a respondent add repeatable blocks such as employment history or a list of attendees, multi-file uploads with per-type and per-size limits, and date picker restrictions that can be narrowed to future dates only, a fixed range, or particular days of the week. Anti-spam covers reCAPTCHA, hCaptcha, Cloudflare Turnstile, honeypot fields, email and domain filters, and Akismet. There is a Gutenberg block, front-end post submission, custom login and registration forms including multisite, an import wizard for Contact Form 7 data, email routing with conditions, and query-string pre-population.
Integrations in the free build include Google Sheets, HubSpot, Mailchimp, ActiveCampaign, AWeber, Campaign Monitor, Trello, Slack, and plain webhooks that reach n8n, Zapier and Make. Quizzes and polls are separate form types rather than field tricks, with live poll results rendered as charts.
Nothing in that list is a trial. For a site that needs a contact form, an order form and a poll, the free plugin is a complete answer.
Where the paid line falls
Four features are marked Pro on the WPMU DEV product page: PDF generation from submissions, geolocation with address autocomplete, Stripe subscriptions for recurring payments, and the e-signature field. Pro templates and cloud templates synced through the WPMU DEV Hub also sit on the paid side.
Pricing is not a per-plugin licence. WPMU DEV sells site-count plans that carry the whole Pro plugin suite, and Forminator Pro comes inside them.
| Plan | Sites | Price | Includes |
|---|---|---|---|
| Pro Basic | 1 | $50 per year | Full Pro plugin suite |
| Pro Standard | 3 | $75 per year | Full Pro plugin suite |
| Pro Plus | 10 | $100 per year | Full Pro plugin suite |
| Premium | Unlimited | $9.99 per month | Suite plus hosting benefits, CDN, backups, seats |
A 30-day money-back guarantee applies. The company's own pricing FAQ confirms that buying a single plugin still hands over the full Pro suite for 1, 3 or 10 sites, which means the practical entry price for the e-signature field or the PDF generator is $50 a year rather than anything plugin-specific.
Read that table as a site licence, because that is what it is. The cost scales with how many WordPress installations carry the plugin, and not at all with how many people in the organisation log in to read what came through. For a small site with a large team, that is favourable. For an agency with many sites and one coordinator, less so.
The submissions screen, and the work it hands back
Forminator stores submissions in the WordPress database and gives them a screen where they can be sorted, filtered and exported. Version 1.57.0 added a custom Submission ID per form along with a prefix setting, which helps when a submission number has to be quoted back to a person. Notifications go out by email on submit, and auto-response can send the respondent a copy of what they wrote.
That covers collection. It does not cover the handling.
There is no owner on a submission. Nothing in the record says which member of staff took responsibility for it, so on any team with more than one person reading the inbox, that fact lives in a chat message or in nobody's head. There is no status either. A submission that has been dealt with and one that has been sitting for four days look the same in the list unless somebody invents a convention, and conventions that depend on memory fail during the weeks when volume goes up.
The reply is the sharper gap. Auto-response handles the templated acknowledgement well. An individual message, the one written to a particular applicant about a particular detail, is composed in a mail client. Once that happens, the record of what was said is in a sent folder belonging to one person, and the WordPress screen showing the submission has no idea it exists. Six weeks later, when the person emails back asking about the thing they were told, the history has to be reconstructed from two places.
This is not a defect in the plugin. A form builder that builds forms and stores what they collect has done its job. It is a boundary, and it is worth naming because a lot of the friction people attribute to the plugin is actually the work sitting on the other side of that boundary.
The spreadsheet workaround and its half-life
The usual response is to export. Submissions come out as a file, or the Google Sheets integration appends each new response as a row, and status and owner columns get added by hand in the sheet. For a short intake with a fixed deadline this is fine, and pretending otherwise would be precious.
It degrades in two predictable ways. The sheet and the plugin drift apart, because a submission edited in WordPress does not update the row and a row edited in the sheet does not update the submission, so within a fortnight there are two versions of the truth and no rule about which one wins. And the same person who owns the row still has to write the reply somewhere else, so the sheet records that a response was handled without holding what was said. That is the point at which the workaround has stopped saving time and started generating questions, and it is a better signal to act on than any feature comparison.
Email routing is not the same as a reply log
Forminator's conditional email routing is the feature most often reached for when this gap appears. It sends different notification emails to different teams based on what the respondent selected, which does solve the sorting problem at the moment of arrival.
What it does not do is close the loop. Routing moves the notification. The reply still leaves from whichever mailbox the notification landed in, so the answer to "has this been dealt with" remains a question you ask a colleague rather than a column you read. Teams usually paper over this with a shared mailbox and a rule that whoever replies also replies to the group. It works until someone is on holiday.
Deliverability deserves a mention here too, because it is the same shape of problem. Notification and auto-response mail sent by a WordPress install goes out through the hosting server unless an SMTP layer is added, and inbox providers have become strict about authentication. A missing acknowledgement looks identical to a submission that never arrived, and the time spent diagnosing that is real.
Counting the cost on the right axis
Pricing models are worth comparing directly, because the wrong axis makes a cheap tool expensive.
| Priced by | What grows the bill | What stays free |
|---|---|---|
| Site licence | Number of WordPress installs | People reading submissions |
| Submission volume | Responses per month | Sites and seats |
| Seats | People who need access | Forms and responses |
Forminator sits in the first row. A team of fifteen on one site pays $50 a year. That is the best case for a site licence, and if the situation matches it, the maths is hard to beat.
The awkward case is the other direction. Where submissions need to be worked on by several people who each need their own view of what is theirs, the constraint is no longer licensing. It is that a WordPress admin screen is a place to look at records, not a place to run a queue. Some teams solve it inside WordPress with a workflow plugin on top. Others move the handling to a tool built for it and keep WordPress for the pages. Either way the decision is about where responses get worked on, which is worth thinking through against the use cases that actually apply before comparing feature grids.
Security cadence and what self-hosting means
Anyone evaluating a self-hosted form plugin should look at its changelog, and Forminator's is instructive. Between 18 August and 17 September 2026, the plugin shipped a run of security releases: cross-site scripting fixes, a PHP object injection fix, a privilege escalation fix, a multisite registration issue, and a payment processing issue. WPMU DEV runs disclosure through the Patchstack programme and credits reporters by name in the log.
The right reading of that is not alarm. A plugin with 600,000 installations that handles payments and file uploads is a target, and a vendor publishing fixes quickly with named credits is behaving correctly. Support responsiveness backs that up: the plugin directory records 61 of 68 support issues resolved in the last two months.
The reading that matters operationally is different. Every one of those releases is an update that somebody has to apply, on every site, reasonably promptly, because the submission data sitting in that database includes whatever the forms collect. That is the standing cost of self-hosting a form plugin, and it does not appear on any pricing page. A hosted tool moves that work to the vendor. A plugin keeps it with you, in exchange for the data staying on your own server. Neither answer is wrong, but the choice should be made deliberately rather than discovered during a security release on a Friday.
What to change first
Take last month's submissions and count two numbers: how many there were, and how many individual replies were typed by a person in response. If the second number is close to the first, the form is working and the handling is the bottleneck, and no plugin setting will fix that. Put the submission and the reply in one place, keep the owner and the status on the response itself, and check any candidate against how it prices access rather than how many fields it offers, which is the axis Halict is built around.
Q1. Is Forminator really free, or is the useful part behind Pro?
The free plugin includes Stripe and PayPal payments, conditional logic, calculations, repeatable field groups, multi-file uploads and all the anti-spam options. Four things are Pro only: PDF generation, geolocation with address autocomplete, Stripe subscriptions for recurring payments, and the e-signature field. For most contact, order and application forms the free build is complete.
Q2. How much does Forminator Pro cost?
It is not sold as a standalone plugin licence. WPMU DEV plans start at $50 per year for one site, $75 for three sites and $100 for ten sites, and each includes the entire Pro plugin suite rather than Forminator alone. Premium covers unlimited sites at $9.99 per month. A 30-day money-back guarantee applies.
Q3. Can several people manage Forminator submissions without stepping on each other?
The submissions screen has no owner field and no status field, so there is nothing in the record that says who took a submission or whether it has been answered. Teams usually add a convention in a chat channel. That works at low volume and tends to break when submissions arrive faster than someone can watch them.
Q4. Does Forminator send the reply to the person who submitted?
Auto-response sends a templated acknowledgement with a copy of the answers, and conditional email routing delivers notifications to different teams. A message written individually for one person is composed in a mail client, so the record of that reply stays in a sent folder rather than next to the submission.
Q5. Should the number of security releases in the changelog be a concern?
Fixes shipping quickly with named reporters is the behaviour you want from a vendor, and Patchstack disclosure is a good sign rather than a bad one. The practical consequence is operational: each release has to be applied on every site holding submission data, and that update work is part of the true cost of running a self-hosted form plugin.