Troubleshooting
Elementor Pro Custom CSS Not Working: Causes and How to Fix It

Short answer
Elementor Pro custom CSS usually fails because of a syntax error, a selector that is not specific enough, misuse of the selector keyword, cached CSS files, or Elementor Pro being inactive. Inspect the element in your browser, fix the rule, then regenerate Elementor CSS and clear all caches.
Key takeaways
- Element CSS uses the selector keyword for the element wrapper.
- One missing brace can break every rule after it.
- Crossed out rules in DevTools mean something else is winning.
- Regenerate Elementor CSS files after changes.
- Remove unused CSS features can strip custom rules.
- Template CSS only affects that template.
Why is Elementor Pro custom CSS not working?
Elementor Pro custom CSS usually fails because of a syntax error, a selector that is not specific enough, a cache serving old CSS files, the wrong use of the selector keyword, or Elementor Pro being inactive.
Custom CSS in Elementor Pro is added in three places: on individual elements, in page settings, and globally in Site Settings. Each place has slightly different rules.
When nothing changes on the page, the CSS is usually not loading at all. When only some rules apply, the CSS is loading but being overridden.
This guide helps you tell those cases apart and fix each one. For general CSS problems outside Elementor, see our guide on CSS changes not showing.
Where can you add custom CSS in Elementor Pro?
You can add custom CSS to a single widget, container or section in its Advanced tab, to a whole page in page settings, or to the whole site in Site Settings > Custom CSS.
| Location | Scope | Best for |
|---|---|---|
| Element Advanced tab, Custom CSS | One widget or container | Small tweaks to one element |
| Page settings, Custom CSS | One page or template | Page-specific layout fixes |
| Site Settings, Custom CSS | Whole site | Global rules and overrides |
| Appearance > Customize > Additional CSS | Whole site, theme level | CSS that should survive builder changes |
Elementor explains the element-level option in its help article on custom CSS in Elementor Pro. The global option is covered on its global custom CSS page.
Putting CSS in the wrong place is a common reason it seems to do nothing. Element CSS only affects that element and its children.
Is Elementor Pro active and working?
Element and page custom CSS are Pro features, so if Elementor Pro is deactivated, failed to update, or its version does not match free Elementor, that CSS may stop being output.
Go to Plugins and check that both Elementor and Elementor Pro are active. Look for notices about version mismatches.
If the Custom CSS panel shows an upgrade prompt, Pro is not being detected. Reconnect your licence or reinstall Elementor Pro.
Our guide on Elementor Pro not working after an update covers version mismatch problems step by step.
Are you using the selector keyword correctly?
In element-level custom CSS, the word selector stands for that element's wrapper, so rules must start with selector or a child of it, otherwise they may not target what you expect.
For example, to change a heading's colour inside a widget, write:
selector .elementor-heading-title {
color: #1a1a1a;
}
Writing just a class name without selector applies the rule to every matching element on the page, not just this widget. That can look like the rule is not working when it is actually being overridden elsewhere.
The selector keyword only works in element CSS. In Site Settings or the theme's Additional CSS, use normal class names instead.
Is there a syntax error in your CSS?
A single missing brace, semicolon or quote can stop every rule after it from working, so check your CSS carefully before looking for other causes.
Common mistakes include:
- A missing closing brace at the end of a rule.
- A missing semicolon between declarations.
- Curly quotes copied from a word processor.
- A media query with an unclosed bracket.
- Comments that open but never close.
Paste your CSS into a validator to find errors fast. The W3C offers a free CSS validation service.
Is another rule overriding your CSS?
If the CSS loads but does not apply, another rule with higher specificity or loaded later is probably winning, and you can confirm this in your browser's developer tools.
Right-click the element and choose Inspect. In the Styles panel, look for your rule. If it is crossed out, another rule is overriding it.
Chrome's guide to viewing and changing CSS shows how to read this panel.
Fix it by making your selector more specific, for example by adding a parent class. MDN explains how browsers rank rules in its guide to CSS specificity.
Use !important only as a last resort. It makes later changes harder.
Is your CSS only working on some devices?
Custom CSS applies to all screen sizes unless you wrap it in a media query, and Elementor's own responsive settings may override it on tablet or mobile.
If a rule works on desktop but not on mobile, check whether the widget has different responsive values set in its Style tab. Those can be more specific than your CSS.
To target one device size, use a media query that matches your Elementor breakpoints. MDN's guide to using media queries explains the syntax.
Our explainer on Elementor breakpoint settings shows where to find your exact breakpoint widths.
Is a cache serving old CSS files?
Elementor writes styles to generated CSS files, so after changing custom CSS you often need to regenerate those files and clear your cache plugin, server cache and CDN.
In WordPress, go to Elementor > Tools and use the option to regenerate CSS and data. Then clear every other cache layer.
Test in a private browser window while logged out. Browser caches often hold old stylesheets.
Our guide on clearing the cache in Elementor walks through each step.
Is the CSS print method causing problems?
Elementor can load styles as external files or embed them in the page, and switching between these methods can fix CSS that does not appear when files fail to generate.
The setting is in Elementor's settings screen, under the performance or advanced options depending on your version. External files are usually faster, but they need a writable uploads folder.
If external files are not being created, try the internal embedding option as a test. If CSS starts working, fix the folder permissions and switch back.
Our explainer on Elementor performance settings covers this option and others.
Is an optimisation plugin removing your CSS?
Features that remove unused CSS or combine stylesheets can strip or reorder Elementor's custom CSS, especially for elements that only appear after interaction.
Turn off remove unused CSS and combine CSS in your optimisation plugin, clear caches and test again.
If that fixes it, add Elementor's CSS files or your custom classes to the plugin's safelist. Our guide on removing unused CSS in WordPress explains how safelists work.
Is the CSS in the right template?
If your CSS targets a header, footer or single post template, add it to that template in the Theme Builder, because CSS on a normal page does not reach elements built in other templates.
Each template is a separate document with its own CSS. Page-level CSS only loads on that page.
For rules that should apply everywhere, use Site Settings custom CSS instead. Our guide to Elementor Pro site settings shows where it sits.
What if nothing works?
If you have checked everything above, test for a plugin or theme conflict, and as a fallback add the CSS to your theme's Additional CSS or a child theme stylesheet.
Use the Health Check and Troubleshooting plugin to disable other plugins for your session only.
Moving CSS to the theme level is a reliable workaround. It loads independently of Elementor's file generation.
Keep a copy of all custom CSS in a text file. That makes it easy to restore after updates or if you change where it lives.
Frequently asked questions
Does Elementor free include custom CSS?
Element and page level custom CSS fields are part of Elementor Pro. Free users can still add CSS through the theme's Additional CSS in the Customizer, a child theme, or a code snippets plugin, and use CSS classes set in the Advanced tab.
Why does my Elementor custom CSS work in the editor but not on the live site?
The editor loads styles directly, while the live page uses generated CSS files that may be cached. Regenerate CSS in Elementor's tools, clear your cache plugin, server cache and CDN, and test in a private window.
What does selector mean in Elementor custom CSS?
In element level custom CSS, selector is replaced with the unique class of that widget or container. It lets you target only that element without knowing its generated class name. It does not work in global or theme CSS fields.
Will my Elementor custom CSS stop working if my licence expires?
Elementor Pro features generally keep working when a licence expires, but you stop receiving updates and support. If Pro is deactivated or removed, element and page custom CSS will no longer load, so keep a copy of important rules.
Should I use important in Elementor custom CSS?
Only as a last resort. It forces a rule to win but makes later changes harder to manage. A more specific selector, such as adding a parent class or the selector keyword, usually solves the problem more cleanly.
Sources
- Custom CSS (Pro) Elementor Help Center
- Global Custom CSS Elementor Help Center
- Specificity MDN Web Docs
- View and change CSS Chrome for Developers
- 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.


