GeneratePress published the GenerateBlocks Pro 2.6 alpha announcement on 19 May 2026. The release matters for WordPress teams because it adds native forms to a block-building stack that many sites already use for layout and performance.
Our verdict
GenerateBlocks Pro 2.6 forms looks useful for simple, design-led forms inside a GeneratePress and GenerateBlocks build. Kahunam’s view is that it should be tested first as a replacement for lightweight contact forms and email signup forms, not as a like-for-like replacement for a mature form plugin across a whole website.
The strongest argument for GenerateBlocks is consolidation. If a site already uses GenerateBlocks for layout, simple forms can sit closer to the page design system, use the same styling approach, and avoid adding a separate form builder for basic capture jobs. The release also includes practical plumbing for email notifications, confirmation emails, webhooks, several email marketing tools and Cloudflare Turnstile.
The limit is scope. Gravity Forms, WPForms, Fluent Forms and Formidable Forms have spent years covering operational workflows such as advanced conditional logic, multi-page forms, entry management, file uploads, payment journeys, surveys, calculations, user registration and wider add-on ecosystems. GeneratePress has also said in its own comment thread that the intention is not to replace the full functionality of Gravity Forms or similar systems.
So the verdict is simple: GenerateBlocks Pro 2.6 forms is promising for lean forms where design consistency and performance matter more than workflow depth. Keep a dedicated form plugin where the form is part of the business process, takes payments, branches heavily, stores important records, or feeds several downstream systems.
Like-for-like comparison
The table below compares the areas that usually decide whether a WordPress team can remove a dedicated form plugin. Treat it as a replacement shortlist, not a complete feature inventory.
| Decision point | GenerateBlocks Pro 2.6 forms | Gravity Forms | WPForms | Fluent Forms | Formidable Forms |
|---|---|---|---|---|---|
| Best fit | Simple contact and email signup forms inside a GenerateBlocks build. | Complex operational forms, developer-friendly customisation and established add-ons. | Template-led forms for small teams that want a guided builder and broad add-on coverage. | Fast form building with strong marketing, payment and automation options. | Data-heavy forms, calculators, directories, views and application-style workflows. |
| Field types | The 2.6 release notes document contact and email signup forms; treat wider field coverage as something to test. | Broad field set, including file uploads, calculations and specialist fields. | Broad field and template coverage across paid plans. | Broad field coverage, including lead capture, survey, payment, registration and calculator use cases. | Broad field coverage, including repeaters, cascading lookups, uploads and calculated fields. |
| Conditional logic | GeneratePress is improving early form control conditions, but it does not yet position them as a full conditional logic system. | Strong conditional logic across fields, sections, pages, notifications, confirmations and feeds. | WPForms positions smart conditional logic as a paid-product feature. | Fluent Forms promotes conditional logic as a core feature. | Formidable Forms promotes smart forms with conditional logic, redirects and conditional notifications. |
| Multi-step or multi-page forms | GeneratePress does not present this as a main 2.6 use case. | Gravity Forms documents paginated forms for longer forms. | WPForms lists multi-page forms in paid plan comparisons. | Fluent Forms promotes multi-step forms. | Formidable Forms promotes multi-page forms with a progress bar and autosave. |
| Spam and anti-bot | GenerateBlocks includes Cloudflare Turnstile. | The Gravity Forms ecosystem offers security integrations and anti-spam options. | Spam protection features vary by plan and add-on. | Fluent Forms includes spam protection options in its feature set. | Formidable Forms lists reCAPTCHA, Turnstile, hCaptcha, Akismet and blocklist options. |
| Integrations and webhooks | GeneratePress documents webhooks plus Mailchimp, Kit, MailerLite, ActiveCampaign and Brevo. | REST API, simple webhooks and a large integration ecosystem. | Webhooks API and many add-ons, depending on plan. | Fluent Forms highlights marketing, CRM, automation and payment integrations. | Formidable Forms offers REST API/webhooks plus integrations for form data, payments and automation. |
| Entry storage | The beta notes add an option to store all email submissions; test retention, export and access controls before relying on it. | Mature entry management, export and add-on workflows. | WPForms provides entry management on paid plans. | Fluent Forms positions built-in entry management as part of the product. | Strong entry handling, including views and data display workflows. |
| Notifications and confirmations | GeneratePress documents form emails and confirmation emails. | Advanced email routing and confirmations, including conditional behaviour. | WPForms treats notifications and confirmations as core builder features. | Fluent Forms treats email notifications and form confirmations as core workflow features. | Formidable Forms promotes conditional confirmations and notifications. |
| Payments | The 2.6 announcement does not document this as a replacement use case. | The Gravity Forms ecosystem includes payment add-ons and recurring payment workflows. | WPForms provides payments across paid plans, with gateways depending on licence. | Fluent Forms positions payment forms and multiple gateways as part of the product. | Formidable Forms promotes Stripe, Square, PayPal, Authorize.net and other payment options. |
| Accessibility | Needs staging checks for labels, focus states, validation messages and keyboard flow. | Gravity Forms states support for WCAG 2.0 AA-compliant forms. | Should be tested per form and theme, especially with custom layouts. | Should be tested per form and theme, especially with multi-step forms. | Should be tested per form and theme, especially with custom HTML and views. |
| Performance and markup | This is likely the strongest case when the site already uses GenerateBlocks, because the form lives in the same block system. | More capability, but usually another plugin and add-on layer to maintain. | More capability, but plan/add-on choices can affect footprint and maintenance. | Broad features may be heavier than needed for a basic contact form. | Capable, but often more than a simple brochure site form needs. |
| Pricing and licensing | This matters if the site already pays for GenerateBlocks Pro or GeneratePress One. | Separate commercial licence. | WPForms offers a free Lite plugin plus paid plans for advanced features. | Fluent Forms offers a free plugin plus paid Pro plans. | Formidable Forms offers a free plugin plus paid Pro plans. |
What the alpha includes
GenerateBlocks Pro 2.6 introduces a forms system with contact and email signup forms. The announcement says site owners can configure form emails and confirmation emails, send submissions to webhooks, connect to tools including Mailchimp, Kit, MailerLite, ActiveCampaign and Brevo, and use Turnstile for spam protection.
The same release also adds direct CSS editing for blocks and Global Styles. That matters because forms often fail on small details: label spacing, focus states, error messages, mobile layout and visual consistency with the rest of a page. If styling lives closer to the block system, teams may need fewer separate plugins and less theme-specific CSS.
What not to assume yet
This is an alpha and beta-period release, so it belongs on a test site first. The announcement tells users to install both GenerateBlocks Pro 2.6 alpha and GenerateBlocks 2.3.0 alpha. A GeneratePress support reply also notes that the forms module isn’t enabled by default. That alone should stop teams from treating it as a drop-in replacement for a mature form plugin.
Before replacing Gravity Forms, Fluent Forms, WPForms or a custom form stack, compare the workflows you actually use. Simple contact forms and newsletter signups may fit the new module. Payment forms, multi-step forms, complex conditional logic, CRM routing, file uploads and legal consent flows may still need a dedicated plugin.
A sensible test plan
Create a staging page with one contact form and one email signup form. Test required fields, confirmation emails, webhook delivery, spam filtering, keyboard navigation, screen reader labels, mobile layout and submission logging. Confirm what happens when a webhook endpoint is down. Check whether email deliverability relies on the site mail setup or an existing SMTP service.
Teams planning larger WordPress changes should also compare this with their broader block-editor roadmap. The earlier Kahunam article on what is coming in WordPress 7.0 explains why editors, design systems and workflow changes should be assessed together rather than one plugin at a time.
Practical takeaway
GenerateBlocks Pro 2.6 could remove a plugin for simple forms, but only after a staging test proves the exact workflow. Treat the release as an evaluation window: list the current form jobs, rebuild the simplest one, and keep the existing form plugin until accessibility, deliverability, entry handling and integration checks pass.
Author
