Contact Form 7 vs WPForms vs Gravity Forms: The Cost-Per-Form Reality

Pick a WordPress form plugin by feature checklist and you'll almost always conclude that Gravity Forms wins. It has the most add-ons, the most field types, the deepest conditional logic. But "most capable" and "right for your site" are different questions, and the gap between them is where people overspend or under-build. The honest way to choose between Contact Form 7, WPForms, and Gravity Forms is to look at the total cost of every form you'll actually build over the life of the site — money, developer hours, and page weight combined.

The pricing structures aren't comparable, and that's the trap

The three plugins sit at completely different points on the pricing model, which is why a flat "which is cheaper" comparison misleads.

• Contact Form 7 is free and GPL, forever, with no paid tier. The catch is that a lot of what you'd want — spam protection beyond a honeypot, conditional fields, multi-step, payments — lives in third-party add-ons of wildly varying quality, or in custom code.
• WPForms is freemium. The Lite version is genuinely free and handles a basic contact form. Conditional logic, file uploads, multi-page forms, and payment integrations sit behind paid tiers that start around $49–99/year for a single site and climb toward $300/year for the Pro and Elite tiers that unlock the full add-on library.
• Gravity Forms is paid-only. There's no free version. Licenses run roughly $59/year (Basic, one site), about $159/year (Pro), and around $259/year (Elite) for the full add-on suite including the advanced integrations. A lifetime/agency-style buyout shows up periodically but the annual license is the norm.

Notice that the renewal is annual. A form plugin is not a one-time purchase — if you let the license lapse you stop getting updates and, for the premium add-ons, the integration stops being supported. Over a five-year site lifespan, Gravity Forms Pro is roughly $800 cumulative, WPForms Pro lands somewhere similar depending on tier, and Contact Form 7 is still $0 in license fees. The license cost only tells you half the story; the other half is labor.

The hidden cost is developer time per form

Here's the calculation almost no comparison runs. Each plugin has a "cost per form built" that depends on how much custom work the form needs beyond what the builder gives you out of the box.

Contact Form 7 defines a form as a block of markup — field tags, mail templates, and validation written as text. A single static contact form takes maybe fifteen minutes and works flawlessly for years. But the moment a form needs conditional fields ("show the shipping address only if 'deliver' is selected"), CF7 has no native UI for it. You're reaching for an add-on like Conditional Fields for Contact Form 7, or writing JavaScript. Build twenty such forms and the accumulated hours of fiddling with shortcode syntax, debugging mail-tag escaping, and stitching add-ons together quietly dwarfs any license fee you avoided.

WPForms and Gravity Forms both give you a drag-and-drop builder where conditional logic is a checkbox and a dropdown, not code. A complex multi-step form with conditional routing that might take two hours of CF7-plus-custom-code work is a fifteen-minute job in either builder. If a developer touches your forms at an hourly rate, the builder pays for itself after one or two non-trivial forms. That's the real break-even, and it arrives much faster than the license math suggests.

A rough decision rule

1. One or two static forms, never changing, built by someone comfortable with markup: Contact Form 7. Free, light, done.
2. A handful of forms with conditional logic, file uploads, and basic email/payment connections, built and maintained by a non-developer: WPForms. The builder is the friendliest of the three and the price matches the scope.
3. Ten-plus active forms, payment workflows, multi-step applications, deep CRM/marketing integrations: Gravity Forms. The add-on ecosystem is the broadest and the developer experience (hooks, REST API, GFAPI) is the strongest.

Integrations are where Gravity Forms separates

For simple "email the submission to me" forms, all three are equivalent. The divergence shows up with native, officially-supported integrations. Gravity Forms ships first-party add-ons for Stripe, PayPal, Square, Authorize.net, Mailchimp, ActiveCampaign, HubSpot, Salesforce, Zapier, Slack, and roughly thirty more — plus a strong third-party developer market on top. WPForms covers the popular ones (Stripe, PayPal, Square, Mailchimp, ActiveCampaign, HubSpot, and webhooks at the higher tiers) but the long tail is thinner. Contact Form 7 has community add-ons for many services, but "community add-on, last updated two years ago" is a maintenance risk you're signing up for.

If your form needs to push a paid registration into Stripe, tag the contact in ActiveCampaign, and create a record in Salesforce — all from one submission — Gravity Forms does that with supported add-ons and no glue code. That single workflow can justify the Elite license outright. Below that level of integration depth, you're paying for capability you won't use.

Front-end performance: real, but smaller than you think

Form plugins load CSS and JavaScript on any page that renders a form. The lightest-to-heaviest order is consistent: Contact Form 7 is the leanest (on the order of ~25–35KB of assets per page with a form), WPForms sits in the middle (~45–60KB), and Gravity Forms is the heaviest (~60–80KB, more when add-ons like the rich-text or multi-page scripts load).

That spread matters most when a form appears site-wide — a newsletter signup in the footer, for instance, loads those assets on every single page. If your forms live only on a dedicated /contact page, the per-visit cost is negligible and shouldn't drive the decision. Two practical mitigations apply to all three: dequeue the plugin's assets on pages with no form (Gravity Forms and WPForms both have settings or filters for conditional asset loading), and lazy-load reCAPTCHA so it doesn't block your Largest Contentful Paint. Keep in mind the whole three-plugin spread is smaller than what a page builder like Elementor or Divi adds to every page (often 150–400KB), so forms are rarely your real Core Web Vitals problem. Aim to keep LCP under 2.5 seconds regardless, and a form plugin alone won't break that budget.

Spam, accessibility, and the things that bite later

Two factors that get ignored in feature tables matter a lot in production. Spam handling: Contact Form 7 ships with a honeypot and Akismet/reCAPTCHA hooks but historically attracts the most spam because its markup is so common that bots target it specifically; budget time for hardening it. WPForms and Gravity Forms both include built-in anti-spam tokens and modern CAPTCHA integration that work with less fuss. Accessibility: Gravity Forms has invested heavily in WCAG-conformant markup and ARIA, which matters if you have legal accessibility obligations; WPForms is solid; Contact Form 7's output is workable but you own the responsibility for labels and error messaging.

How to actually decide

Don't trust the comparison — including this one — over your own hands. Take the single most complex form you genuinely need to build, and build it twice: once in Contact Form 7 (or WPForms Lite) and once in a WPForms or Gravity Forms trial. The friction you hit in thirty real minutes — the integration that isn't there, the conditional rule that takes ten clicks, the spam that floods in on day one — tells you more than any feature matrix. Most reviews are written by someone who spent ten minutes in each tool and never shipped the form. Build your form, send a few test submissions through the whole pipeline to your inbox and your CRM, and the right choice usually becomes obvious before you've spent a dollar.