Skip to content
WPJury
No. 00132 Forms

Gravity Perks: worth it for serious Gravity Forms builds

The verdict Gravity Perks is worth paying for if Gravity Forms is already the foundation of your site and you need advanced features such as nested forms, dynamic population, inventory, calculations, or conditional pricing. It is not worth buying as a standalone form solution: it requires Gravity Forms, its annual cost can become substantial, and simpler builders such as WPForms or Fluent Forms include more functionality in one product.
Situational The ruling
Get v1.2.32

via WorldPressIT · complete package

Best for
  • Gravity Forms power users
  • WordPress agencies
  • Complex registration and booking forms
  • Custom internal workflows
  • Sites needing dynamic form data
Skip it if
  • You need a basic contact form
  • You are choosing your first form builder
  • You want a hosted form service
  • You dislike recurring plugin costs
Version 1.2.32 Updated 11 Sep 2026 Licence GPL
Gravity Perks: worth it for serious Gravity Forms builds screenshot

Gravity Perks is not a single add-on that creates a new “Nested Kind” field. It is a large suite of extensions for Gravity Forms, made by Gravity Wiz. The marketplace description appears to confuse several products: the relevant feature is likely GF Nested Forms, which adds repeatable child forms, while Gravity Perks itself also includes tools for dynamic population, calculations, inventory, conditional pricing, advanced selects, save-and-continue, and many other tasks. The suite currently advertises more than 46 add-ons and is designed to extend an existing Gravity Forms installation, not replace it. ([gravitywiz.com](https://gravitywiz.com/gravity-perks/?utm_source=openai))

That distinction matters because the value is unusually strong for established Gravity Forms users. A complex form that would otherwise need custom PHP and JavaScript can often be assembled with a combination of perks. Populate Anything can pull and filter posts, users, taxonomies, entries, database records, and REST data; Nested Forms can collect related child records inside a parent submission; and Advanced Calculations can handle formulas beyond Gravity Forms’ standard arithmetic. These are practical tools for quotations, applications, product configurators, event registration, staff workflows, and member portals rather than decorative extras. ([gravitywiz.com](https://gravitywiz.com/documentation/gravity-forms-populate-anything?utm_source=openai))

The documentation is one of the product’s genuine strengths. Each perk has its own setup guide, examples, snippets, compatibility notes, and known limitations. The support operation is also more substantial than you normally get from a small WordPress add-on: Gravity Wiz publishes troubleshooting procedures, maintains a large snippet library, and advertises average response times measured in hours. That matters when several perks interact with Gravity Forms, caching, conditional logic, payment feeds, or third-party extensions. ([gravitywiz.com](https://gravitywiz.com/documentation/help-us-help-you/?utm_source=openai))

There are real drawbacks. The suite is modular, so you may need several separate perks to reproduce what another form builder includes by default. Some features have technical boundaries: Populate Anything does not support PostgreSQL, forms embedded more than once on a page can cause problems, and dynamic population can be disrupted by page caching. Nested Forms also introduces a parent-and-child entry model that is powerful but more complicated to export, edit, migrate, and explain to clients than a normal form submission. These are documented behaviours, not minor edge cases. ([gravitywiz.com](https://gravitywiz.com/documentation/gravity-forms-populate-anything?utm_source=openai))

Pricing makes the decision clearer. The current Basic plan is $59 per year for one perk on one site; Advanced is $169 per year for three perks on three sites; and Pro is $299 per year for unlimited perks and sites. The Basic plan is sensible when one specific extension solves an expensive problem. Pro can be excellent value for agencies building multiple Gravity Forms projects, but it is hard to justify for a brochure site or a simple lead form. ([gravitywiz.com](https://gravitywiz.com/gravity-perks/pricing/?utm_source=openai))

Compared with WPForms or Fluent Forms, Gravity Perks is less attractive for users starting from scratch because those products offer a more unified feature set and simpler setup. Compared with Formidable Forms, Gravity Perks is often better for highly tailored Gravity Forms workflows, while Formidable is more cohesive for database-style applications. GravityKit is the closer companion rather than a direct replacement: Gravity Perks improves data collection, while GravityKit focuses more on displaying and managing entries on the front end. ([gravitykit.com](https://www.gravitykit.com/vs/gravity-perks/?utm_source=openai))

Verdict: buy Gravity Perks when you already rely on Gravity Forms and can name the specific problems it will solve. Do not buy it because a marketplace listing promises a mysterious new field type; verify the exact perk, its Gravity Forms requirements, and whether the annual license is cheaper than developing or replacing the whole stack.

Questions people ask

Does Gravity Perks work without Gravity Forms?
No. Gravity Perks is an extension suite for Gravity Forms, so Gravity Forms must be installed and licensed separately.
Is Gravity Perks the same as Nested Forms?
No. Gravity Perks is the suite, while GF Nested Forms is one individual perk within it. Nested Forms adds repeatable child-form entries to a parent Gravity Form.
Does Gravity Perks require a plugin called Gravity Advantages?
No such requirement appears in the developer’s product documentation. The relevant dependency is Gravity Forms, and the marketplace description likely contains an incorrect product name.
How much does Gravity Perks cost?
The developer currently lists Basic at $59 per year, Advanced at $169 per year, and Pro at $299 per year. The plans differ by the number of perks, sites, and support level.
Is Gravity Perks better than WPForms?
It is better for extending an existing Gravity Forms installation with specialized, developer-friendly features. WPForms is usually the simpler and more economical choice when you are choosing a form builder from scratch.

Get Gravity Perks: worth it for serious Gravity Forms builds 1.2.32

Complete package, ready to install, via WorldPressIT.

Download

Other rulings

Formidable Datepicker Options: worth it for serious Formidable forms Formidable Datepicker Options is worth using if you already run Formidable Forms on its Business or Elite plan and need real control over date availability. It is not worth buying Formidable solely for a better calendar, because the add-on is locked to that ecosystem and its most advanced feature, date ranges, depends on the Flatpickr library marked as beta. For existing Formidable users building booking, age-verification, or scheduling forms, it is a practical and capable upgrade. Situational Formidable Forms Pro: worth it for complex WordPress applications Formidable Forms Pro is worth paying for when your forms need calculations, conditional workflows, repeatable fields, payments, PDFs, or front-end data displays. It is overkill for a basic contact form, and its tiered licensing and steeper learning curve make simpler builders better value for straightforward sites. Situational Gravity Forms: worth paying for complex WordPress forms Gravity Forms is worth paying for when forms are central to your site and need conditional logic, payments, file uploads, integrations, or developer-level customization. It is overkill for a basic contact form, and the annual license plus paid add-on tiers make cheaper builders such as Fluent Forms or Formidable Forms better value for many smaller sites. Situational Gravity Perks Page Transitions: worth it for polished multi-step forms Gravity Perks Page Transitions is worth buying if you already use Gravity Forms and want a smoother, more app-like multi-step experience without building custom JavaScript. It is not a must-have for ordinary forms, and its soft-validation limitations make it a poor fit for complex payment, nested, or heavily validated workflows. Situational