A Gravity Forms Alternative That Isn't a WordPress Plugin

Short answer: if your form needs to create WordPress content, read the logged-in user, or fire WordPress hooks, keep Gravity Forms. If it needs to capture enquiries and get them to a person, a hosted builder is less to run — no plugin updates, no site database, no wp-admin logins for the people reading submissions. As of September 2026 BotForms starts at $29/month with a 30-day trial.

Gravity Forms is a good plugin. That is worth saying up front, because most "alternative" posts open by pretending the incumbent is bad. It is not. It has been the serious WordPress form option for over a decade, its conditional logic is solid, and if your site is WordPress and your form needs to touch WordPress, it is doing something a hosted tool structurally cannot.

The question is whether your form needs to touch WordPress. For a lot of businesses the honest answer is no — the form collects an enquiry and sends it somewhere. And once that is true, hosting the form inside the site starts costing more than it returns.

What you actually get from a plugin

Being inside WordPress buys four specific things:

Access to WordPress data. The form knows who is logged in, what role they have, and what content exists. A membership renewal form that pre-fills from the user profile is a plugin job.

The ability to create WordPress things. Post creation from a submission, user registration, updating a custom field. This is the biggest genuine lock-in: hosted forms can send data to WordPress through an API, but they do not natively make posts.

Hooks. If a developer has written custom PHP that runs on submission, that code is attached to the plugin's action hooks and will not travel.

Entries in your own database. Some teams consider this essential. Others discover it is where the risk lives.

If your forms use one of the first three, the rest of this post is informational rather than actionable. Keep the plugin.

What it costs you

Updates are site risk. A form plugin and its add-ons update on their own schedule, and a bad interaction with your theme or another plugin takes the form down. The failure is quiet — the form still renders, it just stops delivering — and you find out when someone asks why nobody called them back.

Submissions live in the site database. This is fine until the day it is not: a hosting migration, a restore from an older backup, a compromised site. Your enquiry history is now coupled to the health of your marketing site, which is the part of your infrastructure most likely to be tinkered with by someone who does not think of it as a database.

Everyone who reads submissions needs wp-admin. That is the one most teams have not thought through. A salesperson who needs to see enquiries gets a WordPress account, which is an account on the thing that publishes your website. The narrower alternative is scoping access at the form layer — the shape of that decision is in who on your team should see form submissions.

Every form change is a site change. Adding a field means logging into the CMS, editing, and hoping. Small, but it is the reason forms go stale — nobody wants to touch production to reword a question.

Plugin or hosted: the honest comparison

What you need	WordPress plugin	Hosted form builder
Create posts or users from a submission	Native	Needs an API integration
Pre-fill from the logged-in user	Native	Not available
Custom PHP on submit	Action hooks	Webhook to your own code
Same form on a non-WordPress page	Rebuild or iframe	Paste the same embed
Keeps working if the site breaks	No	Yes
Who can read submissions	Anyone with wp-admin	Anyone you invite, scoped
Who maintains it	You	The vendor
Cost shape	Annual licence + maintenance	Monthly subscription

The column that decides it is usually the first three rows. Everything below them favours hosted; everything above them favours the plugin.

Embedding without a plugin

A hosted form goes onto a WordPress page the same way a video does — a block with an embed snippet, or an iframe in a custom HTML block. No plugin, no PHP, and the page is still a WordPress page. The mechanics across the main site builders are in embedding a form on WordPress, Webflow or Squarespace.

Two things worth getting right at embed time. Put the form where the page's argument ends rather than in a sidebar, and check it on a phone before you call it done — the majority of enquiry traffic on a service business site arrives on a phone, and a form that needs two-finger zoom is a form that gets abandoned.

Moving the form without losing the history

The migration itself is small. The record-keeping is what people skip.

Export your entries first. Gravity Forms will write them to CSV. Do it before anything else and keep the file off the site — a copy on the site is a copy you lose with the site.

Rebuild rather than transcribe. A form that has been live for three years has accumulated fields nobody reads. Migration is the one moment you are allowed to delete them; the sequence for doing that without losing anything is in migrating your forms to a new builder.

Run both for two weeks. New form on one page, old form everywhere else, then compare completed submissions. If the new one wins, roll it out; if it does not, you have lost nothing and learned something.

Change the notification address last. The single most common migration failure is a form that submits perfectly into a mailbox nobody checks.

If your forms started as PDFs — an application, an intake packet, a service agreement — a rebuild is also a chance to stop retyping them, which is covered in converting a PDF to an online form.

Where AI actually changes the comparison

For years the plugin-versus-hosted argument was about hosting. The newer difference is the build itself.

Describing a form in a sentence and getting a working draft — fields, types, validation, a sensible order — collapses the part of the job that used to take an afternoon of dragging. It matters most for the forms you keep meaning to make and never do: the follow-up form, the second service's intake, the seasonal one. The economics of that are in what an AI-builder run is.

The other half is question quality. Most business forms ask too many things in an order nobody would choose, and a tool that rewrites the questions is doing work a plugin has never claimed to do. That is the subject of AI that writes and optimises your form questions.

If your site is not only WordPress

Plenty of businesses have a WordPress marketing site plus a landing page on something else, or a static site for docs. A plugin form is trapped in the first; a hosted form is one embed everywhere, with the submissions arriving in one place.

That is also the answer for static sites with no CMS at all, where the form needs a backend that does not exist — the pattern for that is in form backends for static sites.

Which alternative

The WordPress form market has three broad exits, and they are not interchangeable.

Another plugin. You keep WordPress integration and change your maintenance burden slightly. Reasonable if the lock-in reasons apply.

A general hosted builder. Jotform, Typeform and the rest. You get the form out of the site and gain a submission dashboard; how those compare on the things small teams actually hit is in the Jotform alternative comparison.

An AI-first hosted builder. Same exit, but the build step changes as well as the hosting.

The wrong reason to switch is the one that shows up most: a plugin conflict broke the form once and you want it to never happen again. That is a real reason, but check the boring things first — who reads the submissions, where they are stored, and how quickly the form can change when the business does.

Getting started

Pick one form. The contact page is usually the safest, or whichever enquiry form is worth the most per submission. Build it in a hosted tool, embed it on one page, leave the plugin in place, and compare a fortnight of completed submissions.

If it wins, move the rest and keep the export. If it does not, you have a two-week test and a clean answer.

BotForms builds the form from a description, embeds anywhere with a snippet, and keeps submissions in a dashboard with scoped team access — 1 user and 1,000 submissions a month on Starter at $29, 3 users and 10,000 on Pro at $79, 10 users and 50,000 on Business at $199, all with a 30-day trial. See features, pricing, or start a trial.