Title: Cache keeps old CSS
Last modified: April 8, 2026

---

# Cache keeps old CSS

 *  Resolved [caroledesignview](https://wordpress.org/support/users/caroledesignview/)
 * (@caroledesignview)
 * [1 month, 4 weeks ago](https://wordpress.org/support/topic/cache-keeps-old-css/)
 * Even after purging cache, old CSS loads for some users. Is there a cache-busting
   option for CSS files?

Viewing 1 replies (of 1 total)

 *  Plugin Author [owaisalam](https://wordpress.org/support/users/owaisalam/)
 * (@owaisalam)
 * [1 month, 3 weeks ago](https://wordpress.org/support/topic/cache-keeps-old-css/#post-18877065)
 * Hi,
 * Thank you for bringing this up.
 * Breeze does include a built-in CSS cache-busting mechanism, but it only works
   when **CSS Minification** is enabled.**How Breeze Handles CSS Cache-Busting**
 * When **CSS Minification** is enabled (Breeze → Settings → File Optimization →
   Minify CSS), Breeze generates combined/minified CSS files and appends a **timestamp-
   based version parameter** (e.g., `?ver=1712764800`).
 * This ensures that whenever the cache is purged, the CSS file URL changes and 
   browsers are forced to download the updated version.**Why Old CSS May Still Load
   After Purging**
 * There are a few common reasons why stale CSS may persist:
 * **1. CSS Minification is disabled**
   If CSS minification is not enabled, Breeze
   serves the original CSS files with their existing `?ver=` parameters (set by 
   WordPress or the theme). In this case, purging the cache does not update the 
   version, so browsers may continue using the cached files.
 * **Solution:** Enable **CSS Minification** under Breeze → Settings → File Optimization.
 * **2. Browser Cache is enabled (long cache duration)**
   When Browser Cache is enabled(
   Breeze → Basic Options), CSS files can be cached in the browser for up to 30 
   days. Even after purging server-side cache, users may still see older CSS from
   their local browser cache.
 * **Solution:** Ask users to perform a hard refresh (`Ctrl + Shift + R` on Windows
   or `Cmd + Shift + R` on Mac) or clear their browser cache.
 * **3. Excluded CSS files**
   If certain CSS files are added to the exclusion list(
   Breeze → File Optimization → Exclude CSS), they bypass Breeze’s cache-busting
   mechanism and retain their original URLs.
 * **Solution:** Review the exclusion list and remove any files that don’t need 
   to be excluded.**Recommended Steps**
    - Enable **CSS Minification** in Breeze
    - Purge all cache using the Breeze admin bar
    - Ask users to hard refresh their browser for immediate results
 * These steps should resolve the issue with stale CSS. Please let us know if you
   need any further assistance

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcache-keeps-old-css%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/breeze/assets/icon-256x256.gif?rev=3352595)
 * [Breeze Cache](https://wordpress.org/plugins/breeze/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/breeze/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/breeze/)
 * [Active Topics](https://wordpress.org/support/plugin/breeze/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/breeze/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/breeze/reviews/)

## Tags

 * [cache](https://wordpress.org/support/topic-tag/cache/)
 * [css](https://wordpress.org/support/topic-tag/css/)

 * 1 reply
 * 2 participants
 * Last reply from: [owaisalam](https://wordpress.org/support/users/owaisalam/)
 * Last activity: [1 month, 3 weeks ago](https://wordpress.org/support/topic/cache-keeps-old-css/#post-18877065)
 * Status: resolved