Plugin how-tos · Guide
How to Style Fluent Forms (Step by Step)

Short answer
Open the form in Fluent Forms, click Style, pick a preset and adjust labels, inputs and buttons. For finer control, add CSS in the form's Custom CSS/JS settings, or style the form from the Fluent Forms block or Elementor widget. Use theme CSS for rules shared by every form.
Key takeaways
- Start with a Form Styler preset close to your design.
- Some advanced styling controls need Fluent Forms Pro.
- Per-form Custom CSS keeps changes to one form.
- Inspect the form to find the right CSS classes.
- Specificity and caching cause most styling failures.
- Test styles on mobile and in error states.
How do you style Fluent Forms?
You style Fluent Forms with its built-in Form Styler presets and controls, the per-form Custom CSS box, your page builder's Fluent Forms widget, or your theme's Additional CSS for site-wide rules.
Fluent Forms gives you several layers of styling. Start with the simplest one that does the job, and only add custom CSS for the details the visual controls cannot reach.
Some advanced styling controls are part of Fluent Forms Pro. The free plugin still includes style presets and a custom CSS box, which covers most basic needs.
The free version is available from the Fluent Forms plugin page on WordPress.org. Keep it updated, because styling options are added and moved between releases.
New to the plugin? Our guide on how to use Fluent Forms in WordPress covers building and embedding your first form.
Which styling method should you use?
Use the Form Styler for colours, spacing and buttons, Custom CSS for exact tweaks to one form, a page builder widget when the form sits in a builder layout, and theme CSS for rules shared by every form.
This table compares the options.
| Method | Where it lives | Scope | Skill needed |
|---|---|---|---|
| Form Styler presets | Form editor, Style panel | One form | Beginner |
| Form Styler advanced controls | Form editor, Style panel (Pro) | One form | Beginner |
| Custom CSS box | Form Settings, Custom CSS/JS | One form | Intermediate |
| Block editor styling | Fluent Forms block sidebar | One placement | Beginner |
| Page builder widget | Elementor, Bricks and others | One placement | Beginner |
| Theme Additional CSS | Customizer or Site Editor | All forms | Intermediate |
Fluent Forms documents its styler in the official Form Styler guide.
How do you use the Fluent Forms Form Styler?
Open the form in the Fluent Forms editor, click the Style option at the top, pick a preset, then adjust the available controls for labels, inputs, buttons and messages.
Follow these steps:
- Go to Fluent Forms > All Forms and open your form.
- Click the Style option in the editor's top bar.
- Choose a preset style. One preset lets the form inherit your theme's styles.
- Expand sections such as container, labels, inputs, buttons and messages.
- Change colours, borders, spacing and typography.
- Save the style and preview the form.
The preview inside the styler updates as you change settings, which saves trips to the front end.
Exact section names and which controls are free or Pro can change between versions. Check the plugin's documentation if a control is missing.
How do you pick a style preset?
Start with the preset closest to your site's look, because presets set sensible defaults for every field type and you only need to adjust a few values afterwards.
The inherit theme style is useful when your theme already styles forms well. Fluent Forms then adds little styling of its own.
A plain default preset works better when your theme's form styles look dated or clash with the form layout.
Switch presets and check the preview on a real page. Fonts and button styles often come from the theme, so the same preset can look different on two sites.
How do you add custom CSS to one Fluent Form?
Open the form, go to Settings & Integrations, find the Custom CSS/JS section, and paste CSS that targets that form's fields, labels or submit button.
Per-form CSS keeps your changes tied to one form. Other forms on the site stay untouched.
To find the right selectors:
- View the page with the form on the front end.
- Right-click a field and choose Inspect.
- Note the classes on the form wrapper, field groups, inputs and button.
- Use a class that includes the form ID to limit rules to that form.
Fluent Forms uses consistent class names, such as ff-el-group for field groups, ff-el-form-control for inputs and ff-btn-submit for the submit button. The Fluent Forms custom CSS guide lists more.
What CSS changes are most common?
Most people change input borders and corner radius, field spacing, label font weight, the submit button colour and width, and the colour of error messages.
Typical tweaks include:
- Rounded input corners with border-radius.
- Larger padding on inputs for easier tapping on phones.
- A full-width submit button on mobile.
- A brand colour on the submit button and its hover state.
- Softer placeholder text colour.
- Clearer error messages in a strong red.
The MDN CSS reference explains each property if you are new to CSS.
Keep colour contrast high. Light grey placeholder text on white often fails accessibility checks.
Why are your Fluent Forms styles not applying?
Styles usually fail because a theme or builder rule is more specific, a cache serves old CSS, or the CSS targets the wrong class or form ID.
Inspect the element in your browser. Crossed-out rules in the Styles panel show which selector is winning.
Make your selector more specific, for example by adding the form's wrapper class in front. Use !important only as a last resort.
Clear your caching plugin, CDN and browser cache after each change. CSS minification can also delay updates until caches rebuild.
The MDN guide to CSS specificity explains why some rules override others. If the button colour is the problem, our guide on Fluent Forms button colour not working covers that case.
How do you style Fluent Forms in the block editor?
Recent Fluent Forms versions add styling controls to the Fluent Forms block, so you can adjust colours, typography and spacing from the block sidebar when embedding a form.
Add the Fluent Forms block to a page, pick your form, then open the block settings sidebar. Look for style tabs alongside the form selector.
Block-level styling applies only to that placement. The same form embedded on another page keeps its own look.
Fluent Forms explains this feature in its post on the Gutenberg block styler.
How do you style Fluent Forms in Elementor?
Use the Fluent Forms widget in Elementor and adjust the Style tab, which offers controls for labels, inputs, buttons and messages without writing CSS.
Search for Fluent Forms in the Elementor widget panel and drag it onto the page. Choose your form in the Content tab.
Then open the Style tab. Controls usually cover typography, colours, borders, spacing and button hover states.
Third-party Elementor add-ons also include Fluent Forms styler widgets with more options. Only install one if the built-in widget falls short. Our guide on Elementor page settings explains how page-level styles can affect embedded forms.
How do you style all Fluent Forms at once?
Add shared rules to your theme's Additional CSS, targeting the general Fluent Forms classes, so every form on the site gets the same base look.
This works well for brand-wide rules, such as button colour, input borders and font sizes.
In a classic theme, go to Appearance > Customize > Additional CSS. In a block theme, open the Site Editor's Styles panel and its Additional CSS option.
Combine both layers: site-wide CSS for brand basics, and per-form CSS or the Form Styler for one-off changes.
Keep site-wide rules simple. Broad selectors can accidentally change forms from other plugins, such as a newsletter signup or a WooCommerce checkout, if they share generic class names.
Prefix every rule with a Fluent Forms wrapper class so it only touches Fluent Forms output. That small habit prevents most clashes.
How do you test your form design?
Check the styled form on phones and desktops, submit test entries to see success and error states, and confirm the form still works after cache and optimisation plugins run.
Run through this list:
- Labels and placeholders are readable.
- Fields stack cleanly on narrow screens.
- Error messages are clear and visible.
- The success message matches your design.
- Focus outlines are visible for keyboard users.
Also make sure notifications still arrive after styling changes. If emails stop, see our guide on Fluent Forms email notifications not working.
If you are still deciding whether Pro's styling tools are worth it, see is Fluent Forms worth it.
Frequently asked questions
Can I style Fluent Forms without Pro?
Yes. The free plugin includes style presets and a per-form Custom CSS box, and you can also add CSS through your theme. Pro adds more visual controls in the Form Styler, so you need less custom CSS.
Where is the custom CSS option in Fluent Forms?
Open the form, go to Settings & Integrations, and look for the Custom CSS/JS section. CSS added there loads with that form only, so it will not affect other forms on your site.
Why does my Fluent Form look different from the styler preview?
Your theme or page builder may load its own form styles that override Fluent Forms, or a cache may serve old CSS. Inspect the element to find the winning rule, then clear every cache layer.
How do I make the Fluent Forms submit button full width?
Use the button width option in the Form Styler if your version has it. Otherwise add CSS targeting the submit button class and set its width to 100 percent, optionally only on small screens with a media query.
Can I use the same style on several Fluent Forms?
Yes. Add shared CSS to your theme's Additional CSS using the general Fluent Forms classes, so every form inherits it. Use the per-form styler or CSS box only for differences.
Sources
- Official Form Styler Fluent Forms Docs
- Styling / Custom CSS Fluent Forms Docs
- Gutenberg Block Styler in Fluent Forms Fluent Forms
- Specificity MDN Web Docs
- Fluent Forms plugin WordPress.org
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


