Download websites that use Gravity Forms

About Gravity Forms

WordPress gives away form plugins, so the informative thing about Gravity Forms is that it is not given away. A Commercial licence, sold by Rocketgenius, has to be bought and then renewed to keep receiving updates, and that single fact turns a form row into a spending signal.

The plugin has been in the market since 2009, written in PHP, and it is chosen by people building forms that do work rather than forms that send an email. Conditional logic, multi-page flows, file uploads, payment gateways and connectors into sales and marketing systems are the reason somebody pays for it instead of using the free options. As of September 2026 we detect it on 274,607 sites in the Form builders group, which is a population of sites where a form sits inside an operational process.

Version data is where the commercial reading gets sharper. We see 933 distinct version strings across the detected sites, with 2.10.5 accounting for a large block of them and a long tail trailing behind. A tail that wide also means version matching is better done in buckets than on exact strings, since minor releases ship constantly and the precise string a site reports is mostly an accident of when it last updated. On free software a stale version usually means neglect. On licensed software a stale version usually means the licence lapsed, because updates stop when the renewal does. A site sitting well behind the current release is therefore either running unpatched form handling that touches payment and personal data, or is a customer the vendor has already lost, and those two readings are valuable to entirely different buyers.

Every detection also carries the platform underneath it, since the plugin only runs on WordPress, and that compound signal is more useful than either half alone. A form built to route submissions into a sales system implies there is a sales system, which in turn implies a company with a pipeline rather than a brochure site with a contact box. Forms are where a website stops describing a business and starts feeding it, so the presence of a paid, connector-heavy form builder marks the sites where the web is doing operational work.

Geography fits the profile. 186,863 of the detections sit in United States, and .com carries much of the population, which is what an agency-built business population looks like rather than a consumer one. Security researchers, competing form vendors, agencies selling maintenance retainers, and integration platforms hunting for accounts that already pay for tooling all read the same table for different reasons.

A detection is a plugin, not a form. Asset loading is often site-wide, so recognising the plugin on one page does not prove that page carries a form, and anyone who needs the form itself still has to visit the site. What the row supports is the population question rather than the page question, and being clear about which of the two is being asked saves a great deal of wasted crawling.

The version column has an honest limit. Recognising a release depends on version markers in asset paths, and caching and optimisation layers strip exactly those markers, so the version distribution describes the subset of sites that expose it and leans toward less aggressively optimised installations. Presence also says nothing about which paid add-ons a site licenses. A per-domain lookup answers whether one company uses the plugin. The downloadable list answers the questions that need the whole population at once: which sites run old releases, which of them also carry a payment integration, and which segments renew.