This post used to review Ultimate Form Builder by Access Keys. That plugin was closed on WordPress.org in March 2023 for a guideline violation and hasn’t been available since, if you’re running it, it’s not receiving security updates and should be replaced. Rather than leave a review of a dead product up, here’s Fluent Forms, a free drag-and-drop form builder that covers the same ground and is actively maintained.
Before getting into what it does, it’s worth being direct about what a “closed for guideline violation” plugin actually means for anyone still running it. WordPress.org pulls plugins from the directory for a range of reasons, security vulnerabilities discovered and not fixed, misleading marketing, undisclosed data collection, licensing disputes. Whatever the specific reason here, a closed plugin stops receiving updates through the normal channel, which means any vulnerability found after closure never gets patched. A form builder specifically handles user-submitted data, names, emails, sometimes payment or sensitive information depending on what the form collects, which makes it a genuinely bad plugin category to be running unpatched. If you’re on the old plugin, treat this as more urgent than a typical “nice to update eventually” situation.
What Fluent Forms handles
Contact forms, quotation requests, surveys, feedback, file uploads, booking forms, multi-step forms, conditional forms, the same range of form types the old plugin promised, built with a drag-and-drop editor rather than hand-coded fields.
Free version
- Unlimited forms, with a drag-and-drop builder
- Standard field types: text, textarea, email, dropdown, radio, checkbox, number, and more
- Conditional logic for showing and hiding fields based on earlier answers
- Basic payment field support
- Entry storage and management inside WordPress, with export
- Spam protection built in
The unlimited-forms detail is worth flagging since it’s not universal in this plugin category, several competing form builders cap the free tier at a small number of active forms and push you to upgrade the moment you need a fourth or fifth form on the site. Fluent Forms not gating form count on the free tier means a site with several distinct forms, a general contact form, a quote request form, a job application form, doesn’t need to pay anything just to have that many active simultaneously, the paid tier gates deeper functionality rather than raw form count.
Pro version
- 55+ input field types, including advanced UI elements (date pickers, sliders, ratings)
- Multi-step forms with progress indicators
- 60+ third-party integrations (email marketing, CRMs, payment gateways)
- Advanced conditional logic across display, email routing, and redirects
- Quiz and survey-specific field types
- Multi-column layouts
700,000+ active installs, updated within the last few days as of this writing, among the more actively developed form builders on WordPress right now.
Migrating From the Old Plugin
If you’re coming from Ultimate Form Builder or any other discontinued form plugin, there’s no automatic import path between unrelated plugins, form structures, field configurations, and stored entries are generally plugin-specific and don’t transfer cleanly. Plan on rebuilding your forms manually in Fluent Forms rather than expecting an import wizard to handle it. For existing form entries already stored in your database from the old plugin, export what you can before deactivating it, since a plugin closed on WordPress.org can still be deactivated and even reactivated locally from a downloaded copy if you already have the files, but you can’t reinstall it fresh from the directory once it’s been pulled. Do this export step before removing the old plugin entirely, not after, since recovering data from a fully removed plugin’s custom tables is a much harder problem than exporting it while the plugin is still active.
Spam Protection in More Detail
The built-in spam protection on the free tier is worth understanding rather than just trusting blindly. Fluent Forms includes honeypot fields (invisible fields that trip up bots but stay hidden from real visitors) by default, and supports Google reCAPTCHA and hCaptcha integration for forms that need a stronger layer, a public contact form that’s become a spam magnet, for instance. Honeypot alone handles a meaningful share of basic bot spam without adding any friction for real visitors, since they never see or interact with the honeypot field at all. For a form seeing persistent, more sophisticated spam despite honeypot protection, layering on reCAPTCHA is the next step up, though it does add a small amount of friction, and for some visitors, a genuine accessibility or usability concern, worth weighing against how bad the spam problem actually is before defaulting to the most aggressive option on every form sitewide.
Comparing to Other Popular Free Form Builders
Fluent Forms isn’t the only actively maintained free option worth knowing about, and it’s worth a brief honest comparison rather than treating it as the only reasonable choice. WPForms’ free Lite version is more limited in form count and field types than Fluent Forms’ free tier, but its paid tiers lean heavily into an extremely polished, template-driven setup experience that’s arguably faster for a non-technical user building a simple form quickly. Contact Form 7, still widely used, is lighter-weight and more code-oriented, appealing to developers comfortable writing form markup directly but offering a noticeably rougher experience for anyone wanting a visual drag-and-drop builder without touching shortcode syntax. Where Fluent Forms tends to win the comparison is the combination of a genuinely capable free tier, a modern drag-and-drop interface, and native performance, it’s built without jQuery dependency in its frontend rendering, which some competing form plugins still carry as legacy baggage, and that translates to a measurably lighter page-load footprint on a form-heavy page.
Performance Impact on Page Load
A form plugin’s frontend footprint matters more than it might seem, especially on a page where the form isn’t the only thing loading, a landing page with a hero section, testimonials, and a contact form all competing for load-time budget. Fluent Forms’ vanilla-JavaScript approach to its frontend rendering, rather than depending on jQuery or a heavier framework, generally produces less script weight than older-generation form plugins built when jQuery dependency was the WordPress default assumption. This isn’t a dramatic difference on a single-form page, but it compounds on a site running multiple forms across several pages, or a page embedding more than one form simultaneously, where each additional heavy dependency adds up in aggregate page weight and can measurably affect Core Web Vitals scores.
Entry Management and Notifications
Beyond just collecting submissions, worth checking how entry management actually works day to day, since that’s where a form builder either saves or costs you real admin time. Fluent Forms stores entries inside wp-admin with filtering and export built in on the free tier, so you’re not locked out of your own submission data without upgrading, a limitation some competing plugins impose. Notification emails, confirming to the submitter, alerting an admin, are configurable per form, including conditional routing rules on the Pro tier, useful if different form types need to reach different team members automatically rather than every submission landing in one shared inbox regardless of what it’s actually about.
Using it with BuddyX
The BuddyX theme doesn’t need special integration to work with Fluent Forms, forms display cleanly inside any BuddyX page or post the same way they would with any other well-built theme. If you’re building a community site and want contact, registration-adjacent, or feedback forms that match your site’s design, dropping a Fluent Forms block into a BuddyX page works out of the box. Check out the BuddyX demo to see the theme itself.
Conversational Forms as an Alternative Layout
Beyond the standard all-fields-at-once layout, Fluent Forms supports a conversational form style, presenting one question at a time in a chat-like sequence rather than a full traditional form. This isn’t the right choice for every form, a short two-field contact form doesn’t benefit much from being broken into a multi-step conversation, but for a longer form, an in-depth application, a multi-part survey, the conversational format can meaningfully reduce the perceived effort of completing it, since a visitor is only ever looking at one question at a time rather than confronting the full length of the form upfront. Worth testing both layouts for a longer form specifically to see which one actually produces a better completion rate for your audience, since the answer isn’t universally the same across every use case.
A Few Community-Site-Specific Use Cases
Beyond a generic contact form, a form builder pulls real weight on a community or membership site specifically. A member application or vetting form, gated behind conditional logic that routes different applicant types to different review queues, handles onboarding more cleanly than an open-registration free-for-all. An event RSVP form with a payment field covers ticketed community meetups without needing a separate events plugin’s built-in payment handling, which is sometimes more limited than a dedicated form builder’s payment integration. And a member feedback or satisfaction survey, run periodically rather than as a one-off, gives a community manager structured, comparable data over time rather than scattered anecdotal comments pulled from an activity feed.
Backing Up Form Data Independently
Since form entries live in your WordPress database alongside the rest of your site content, they’re covered by whatever backup routine your site already runs, but it’s worth confirming that coverage specifically rather than assuming it. Some backup plugins exclude certain custom database tables by default unless configured otherwise, and a form plugin’s entry storage can occasionally use its own custom tables outside the standard wp_posts structure. A quick check of your backup plugin’s table-inclusion settings, and a test restore that specifically verifies form entries survive the process, is worth doing once after setup rather than discovering a gap the first time you actually need to restore from a backup.
A Note on Ongoing Maintenance
The core lesson from the plugin this post used to cover isn’t really about Fluent Forms specifically, it’s a broader point worth applying to every plugin choice, especially anything handling user data directly. Before committing to any form plugin, or any plugin at all, check its update frequency, its open support forum for unresolved critical issues, and whether it’s actively responding to WordPress core and PHP version compatibility over time. A plugin with a large install base and infrequent updates is a bigger long-term risk than a smaller plugin with a consistent, recent update history, since install-base size alone doesn’t protect against abandonment or closure the way this post’s original subject demonstrates directly.
GDPR and Data Handling Considerations
Any form collecting personal information, name, email, and especially anything more sensitive, is a data-handling touchpoint worth thinking through deliberately rather than treating as a purely technical setup task. Fluent Forms includes GDPR-related settings on both free and Pro tiers, an option to require explicit consent checkboxes, and controls for how long entry data is retained before automatic deletion. Enabling and actually configuring these settings, rather than leaving them at whatever the default is, matters if your site has visitors from regions with data privacy regulations, which for most public-facing sites today is a realistic assumption regardless of where the business itself is based. It’s also worth pairing form-level consent settings with a clear, accessible privacy policy that specifically covers what happens to form submission data, since a consent checkbox without a genuinely informative privacy policy behind it is weaker compliance than it looks.
Accessibility of the Form Builder Output
A drag-and-drop form builder’s visual editor being easy to use doesn’t automatically guarantee the forms it produces are accessible to visitors using assistive technology. Worth checking specifically: are form field labels properly associated with their inputs for screen readers, is error messaging announced clearly rather than only shown as a color change, and can the entire form be completed using a keyboard alone without a mouse. Fluent Forms’ output generally follows standard accessible form markup practices by default, but any heavy customization through custom CSS or a complex conditional logic setup is worth testing directly with a screen reader or keyboard-only navigation before considering a form genuinely done, rather than assuming the builder’s defaults cover every customization you might layer on top.
Mobile Form Experience
Forms are one of the more failure-prone elements on mobile specifically, since cramped input fields, a date picker that doesn’t work well with touch, or a multi-column layout that doesn’t collapse properly on a small screen can all turn a simple form into a frustrating one. Fluent Forms’ responsive behavior generally handles standard layouts well by default, but multi-column forms, a Pro feature, are worth testing specifically at a phone width, since a layout that looks clean in a two- or three-column desktop view needs to collapse sensibly to a single column on mobile rather than squeezing multiple narrow columns into a screen that can’t comfortably display them. Any form expected to see meaningful mobile traffic, which in practice is most public-facing forms today, deserves an actual phone test before being considered finished, not just a browser-resize check on desktop.
Email Marketing and CRM Integrations in Practice
The Pro tier’s 60+ integrations are a headline number, but what actually matters for most sites is whether the specific tool they’re already using is covered, and how deep that specific integration goes beyond a basic “send the submission somewhere.” A well-built integration should let you map form fields to the target tool’s fields directly, rather than just dumping a generic notification, and should support conditional routing so, for example, a form submission only adds a contact to a specific email list if a particular checkbox was selected. Before committing to the Pro tier specifically for its integrations, it’s worth confirming your actual email marketing platform or CRM is covered with the depth of field mapping and conditional logic your use case actually needs, rather than assuming “60+ integrations” automatically means your specific tool gets full-depth support.
Common Setup Issues Worth Knowing About
- Form not sending notification emails. Almost always a server email deliverability issue rather than a plugin bug, check whether your hosting environment is properly configured with SMTP rather than relying on PHP’s default mail function, which many hosts throttle or block outright for spam-prevention reasons.
- Conditional logic not triggering as expected. Usually traces back to a field’s internal name changing after the logic was set up, editing a field’s label doesn’t always update references to it in conditional rules, worth double-checking the underlying field references after any field renaming.
- Styling conflicts with the active theme. A heavily customized theme can occasionally override form styling in unexpected ways, isolating the issue with your browser’s inspector to see which CSS rule is winning is faster than guessing at a fix.
- Duplicate submissions. Usually a double-click on the submit button combined with no disabled-state feedback, confirm the submit button visibly disables or shows a loading state immediately on click so users don’t click multiple times assuming nothing happened.
Frequently Asked Questions
Can I import forms from Contact Form 7 or WPForms?
Fluent Forms includes a built-in importer for several popular form plugins, including Contact Form 7, WPForms, and Ninja Forms, which handles field structure migration automatically, though it’s worth reviewing each imported form manually afterward to confirm conditional logic, notification settings, and any custom styling carried over correctly rather than assuming a perfect one-to-one migration.
Does the free version include a payment field?
Basic payment field support is included free, generally covering a straightforward one-time payment collection through a supported gateway. More advanced payment scenarios, subscriptions, multiple payment methods on the same form, split payments, are gated to the Pro tier, worth checking against your specific payment needs before assuming the free tier covers a more complex use case.
Is my form data stored only in my own WordPress database, or does it pass through Fluent Forms’ own servers?
Core form submission and storage happens directly in your own WordPress database, it’s a self-hosted plugin rather than a service that routes your data through a third party by default. Specific integrations, an email marketing platform, a payment gateway, do send relevant data to that third-party service as part of how the integration functions, which is expected and disclosed behavior for those specific connections rather than a general data-routing concern with the plugin itself.
Interesting Reads:
How to create a multivendor marketplace using WordPress
BuddyPress Demo Website - Learn BuddyPress WordPress Community Plugin