Beyond Contact Form 7 and WP Forms, the suite has a module for ten more form plugins, so a site keeps one form design whichever plugin it already uses.
The other ten, and what each is found by
- Gravity Forms, by its
gravity_formfunction. Ninja Forms, byNinja_Forms. Fluent Forms, bywpFluentForm. - Forminator, by its
Forminator_APIclass. Formidable Forms, byFrmForm. - SureForms, Everest Forms, Happyforms, weForms and WS Form, each by the version constant its plugin defines.
Ninja Forms and Fluent Forms are the two stylers that ship enabled. The other ten are off until you switch them on.
Point a styler at your form
- Switch the matching module on under Divi Squad → Modules and save.
- Add it to a row in the Divi Builder.
- Choose your form from the Form dropdown under Form Options.
- Style every field, label, message and button from the Design tab.
What differs between the modules is only what the underlying plugin renders. Some emit their own wrappers around a field group, so which spacing control matters varies a little from one to the next. The set of styling areas does not.
MetForm was removed
The MetForm styler is gone, and it is not coming back. MetForm builds its forms for Elementor, so a MetForm form inside a Divi page is an Elementor document with its own per form CSS, scoped several classes deep and with ids that differ per form, which a Divi module cannot win against. Its fields are Elementor widgets rather than form fields, which left the field settings with nothing to style. It had also stopped registering: the class it detected MetForm by no longer exists in current MetForm, so the module was unreachable in the builder anyway. It was off by default, so this reached only sites that had turned it on and built with it. A page still using it shows the module as missing.
When a form will not style
- Check the form plugin is active. The module is registered only while its plugin is, and deactivating the plugin removes the module from the picker.
- Check the module is switched on and saved under Divi Squad → Modules. Ten of the twelve ship off.
- Reload the builder. The form lists are assembled when the builder loads, so a form created in another tab since then is not in the dropdown yet.
- If one setting in particular refuses to take, it is usually the form plugin’s own stylesheet rather than the module. Several of these plugins ship strong selectors. The module’s CSS ID and CSS Class fields in the Advanced tab are the way through.