Troubleshooting CSS - WPForms (2024)

Have you created custom CSS for your forms, but haven’t been able to see those styles when viewing your site? There are a few common issues that can cause CSS not to appear correctly on a site.

This tutorial will walk through options to troubleshoot why your CSS is not working and offer possible solutions.

In This Article

Browser Caching
Invalid CSS Format
CSS Specificity

Note: If you’d prefer not to use custom CSS to style your forms, consider checking out our form styling tutorial to learn how to style your forms in the block editor.

Browser Caching

Browsers often cache or temporarily store resources from websites you visit to improve load speed. Some sites will also use plugins for additional caching. Often when you don’t see your custom styles on your site, it’s because the browser or other system has cached an older version of your site.

Here’s a tutorial that’ll walk you through the main steps to clear your site and plugin caches.

If clearing your browser cache doesn’t seem to work, here are a couple of additional strategies to try:

Trying a Different Browser

Each browser will keep its cache of the sites you visit. By opening your site in a different browser (or in the private mode offered by some browsers, such as Chrome’s incognito window), you can often see an uncached version of your site.

Asking Your Host if They Have a Cache

Some hosts will provide caching for your site right on their servers, which is where your site’s files are stored. If you’re not sure, you may want to contact your host to ask if they are caching your site and, if they are, ask them to clear that cache for you.

Trying a Different Internet Source

Occasionally, just loading your site over a different internet source can help to bypass an existing cache. If you have a mobile device with available data, the simplest way to do this is to temporarily turn off WiFi on your device and reload the page.

Invalid CSS Format

CSS must be written in a specific format in order for a browser to understand it. There are many online tools to check that your CSS is valid, including W3School’s CSS Validator. This is an excellent option if you have a lot of custom CSS and at least a little previous experience creating CSS.

If you are only using a small amount of CSS, however, it may sometimes be easier to do a quick format check of your own. Let’s start by looking at a snippet of valid CSS:

div.wpforms-container-full .wpforms-form .wpforms-title { font-size: 26px; margin: 0 0 10px 0;}

Here’s why this CSS is valid or ‘readable’ by browsers:

Correct selector format: If the selector includes multiple parts, it needs to be written from ‘biggest’ to ‘smallest’. In the example above, div.wpforms-container-full is the biggest container element in the HTML, while .wpforms-form is inside of that container. The smallest and last item in the selector, .wpforms-title, is contained inside of both of those other elements. In any other order, the browser won’t be able to read this selector.
Two brackets: There must be an opening curly bracket ({) right after the CSS selector and at the end of the property and value list. Forgetting that closing bracket (}) is a common mistake, and will usually prevent all CSS below it from being shown in the browser.
Colon and semicolon: Be sure to include a colon (:) between every CSS property and value, and a semicolon (;) after every value so the browser can read your CSS (for example, font-size: 26px;).
Correct use of whitespace: For the most part, CSS isn’t very picky about whitespace (which includes tabs and spaces). An exception to this, however, is for units. 26px will work, for example, while 26 px will not.

For more information on writing CSS with proper syntax, you can check out this tutorial from W3Schools.

CSS Specificity

Since all themes and most plugins contain their own sets of styles, you will often find that your custom styles must “compete” against existing styles. In such situations, the more specific CSS selector will almost always win out over a less specific selector.

Using !important in CSS

In some situations, you can force a less specific snippet of CSS to work by including the !important rule before the semicolon. It’s always better to try a more specific selector (as described above) first, but sometimes this can offer a quick fix.

It’s important to note, however, that adding the !important rule won’t always work. Let’s try this approach for the CSS we discussed in the last example:

.wpforms-title { font-size: 40px !important;}

In this situation, the browser prefers the specificity of the default CSS over the !important rule, so this CSS will not be applied to your site.

Let’s look at an example where adding the !important rule does work. By default, the asterisk (*) that marks a ‘required’ field in WPForms will be red:

Here is the CSS that creates that style (#ff0000 is a hex code for the color red):

div.wpforms-container-full .wpforms-form .wpforms-required-label { color: #ff0000;}

We want to make these asterisks appear blue instead. We could copy that full selector from the CSS above, or we could use a short selector and add the !important rule, as in this CSS snippet:

.wpforms-required-label { color: #007acc !important;}

It can be tough to know whether or not the !important rule will work, so you’ll likely need to give it a shot and test it out.

That’s it! We’ve covered the most common troubleshooting strategies to use when CSS isn’t working. If you’re still having trouble styling your WPForms, please get in touch with support so we can help you out.

Next, would you like to further customize your forms? Check out our tutorial on customizing individual form fields for details and examples.