Formie 4 - Beta 1

Verbb Team Verbb Team June 2026 5 min read

Blog formie 4

Today we're opening up the first public beta of Formie 4 for Craft 5, and this one's a little different from our usual "here's a mountain of shiny new things" post. The shiny things are coming. But forms often end up holding a surprising amount of a business together, from enquiries feeding a CRM to payment forms taking money, so before any of that lands, we want to be sure your existing forms, submissions and integrations make the trip in one piece.

When we shipped Formie 3, we said all its internal rework was the first step towards bigger things like surveys, quizzes and proper multi-site support. Formie 4 is where they arrive, starting with this beta's migration work. If you'd rather go straight to installing, the Formie 4 Beta upgrade guide has the steps and migration notes.

Why Formie 4 Is Still for Craft 5

A new Formie major has usually arrived alongside a new Craft major, with Formie 2 for Craft 4 and Formie 3 for Craft 5. This time it doesn't. Craft is moving towards longer-term support (opens new window), and with Craft 6 (opens new window) still in alpha, Formie will be on Craft 5 for a good while yet. We didn't want to hold foundation work back until a new Craft release came along to justify it.

Some of that work started in Formie 3, when we began moving Formie's fields off Craft's own field classes. Formie 4 finishes the job, moving the rest of Formie's fields and field layouts onto its own system. That's more than tidying up, because Craft doesn't manage field settings per site, and proper multi-site forms need Formie's fields to be fully separate from Craft's.

What's Changed So Far

We'll tell the bigger feature story as the betas roll on, but Beta 1 already includes:

  • A new form builder, built to be fully accessible and responsive
  • A revamped content model for forms and submissions
  • Formie's own field system in place of Craft fields and field layouts
  • A new frontend package stack for popular frameworks (or none at all)
  • More reliable save and resume behaviour
  • Better foundations for submission workflows and the feature betas to come

Most of these changes are under the hood. Formie 4 aims to be as non-breaking as possible, with compatibility layers to keep your existing templates and extension points working through the transition.

Upgrading From Formie 3

If you're on Formie 3 and Craft 5, this is the path we most want tested. We've been running Formie 3 to Formie 4 upgrades locally, checking forms, fields, submissions, notifications, integrations, settings and template behaviour. A typical Formie 3 site should be able to install the beta, run migrations and carry on as before. As with any beta, please try that on a copy of your site first.

Upgrading Straight From Formie 2

You can also go directly from Formie 2 on Craft 4 to Formie 4 on Craft 5, without a stop at Formie 3 along the way. With Craft 4 nearing its end of life, there won't be a matching Formie 2 release for any of this work, so Formie 4 is where Craft 4 sites are headed, and we wanted that to be a single move.

We'd especially love to hear from teams looking after long-running Craft 4 sites. If yours has large forms, older submissions, custom templates, integrations, payments or a few years of production quirks, you're exactly who we want testing this.

New Frontend Packages and Starters

Our headless demo showed what's possible with Formie on a headless site, but you were still wiring up a fair bit yourself. Formie 4 adds packages that handle more of that for teams with custom frontends.

Beta 1 is the first chance to try them alongside the plugin. If you render forms outside the default Twig flow, or build with React, Vue or Web Components, we'd love your feedback on the setup, the API and the docs.

To make that easier outside an existing project, we've published starters for React (opens new window), Vue (opens new window), Web Components (opens new window), Next.js (opens new window) and Nuxt (opens new window). They cover server-rendered forms, where Formie still owns the HTML, and client-rendered forms, where your app builds the UI from Formie's form definition. There are also examples for Barba.js (opens new window), Sprig (opens new window) and Datastar (opens new window), where Craft still renders the form but the page around it has its own reactive or transitional behaviour.

Who Should Test More Closely

If you use Formie the usual way (building forms in the control panel, rendering them with the standard templates and connecting built-in integrations), we're aiming for the upgrade to be uneventful. Existing forms should keep working as they do now.

Spend more time with the upgrade guide if your project has any of these.

  • Custom Formie fields
  • Custom integrations, captchas or payment providers
  • Custom JavaScript that hooks into Formie's frontend events
  • Heavily customised Twig templates
  • Direct use of Formie's PHP APIs in your own module or plugin
  • Headless or JavaScript-rendered forms using the new packages

Those projects use parts of Formie that a normal form setup never touches, so their feedback is especially useful.

What's Coming Next

Once the upgrade path is solid, the betas move on to features. We're planning themed releases for builder organisation and defaults, notifications and status workflows, dynamic option sources, file uploads, integrations, spam and captcha controls, payments, surveys, polls and quizzes, localisation, headless and API work, performance, accessibility and a final round of polish. We'll write them up as they land.

How to Try It

The Formie 4 Beta upgrade guide has the full instructions. The short version goes like this.

  1. Back up your database and project files.
  2. Use a local, staging or disposable copy of your site.
  3. Install the beta with Composer.
    composer require verbb/formie:"^4.0.0-beta.1"
  4. Run migrations.
  5. Check your forms, submissions, notifications, integrations, templates and frontend behaviour.

Then send us anything weird, on GitHub (opens new window) or through Verbb support. Every odd setup you test now is one less surprise on launch day, so a massive thanks in advance to everyone who gives the beta a go!