Troubleshooting
Forminator CSS Not Working: Causes and How to Fix It

Short answer
Forminator CSS usually fails because a more specific theme rule overrides it, the selector targets the wrong element, a cache serves old styles, or the form's design style takes over. Inspect the field, add CSS in the form's Custom CSS box, prefix rules with the form ID, and clear every cache.
Key takeaways
- Inspect the field first to see if your rule loads or is crossed out.
- Add CSS in the form's Appearance tab so it is scoped to that form.
- Prefix selectors with the form ID to beat theme specificity.
- Built-in design styles and colours can override your rules.
- Clear page, CDN and browser caches after every change.
- Validate CSS because one syntax error can break later rules.
Why is Forminator CSS not working?
Forminator CSS usually fails because a more specific theme or plugin rule overrides it, the selector is wrong, a cache serves an old stylesheet, or the form's design style blocks your changes.
Most cases come down to one of five things. The rule never loads, it loads but loses a specificity battle, it targets the wrong element, the browser or server shows an old copy, or the Appearance settings in the form editor take over.
The fastest way to find out which one applies is to inspect the field in your browser. That tells you in seconds whether your rule is present and whether something is striking it out.
If the whole form is missing rather than unstyled, that is a different problem. Our guide on Forminator not showing covers drafts, shortcodes and blocked scripts.
Where should you add custom CSS for Forminator?
The safest place is the Custom CSS box in the form's Appearance tab, because Forminator scopes it to that form and loads it with the form.
Open Forminator > Forms, edit the form, and go to the Appearance tab. Scroll to the Custom CSS section and add your rules there. Forminator usually inserts a form-specific wrapper selector for you, so rules apply only to that form.
You can also add CSS in Appearance > Customize > Additional CSS in a classic theme, in the Site Editor's custom CSS in a block theme, or in a child theme stylesheet. These work for every form on the site, but they load in a different order, so they may need more specific selectors.
Avoid editing files inside the Forminator plugin folder. Updates replace those files, so your changes would disappear. The WordPress child theme handbook explains a safer place for site-wide styles.
Is the form's design style overriding your CSS?
Yes, quite often: Forminator's built-in design styles and colour settings print their own CSS, which can beat a generic rule you wrote elsewhere.
In the Appearance tab, Forminator offers several design styles such as Default, Flat, Bold and Material, plus an option to drop its styles and let the theme take over. Each style ships with its own CSS rules for inputs, labels and buttons.
If you set custom colours in the Appearance tab, those colours are also printed as CSS. A rule such as input { background: #fff; } in your theme will lose to them because Forminator's selectors are longer and more specific.
You have two clean options. Style the form inside the Appearance tab with the built-in colour, font and spacing controls. Or switch the design style to the option that removes Forminator's styling, then write your own CSS from scratch.
Mixing both approaches is where most frustration starts. Pick one and stick with it for each form.
How do you check whether your CSS rule is loading?
Right-click the field, choose Inspect, and look at the Styles panel; if your rule is missing, it is not loading, and if it is crossed out, something overrides it.
Browser developer tools are the most useful debugging aid here. Chrome DevTools and Firefox's inspector both show every rule applied to an element, in order, with the file it came from.
Look for three patterns:
- Rule not listed at all. The CSS is not on the page, or the selector does not match the element.
- Rule listed but struck through. Another rule with higher specificity or
!importantwins. - Rule listed and active, but no visual change. You may be styling a wrapper rather than the actual input, label or button.
Note the exact class names Forminator uses on the element. Forminator wraps forms in classes such as forminator-ui and forminator-custom-form, and gives each form an ID based on its form number. Copy selectors from the inspector rather than guessing them.
Is CSS specificity the problem?
Very often it is: Forminator uses long, chained selectors, so a short rule from your theme or Additional CSS loses even when it loads later.
CSS applies the rule with the highest specificity, and only uses source order to break ties. MDN's specificity guide explains how IDs, classes and element names are weighted.
A rule like .forminator-button { background: red; } has one class. Forminator's own rule may combine the form wrapper, a design attribute and the button class. That beats yours every time.
Make your selector at least as specific as the one you see in the inspector. Prefixing with the form's ID is usually enough:
#forminator-module-123 .forminator-button-submit {
background: #1d4ed8;
border-radius: 6px;
}
Replace 123 with your form's ID, which you can see in the form shortcode. Use !important only as a last resort, because it makes later changes harder.
Could caching or minification be serving old styles?
Yes; page caches, CSS minification and CDN caches can keep serving an old stylesheet, so your new rules never reach the browser.
Clear every cache layer after each CSS change. That includes your caching plugin, any server cache from your host, a CDN such as Cloudflare, and your browser cache. A private window helps confirm what logged-out visitors see.
CSS optimisation features cause a second kind of problem. Combining, minifying or removing unused CSS can strip rules that Forminator loads only when a form is present. If styles break only for visitors, exclude Forminator's stylesheets from these features.
Our walkthrough on how to clear cache in WordPress lists where each cache usually lives.
Is your theme or page builder overriding the form?
Themes and builders often set global styles for inputs, buttons and labels, and those rules can override or mix with Forminator's styling.
Many themes style input, select, textarea and button elements globally. When the theme rule is more specific, or uses !important, it wins over Forminator.
To confirm, switch temporarily to a default theme such as Twenty Twenty-Five on a staging copy and reload the form. If the styling looks right there, the theme is involved.
Page builders add another layer. Elementor, Divi and others may wrap the form in containers with their own typography and spacing. If you embed forms that way, our guide on using Forminator in Elementor shows where builder settings can clash with the form's own design.
Are you targeting the right element?
Many CSS changes fail because they target the wrapper or label instead of the actual input, button or dropdown element that you can see.
Forminator builds fields from several nested elements. A text field has a wrapper, a label, the input itself and sometimes a description. Dropdowns may use a styled replacement instead of the native select element.
If you set a width on the field wrapper, the input may still stretch to fill it. If you style a native select that Forminator hides, nothing changes on screen.
Use the inspector to click the exact element you want to change, then copy its class. For sizing problems in particular, see our guide on how to make a field in Forminator smaller.
Does the CSS have a syntax error?
A single missing brace or semicolon can stop every rule after it from working, so check your CSS for syntax errors before blaming the plugin.
Browsers skip invalid declarations quietly. A missing closing brace can swallow the rest of the stylesheet, so it looks as if nothing works.
Paste your code into the W3C CSS Validator to catch errors quickly. Also check for curly quotes copied from a word processor, which break selectors and values.
Keep Forminator rules grouped together with a short comment. That makes problems easier to spot later.
Which fix matches which symptom?
Match what you see to the likely cause below, then apply the fix in that row before trying anything else.
| Symptom | Likely cause | Fix |
|---|---|---|
| Rule missing in inspector | Not loaded or selector mismatch | Move CSS to the form's Custom CSS box and copy selectors from the inspector |
| Rule crossed out | Specificity or !important | Prefix with the form ID |
| Works for admins, not visitors | Page or CDN cache | Clear all caches and exclude Forminator CSS from optimisation |
| Styles change after switching theme | Theme global styles | Increase specificity or adjust theme rules |
| Nothing after a certain rule works | Syntax error | Validate the CSS |
| Colours keep reverting | Appearance tab colours | Change colours in the form editor or remove its styles |
How do you stop Forminator CSS issues coming back?
Keep custom styles in one place, use form-specific selectors, and retest forms after plugin, theme or cache setting changes.
Forminator updates can change class names or markup now and then. Check the changelog on the Forminator plugin page before updating, and test on staging when a form matters for leads or payments.
If you style many forms the same way, Forminator's appearance presets let you save one design and apply it to other forms. WPMU DEV describes this in its post on global appearance presets.
If you are still learning the plugin, our Forminator beginner guide covers form settings beyond styling.
When nothing works, collect the page URL, your CSS, and a screenshot of the inspector, then post on the plugin's support forum. That information gets you a faster answer.
Frequently asked questions
Where is the Custom CSS option in Forminator?
Edit the form, open the Appearance tab, and scroll to the Custom CSS section. Rules added there load with that form and are scoped to it, which makes them less likely to clash with other forms or your theme.
Why does my Forminator CSS work in the editor but not on the live page?
A page cache, CDN cache or CSS optimisation feature is usually serving an older or stripped stylesheet. Clear every cache layer, exclude Forminator styles from combine and unused CSS features, and check the page in a private window.
Should I use !important in Forminator CSS?
Only as a last resort. A more specific selector, such as one that starts with the form ID, normally wins without it. Overusing important flags makes future styling changes harder, because each new rule then needs its own important flag too.
How do I find the Forminator form ID for CSS?
The form ID appears in the form shortcode in your Forminator forms list. On the page, the form wrapper carries an ID based on that number, which you can see by inspecting the form in your browser.
Can my theme stop Forminator styles from working?
Yes. Many themes style inputs and buttons globally, sometimes with important flags. Test the form with a default theme on a staging copy. If it looks right there, raise the specificity of your Forminator rules or adjust the theme styles.
Sources
- Forminator WordPress.org Plugin Directory
- Use a Form's Style Everywhere with Forminator's Global Appearance Presets WPMU DEV
- Specificity MDN Web Docs
- View and change CSS Chrome for Developers
- Child Themes WordPress Developer Resources
- CSS Validation Service W3C
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.


