Troubleshooting
Fluent Forms Button Color Not Working: Causes and How to Fix It

Short answer
A Fluent Forms button colour usually fails to change because your theme or page builder styles override it, or a cache is still serving old CSS. Set the colour in the submit button settings, clear every cache, inspect the button to find overriding rules, and add a specific CSS rule for the submit button if needed.
Key takeaways
- Theme and page builder button styles are the most common cause.
- Set the colour in one place to avoid conflicting settings.
- Clear plugin, server, CDN and browser caches after every change.
- Use a specific CSS rule on the submit button class, with important as a last resort.
- Set hover and focus colours separately and check contrast.
Why is the Fluent Forms button colour not working?
The Fluent Forms button colour usually does not change because your theme or page builder CSS overrides it, a cache is serving old styles, or the colour was set in a place that a later style setting replaces.
Fluent Forms gives you several places to style the submit button. When two of them disagree, or your theme adds its own button styles, the colour you picked may never reach the screen.
The good news is that the fix is almost always CSS or settings, not a broken plugin. Work through the checks below in order.
If you are new to the plugin, our overview of what Fluent Forms does explains how its forms are built.
Where can you set the submit button colour in Fluent Forms?
You can set the button colour in the submit button's own settings, in the form styler, in a page builder widget, or with custom CSS, and the most specific rule wins.
Here are the usual places, from simplest to most powerful:
| Where | What it controls | Notes |
|---|---|---|
| Submit button settings | Button style, background and text colour | Click the submit button in the form editor |
| Form styler | Colours, spacing and fonts for the whole form | Some styler options depend on your plan |
| Page builder widget | Button styles when the form sits in Elementor or similar | Overrides plugin styles on that page |
| Custom CSS | Any style you write | Most control, needs care with specificity |
Pick one place and stick to it. Setting the colour in three places at once makes it hard to know which one is winning.
The Fluent Forms styling documentation explains the styling options available in your version.
How do you change the colour in the submit button settings?
Open the form in the editor, click the submit button, choose a custom button style, set the background and text colours, then save the form.
Steps:
- Go to Fluent Forms and edit your form.
- Click the submit button at the bottom of the form.
- In the settings panel, find the button style option.
- Choose a custom style instead of the default.
- Set the background colour, text colour and hover colours if shown.
- Click Save Form and check the live page.
If the colour pickers do not appear, you may still be on the default style. Switching to a custom style usually reveals them.
Some forms use a custom submit button field instead of the standard button. That field has its own style settings, so edit it directly rather than looking for the default submit button options.
After saving, reload the live page rather than relying on the editor preview. The editor does not load your theme, so it cannot show theme overrides.
Is your theme overriding the button colour?
Very often, yes. Many themes style every button or submit input on the site, and a theme rule with higher specificity or !important beats the Fluent Forms setting.
To check, right-click the button on the live page and choose Inspect. In the styles panel, look for your colour with a line through it, which means another rule wins.
The winning rule shows which file it comes from. If it points to your theme's stylesheet, the theme is the cause.
The Chrome DevTools CSS guide shows how to read crossed-out rules and find their source.
Page builders cause the same problem. Elementor global colours and button styles, for example, can apply to any button inside an Elementor section.
How do you fix the colour with custom CSS?
Add a CSS rule that targets the Fluent Forms submit button class with enough specificity, and add !important only if a theme rule still wins.
Fluent Forms adds its own classes to the submit button. A rule like this usually works:
.fluentform .ff-btn-submit {
background-color: #1e6bd6;
color: #ffffff;
border-color: #1e6bd6;
}
.fluentform .ff-btn-submit:hover {
background-color: #174fa0;
color: #ffffff;
}
If the theme still wins, raise specificity by adding the form's ID class, or add !important to the colour lines.
Add the CSS in the form's custom CSS settings, in Appearance > Customize > Additional CSS, or with a snippets plugin. Our guide on adding code to WordPress covers the safe options.
The MDN guide to CSS specificity explains why one rule beats another.
Could caching hide your colour change?
Yes, if a caching plugin, server cache or CDN serves an old copy of the page or stylesheet, your new colour will not show until every cache is cleared.
This is one of the most common reasons a change looks like it failed. The setting saved, but visitors still get the old CSS.
Clear the cache in this order:
- Your caching plugin.
- Your host's server cache, if it has one.
- Your CDN, such as Cloudflare.
- Your browser, or test in a private window.
Optimisation plugins that combine CSS files can also keep old styles. Regenerate their combined files after clearing the cache.
Our guide on fixing CSS changes not showing covers each layer in more detail.
Why does the colour work in the editor but not on the page?
The editor shows the form with only Fluent Forms styles, while the live page also loads your theme, page builder and optimisation plugins, so their styles can override yours.
That gap is normal. Always judge the colour on the live page, logged out, in a private window.
If the form is embedded with an Elementor or other builder widget, check the widget's style tab. Builder widgets often have their own button colour settings that sit above the plugin's.
For Elementor users, our guide on using Elementor in WordPress shows where widget style settings live.
What if only the hover or focus colour is wrong?
Hover and focus colours are separate states, so you must set them separately, either in the button settings or with :hover and :focus rules in CSS.
A button can look right until someone points at it. Themes often set a hover colour for every button, which then overrides yours on hover only.
Add a focus style too. Keyboard users rely on a visible focus outline to know where they are on the page.
.fluentform .ff-btn-submit:focus-visible {
outline: 3px solid #174fa0;
outline-offset: 2px;
}
Check colour contrast between the button and its text. The WebAIM contrast checker shows whether your colours meet accessibility guidelines.
Could a plugin conflict cause the problem?
Rarely, but yes, a plugin that injects global styles, such as a dark mode plugin or another form plugin, can override the Fluent Forms button colour.
Test by switching to a default theme on a staging copy and disabling other plugins. If the colour works, reactivate items one at a time until it breaks.
Our guide on finding which plugin is causing a problem walks through that method.
Update Fluent Forms too. Styling bugs are sometimes fixed in newer releases, and the Fluent Forms listing on WordPress.org shows the latest version and changelog.
What is the quickest checklist to fix it?
Set the colour in one place, clear every cache, inspect the button for overriding rules, then add a specific CSS rule with !important if the theme still wins.
- Choose a custom button style in the submit button settings.
- Save the form and clear all caches.
- Inspect the live button for crossed-out colour rules.
- Check builder widget styles if the form sits in a page builder.
- Add a targeted CSS rule for normal, hover and focus states.
- Test logged out in a private window and on a phone.
Once it works, note where you set the colour. The next person to edit the site will thank you.
Frequently asked questions
Why does my Fluent Forms button stay the theme colour?
Your theme probably styles all buttons with a rule that is more specific than the Fluent Forms setting. Inspect the button, find the theme rule, then add a more specific CSS rule targeting the Fluent Forms submit button class, using important only if needed.
Where do I add custom CSS for Fluent Forms?
You can add CSS in the form's custom CSS settings inside Fluent Forms, in the WordPress Customizer under Additional CSS, or with a code snippets plugin. Avoid editing plugin files, because updates overwrite them.
Do I need Fluent Forms Pro to change the button colour?
Basic button colour options and custom CSS are available in the free version. Some advanced styler options may depend on your plan, so check the current Fluent Forms documentation for the exact split.
Why does the button colour change back after an update?
If you edited plugin or theme files directly, updates replace them. Move your CSS into the Customizer, a child theme or a snippets plugin. Also check that a caching or optimisation plugin did not restore old combined files.
How do I change the button hover colour in Fluent Forms?
Set the hover colours in the submit button settings if your version shows them, or add a CSS rule using the hover state on the submit button class. Remember to set a visible focus style for keyboard users too.
Sources
- Fluent Forms Styling and Custom CSS Fluent Forms
- Fluent Forms WordPress.org Plugin Directory
- Specificity MDN Web Docs
- View and change CSS Chrome for Developers
- Contrast Checker WebAIM
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.


