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

Short answer
WPBakery custom CSS usually fails because the page was not updated after saving the CSS, a more specific theme rule overrides it, or a syntax error breaks the block. Design Options values, cached or minified files and wrong selectors are the other common causes.
Key takeaways
- Update the page after saving page-level CSS.
- Use the inspector to see which rule wins.
- One syntax error can break every rule after it.
- Design Options can override your custom CSS.
- Clear caches and test with minify off.
- Extra class names make targeting reliable.
Why is WPBakery custom CSS not working?
WPBakery custom CSS usually fails because theme styles with higher specificity override it, the CSS has a syntax error, the page was not updated after adding it, or a cache or minify plugin is serving old files.
WPBakery Page Builder gives you a few places to add CSS. There is a site-wide box in the plugin settings, a per-page box in the editor, and design options on each element.
When your rules do nothing, the browser is either not loading them or something stronger is winning. Finding out which one is the key to the fix.
This guide works through the causes from most to least common, with a quick way to test each.
Where can you add custom CSS in WPBakery?
You can add custom CSS globally in the WPBakery settings, per page in the editor's page settings, and per element through Design Options and extra class names.
The table shows each option and when it loads.
| Location | Where to find it | Applies to |
|---|---|---|
| Global Custom CSS | WPBakery Page Builder, then Custom CSS | Every page built with WPBakery |
| Page custom CSS | Page settings icon in the editor bar | That page only |
| Design Options | Element settings, Design Options tab | That element only |
| Extra class name | Element settings, General tab | Lets you target it from other CSS |
WPBakery's knowledge base explains these in its custom CSS article. The site-wide box is covered in the WPBakery Page Builder settings guide.
If you are not sure where a rule was added, check all four. Old rules in one place can fight new rules in another.
New to the builder? Our guide on how to use WPBakery Page Builder explains the editor layout first.
Did you save and update the page?
CSS added in the page settings box only takes effect after you click Save Changes in the box and then Update or Publish for the page itself.
This is the most common cause. The page settings window has its own save button, but that only stores the CSS in the editor.
You still need to update the page. Until then, visitors see the old version.
For global CSS, click Save Changes at the bottom of the settings screen. Then reload the front end in a private window to avoid your own browser cache.
Is another style overriding your CSS?
Most of the time the CSS loads fine but loses to a more specific rule from the theme or WPBakery itself, so the browser applies the other style instead.
CSS follows rules of specificity and order. A selector like .vc_row .wpb_column .vc_btn3 beats a simple .vc_btn3. MDN explains how this works on its CSS specificity page.
To check, right-click the element and choose Inspect. In the styles panel, look for your rule. If it is crossed out, another rule is winning.
Fixes, from cleanest to bluntest:
- Make your selector more specific, for example by adding a parent class.
- Give the element an Extra class name and target that.
- Move your CSS so it loads after the theme's CSS.
- Use
!importanton the one property that must win.
Avoid adding !important to everything. It makes future changes harder.
Is there a syntax error in your CSS?
A single missing brace, semicolon or quote can stop every rule after it from working, so one typo can make a whole block of CSS look broken.
Look for:
- Missing closing
}braces. - Missing
;between properties. - Curly quotes pasted from a word processor.
- Comments that open with
/*but never close. - Invalid property names or values.
Paste your CSS into the W3C CSS validator to find errors quickly. It shows the line number of each problem.
If only the rules near the bottom fail, the error is usually just above the first broken rule.
Are Design Options overriding your CSS?
Design Options on an element output their own CSS for that element, and that generated CSS can override rules you wrote in the custom CSS boxes.
For example, if you set padding in Design Options and also set padding in custom CSS, the Design Options value may win because of how it is targeted.
Open the element, go to Design Options, and clear values that conflict with your custom rules. Then save and update.
The same applies to responsive settings. Values for different screen sizes can override desktop rules. Our guide on WPBakery responsive settings explains how those layers interact.
Is caching or minification serving old CSS?
Caching and optimization plugins can keep serving an old copy of your CSS, or break it while combining files, so changes do not appear on the front end.
Signs include CSS working in the editor but not on the live page, or working for you but not for visitors.
Try this:
- Clear your caching plugin.
- Clear any server cache from your hosting panel.
- Purge your CDN.
- Turn off CSS minify and combine options, then test.
- Hard refresh the page or use a private window.
If turning off minify fixes it, exclude WPBakery's CSS from optimization rather than leaving minify off everywhere.
Is your selector targeting the right element?
If your selector does not match the HTML on the page, the CSS will load but never apply, so check the real class names in the browser inspector.
WPBakery wraps content in its own classes like vc_row, wpb_column and wpb_wrapper. Theme and add-on elements add their own classes too.
The easiest way to target one element reliably is to add an Extra class name in its General tab, such as hero-button. Then write .hero-button in your CSS.
Note that some elements put the class on an outer wrapper, not the inner button or text. Inspect the page to see where your class lands and adjust the selector.
Are media queries or responsive rules hiding the change?
CSS inside a media query only applies at certain screen widths, so a rule written for mobile will not show on desktop, and the reverse.
Check that your media query matches the device you are testing on. A rule inside @media (max-width: 767px) only runs on narrow screens.
Use the device toolbar in your browser's developer tools to test different widths without changing devices.
Could a plugin conflict or outdated version be the cause?
Yes. An outdated WPBakery version, a theme bundling an old copy, or a conflicting plugin can stop custom CSS from loading at all.
Many themes bundle WPBakery. If the theme ships an old version, update the theme or ask the theme author for the latest bundled copy.
To test for conflicts, use the Health Check & Troubleshooting plugin. It turns plugins off only for your session.
If WPBakery itself is misbehaving, our guide on WPBakery Page Builder plugin not working covers broader fixes.
Where else can you put CSS if WPBakery's box will not work?
You can add CSS in the theme's Customizer Additional CSS panel or a child theme stylesheet, both of which load site-wide and are easy to manage.
Classic themes offer Appearance, then Customize, then Additional CSS. Child theme stylesheets are best for larger amounts of CSS.
Keeping CSS in one place makes it far easier to troubleshoot later. If you split rules across WPBakery, the Customizer and a child theme, write a short comment above each block noting where it belongs.
Similar issues happen in other builders too. See our guide on Elementor Pro custom CSS not working for comparison.
Form plugins have their own quirks with styling. Our guide to Forminator CSS not working covers those.
Frequently asked questions
Where is the custom CSS option in WPBakery?
Site-wide CSS lives in the WPBakery Page Builder menu under Custom CSS. Page-level CSS is in the page settings window, opened from the icon in the editor bar. Element styling is in each element's Design Options tab.
Why does my WPBakery CSS work in the editor but not on the live page?
This usually means a cache or optimization plugin is serving old or broken CSS, or the page was not updated after saving. Clear every cache, turn off CSS minify to test, and update the page.
Should I use !important in WPBakery custom CSS?
Use it sparingly, only on a property that must override a stubborn theme rule. A more specific selector or an extra class name is usually a cleaner fix and keeps future changes easier.
How do I target one WPBakery element with CSS?
Open the element's settings and add a word in the Extra class name field on the General tab. Then target that class in your custom CSS. Inspect the page to confirm which wrapper the class is added to.
Does WPBakery custom CSS work with every theme?
It works with most themes, but themes that bundle an old WPBakery version or load very specific styles can block it. Update the theme and WPBakery, then use more specific selectors where needed.
Sources
- Custom CSS WPBakery Knowledge Base
- WPBakery Page Builder Settings WPBakery Knowledge Base
- Specificity MDN Web Docs
- CSS Validation Service W3C
- Health Check & Troubleshooting 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.


