WPForms

What Is WPForms?

WPForms is a popular drag-and-drop form builder plugin for WordPress, designed to let site owners create contact forms, subscription forms, payment forms, and surveys without writing any code. It is widely regarded as one of the most beginner-friendly form solutions in the WordPress ecosystem, and its publisher reports that it is active on millions of websites, which places it among the most-installed form plugins in the WordPress plugin directory.

WPForms was created by the team behind several well-known WordPress products and launched with a deliberate focus on simplicity. Where older form plugins exposed dozens of technical settings, WPForms leads with pre-built templates and a visual editor so that a non-technical user can publish a working contact form in minutes. That positioning, "the most beginner-friendly WordPress form plugin," is the company's central marketing claim and explains much of its design.

It is important to be precise about what WPForms is. It is a server-side WordPress plugin: PHP code that installs into a self-hosted WordPress site and runs as part of that site. It is not a hosted form service that you embed from a third-party domain, and it is not a browser extension. When a visitor submits a WPForms form, the data is processed by the WordPress installation itself (and optionally forwarded to integrated services), and the form markup is rendered into the page by WordPress on the server.

Because WPForms ships its own predictable CSS, JavaScript, and HTML markup patterns, it leaves clear, recognizable fingerprints in a page's source. That makes it one of the more detectable WordPress plugins, both for a person inspecting the page by hand and for an automated server-side scanner such as StackOptic that fetches a URL and analyzes the returned HTML and asset references.

WPForms is distributed in a freemium model. A free edition, WPForms Lite, is available in the official WordPress plugin directory and covers basic contact forms. Paid tiers unlock the features most businesses eventually want, such as conditional logic, multi-page forms, payment collection, marketing-platform integrations, and advanced form types like surveys and polls. This tiered structure is common across the WordPress plugin market and shapes which fingerprints appear on a given site: a simple brochure site might only load the Lite assets, while a lead-generation site often loads additional addon scripts.

How WPForms Works

At its core, WPForms is a form builder layered on top of WordPress's plugin architecture. Once installed and activated, it adds a dedicated section to the WordPress admin where users build forms on a visual canvas. You start from a template, such as a simple contact form, a newsletter signup, or a request-a-quote form, and then drag fields (name, email, dropdown, checkboxes, file upload, payment, and so on) into place. Each field has settings for labels, placeholders, validation, and visibility.

Forms are stored in the WordPress database and assigned a numeric form ID. To display a form, the user inserts it into a post, page, or widget area. In the modern block editor, this is done with a dedicated WPForms block; in classic contexts, it is done with a shortcode of the form [wpforms id="123"]. When WordPress renders that page, the plugin replaces the block or shortcode with the full HTML for the form and enqueues the CSS and JavaScript needed to style and validate it.

On the front end, WPForms handles client-side validation (checking required fields and email formats before submission) and then processes the submission on the server. Depending on configuration, a submission can trigger notification emails, store an entry in the database for later review, run conditional logic, and pass data to connected services such as email-marketing platforms or payment processors. Anti-spam protection is built in, historically through a hidden honeypot field and more recently through modern token-based checks and optional CAPTCHA integrations.

A useful way to understand the workflow is to follow a single form from creation to submission. A marketer chooses a "Newsletter Signup" template, drags in an email field and a consent checkbox, and configures the form to add subscribers to a mailing-list integration. They embed it on the homepage with the WPForms block. A visitor fills it in; the plugin validates the input in the browser, submits it to WordPress, stores an entry, sends the site owner a notification email, and forwards the subscriber to the connected marketing platform, all without the marketer writing a line of code. This end-to-end automation, driven entirely from the WordPress admin, is the heart of the product.

WPForms extends through addons rather than a sprawling settings panel. Functionality such as Stripe or PayPal payments, multi-step "Form Pages," surveys and polls, conversational forms, and CRM connectors are delivered as separate addon modules that load their own assets only when used. This modular approach keeps the base plugin lightweight while allowing a single site to grow from a basic contact form into a full lead-capture and payment system.

How to Tell if a Website Uses WPForms

WPForms leaves several dependable fingerprints in the HTML and asset references of any page that displays one of its forms. Because StackOptic analyzes a URL from the server side, it inspects the same signals you can check by hand with View Source, browser DevTools, or a detection extension. Note that WPForms only loads its assets on pages that actually render a form, so the most reliable place to look is a page known to contain a form, such as a contact page.

Asset paths under the plugin directory. The strongest signal is the plugin's own CSS and JavaScript, served from the WordPress plugins directory. Look for requests to paths containing /wp-content/plugins/wpforms-lite/ (the free edition) or /wp-content/plugins/wpforms/ (the paid edition), typically loading files such as a wpforms-full.css stylesheet and validation scripts. These paths are close to definitive.

WPForms-prefixed markup. The rendered form is wrapped in container elements with recognizable classes and IDs. You will commonly see a <div class="wpforms-container ...">, a <form ...> with classes like wpforms-form, IDs in the pattern wpforms-form-123, and field wrappers using wpforms-field classes. Submit buttons carry wpforms-submit classes. This wpforms-* prefix throughout the markup is a clear tell.

Hidden form metadata. WPForms forms embed hidden inputs that identify the form, such as a field named wpforms[id] carrying the numeric form ID, plus nonce and post-ID fields. Seeing name="wpforms[id]" in the page source is a strong, specific indicator.

The shortcode in source (occasionally). On misconfigured pages or in cached fragments, you may even spot a raw [wpforms id="..."] shortcode, which is unambiguous.

WordPress confirmation. Because WPForms only runs on WordPress, confirming WordPress itself adds confidence. Signals like a /wp-content/ path, a wp-json REST endpoint, or a <meta name="generator" content="WordPress ..."> tag corroborate the platform.

Here is how to check each signal yourself:

Method	What to do	What WPForms reveals
View Source	Open a contact page, right-click, "View Page Source"	wpforms-container markup, wpforms[id] hidden field, plugin asset paths
Browser DevTools	Inspect the form element and the Network tab	/wp-content/plugins/wpforms*/ CSS/JS requests, wpforms-* classes
curl	`curl -s https://example.com/contact	grep -i wpforms`
Wappalyzer	Run the extension on the live page	Identifies "WPForms" under Form builders / Widgets
BuiltWith	Look up the domain	Current and historical WPForms detection plus the hosting profile

A fast terminal check is curl -s https://example.com/contact-us/ | grep -i "wpforms". If that returns matches for the container class or the plugin path, you are almost certainly looking at WPForms. Because identifying a plugin first means identifying the platform, our guide on how to tell if a website is built with WordPress is a useful starting point, and the broader methodology in how to find out what technology a website uses explains how to combine signals.

A practical caveat is that detection depends on landing on a page that renders a form. A homepage with no form may show no WPForms assets at all, which is why scanning a contact or signup page is the most reliable approach. Some sites also use caching and asset-optimization plugins that minify or rename files, but the wpforms-* class names and the hidden wpforms[id] field are embedded in the form markup itself and survive most optimization. When several signals line up, the plugin path, the container class, and the hidden ID field, the conclusion is dependable even on a heavily customized theme. For identifying the surrounding theme and other plugins, see how to identify a WordPress theme and plugins.

Key Features

• Drag-and-drop builder. A visual canvas with pre-built templates lets non-technical users assemble forms in minutes without touching code.
• Form templates. A large library of starting points, including contact, newsletter, request-a-quote, registration, and survey forms.
• Conditional logic. Show, hide, or change fields and notifications based on a visitor's previous answers (a paid-tier feature).
• Payment collection. Integrations with Stripe, PayPal, Square, and Authorize.Net turn forms into order or donation forms.
• Marketing and CRM integrations. Native connectors push submissions to email-marketing platforms and customer-relationship tools.
• Spam protection. Built-in honeypot and token-based anti-spam plus optional CAPTCHA and modern challenge integrations.
• Entry management. Submissions are stored in WordPress for review, export, and reporting, in addition to email notifications.
• Surveys, polls, and form pages. Addons add distraction-free full-page forms, conversational layouts, and survey reporting.

Pros and Cons

Pros

• Exceptionally beginner-friendly, with templates and a visual editor that require no coding.
• Lightweight base plugin that loads addon assets only when needed, helping page performance.
• Strong integration ecosystem covering payments, email marketing, and CRMs.
• Reliable, well-documented, and frequently updated, with a large support footprint.

Cons

• The most useful features (conditional logic, payments, integrations) require a paid license.
• As a WordPress-only plugin, it cannot be used on non-WordPress sites.
• Power users may find it less flexible than developer-oriented form frameworks.
• Annual licensing costs can add up for sites that need multiple addons.

WPForms vs Alternatives

WPForms competes with other WordPress form plugins and, more broadly, with hosted form services. The table below clarifies where it fits.

Solution	Type	Ease of use	Best for
WPForms	WordPress plugin	Very high (beginner-first)	Site owners wanting quick, no-code forms on WordPress
Gravity Forms	WordPress plugin	Medium (developer-friendly)	Complex, data-heavy forms and advanced workflows
Contact Form 7	WordPress plugin	Low (markup-based)	Developers comfortable configuring forms via templates
Ninja Forms	WordPress plugin	High	Modular, addon-based form building
Typeform	Hosted SaaS (embed)	High	Conversational, brand-led forms across any platform

If you suspect a site uses a different WordPress form plugin, the same inspection techniques apply, the asset path and CSS-class prefix simply change, for example gform_ markup and /plugins/gravityforms/ paths indicate Gravity Forms. You can also compare WPForms with the SEO-focused Yoast SEO plugin to see how different plugin categories fingerprint a WordPress site.

Use Cases

WPForms is most at home on small-business and marketing websites that need dependable contact and lead-capture forms without a developer. A local service business uses it for a "request a quote" form; a consultant uses it for a contact form that emails them on submission; a SaaS landing page uses it for a newsletter signup wired into an email-marketing platform.

It also suits sites collecting payments or donations through simple forms, membership or event registrations, customer-feedback surveys and polls, and multi-step application forms broken into digestible pages. Because submissions can be stored as entries and forwarded to CRMs, WPForms frequently sits at the front of a lead-generation pipeline, capturing prospects and routing them into downstream tools.

From a competitive-intelligence and lead-qualification standpoint, detecting WPForms on a site is a meaningful data point. It indicates a self-hosted WordPress site whose owner is actively collecting leads, signups, or payments through forms, which is exactly the profile many B2B vendors want to identify. Knowing which form plugin and which integrations a prospect uses helps tailor outreach and gauge how a target captures demand. This kind of plugin-level insight is part of what makes technology detection valuable for sales teams, as explained in what is technographics: using tech stack data to qualify leads.

Frequently Asked Questions

Is WPForms free?

There is a free edition, WPForms Lite, available in the official WordPress plugin directory, which covers basic contact forms and email notifications. The paid tiers (Basic, Plus, Pro, and Elite) add the features most businesses want, such as conditional logic, payment integrations, marketing-platform connectors, surveys, and advanced form types. Many sites start on Lite and upgrade as their needs grow, which is why some sites show only the wpforms-lite asset path while others load the full plugin and its addons.

How can I tell if a site is using WPForms for free?

Yes, you can detect it for free. Open a page that contains a form (a contact page is ideal), view the source, and look for wpforms-container markup, a hidden input named wpforms[id], or asset requests to /wp-content/plugins/wpforms-lite/ or /wp-content/plugins/wpforms/. Free tools like Wappalyzer and BuiltWith confirm it, and a single curl -s URL | grep wpforms command works from any terminal.

Does WPForms work without WordPress?

No. WPForms is a WordPress plugin written in PHP that installs into and runs on a self-hosted WordPress site. It is not a standalone hosted service and not a browser extension, so it cannot be added to a non-WordPress platform. If you find WPForms on a site, that site is necessarily running WordPress, which is why confirming WordPress fingerprints alongside the plugin increases detection confidence.

Why don't I see WPForms on every page of a site that uses it?

WPForms only enqueues its CSS and JavaScript on pages that actually render a form, to avoid loading unnecessary assets site-wide. As a result, a homepage or blog post with no form may show no WPForms signals at all, even though the plugin is installed. To detect it reliably, scan a page you expect to contain a form, such as a contact, signup, or quote-request page.

What is the difference between WPForms and Contact Form 7?

Both are WordPress form plugins, but they target different users. WPForms leads with a drag-and-drop visual builder and templates aimed at beginners, while Contact Form 7 is a long-standing free plugin that is configured by editing markup-like form templates and is favored by developers. In the page source, the two differ clearly: Contact Form 7 uses wpcf7 classes and /plugins/contact-form-7/ paths, whereas WPForms uses wpforms-* classes and /plugins/wpforms*/ paths.

Want to identify WPForms and the rest of a site's stack automatically? Run any URL through StackOptic at https://stackoptic.com.