Troubleshooting · Guide
How to Clear Every Cache Layer in WordPress
Short answer
Clear the caching plugin first, then the host server cache, then the CDN cache, and finally your browser cache. Clearing one layer does not clear the others, so work outward from WordPress and check the result in a private window after each step.
Key takeaways
- Clear layers in order: plugin, host server cache, CDN, then browser cache.
- Purging the CDN does not clear copies already saved in a visitor's browser.
- Cloudflare recommends single-file purging over Purge Everything for one-page edits.
- A private window shows what a new visitor sees, while a normal reload can show your saved copy.
- Two caching plugins on one site can serve each other's stale copies, so keep only one.
What does clearing the cache do?
Clearing the cache deletes saved copies of your pages and files, so WordPress and your server build fresh copies with your latest changes.
A cache stores a finished copy of a page, a stylesheet, or a script. When a visitor asks for that page again, the server sends the saved copy instead of building it from scratch. That makes the site faster, but it also means an old copy can hide a new edit.
Clearing the cache does not delete your content, your theme, or your settings. It only removes the saved copies. WordPress rebuilds them on the next visit, either at once or when the next visitor loads the page.
A WordPress site can hold four or five cache layers at once: the caching plugin, the host server cache, the CDN, the browser, and sometimes an object cache.
Each layer stores its own copy. Clearing one layer does not clear the others, so a change can stay hidden until you clear the layer that holds the old copy.
| Layer | What it stores | Where to clear it |
|---|---|---|
| Caching plugin | Finished HTML pages | wp-admin admin bar or plugin settings |
| Host server cache | Full pages before WordPress runs | Hosting dashboard |
| CDN | Files on edge servers near visitors | CDN dashboard |
| Browser | Styles, scripts, and images on your computer | Browser settings or hard refresh |
| Object cache | Database results in memory | Plugin or host tools |
What do you need before you start?
You need wp-admin access, your hosting dashboard login, and your CDN login if you use one.
Log in to wp-admin first, since the caching plugin controls live in the dashboard. If wp-admin will not load, skip to the host cache section, because the host panel can clear the server cache without WordPress.
Open your hosting dashboard in a second tab. Most managed hosts run their own server cache, and the plugin purge does not reach it. Keep the CDN dashboard open too if you use Cloudflare or another CDN.
Note which caching plugin your site uses before you click anything. Common choices are WP Rocket, LiteSpeed Cache, and WP Super Cache. Each one puts its purge button in a different place, and the steps below cover all three.
Plan on 5 to 15 minutes for the whole job. Each purge takes seconds. Checking the result in a private window takes the rest of the time.
How do you clear the cache plugin layer?
You clear the plugin cache from the admin bar or from the plugin settings, and the plugin layer is the first one to clear.
Start with the admin bar at the top of wp-admin. Most caching plugins add a menu there with a purge option. Click it, wait for the confirmation message, and the plugin cache is gone.
For WP Rocket, hover over the WP Rocket menu in the admin bar and choose Clear cache or Clear and preload cache.
The WP Rocket docs list both options in the top menu, and they note that WP Rocket clears the cache by itself in most common cases. You only need the manual click after changes made outside the editor, such as edits over FTP or a redirect change.
You can also clear WP Rocket from Settings > WP Rocket > Dashboard, where the Clear and preload cache button sits. If preload is on, the plugin rebuilds the cache for your main pages right after clearing, so the first visitor does not hit a slow uncached page.
For LiteSpeed Cache, go to LiteSpeed Cache > Toolbox > Purge and click Purge All - LSCache. The LiteSpeed docs state that this button purges all cache entries tied to the current WordPress install. The same page lists a separate Purge All - Opcode Cache button, which clears the opcode cache, not the page cache.
For WP Super Cache, go to Settings > WP Super Cache, open the Easy tab, and click Delete Cache under Delete Cached Pages. The Jetpack clear-cache guide gives the same steps, and it notes that WP Super Cache builds static HTML files from your site and serves those to visitors.
Clear one page instead of the whole site when only one page changed. In WP Rocket, hover over the page in Pages or Posts and click Clear this cache. In LiteSpeed Cache, use Purge this page - LSCache from the admin bar while viewing the page.
How do you clear the host server cache?
You clear the host cache from your hosting dashboard, and you need this step when the plugin purge alone does not show your change.
Managed hosts run a server cache in front of WordPress. That cache stores full pages before WordPress runs, so a plugin purge never touches it. If you cleared the plugin cache and the page still looks old, the host cache is the usual cause.
The button name changes by host. Look for Caching, Performance, Speed, or Server Cache in your host panel.
SiteGround calls its tool SuperCacher, and its own knowledge base places it under Site Tools > Speed > Caching (SiteGround: 503 error). Open the Dynamic Cache tab there and click Flush Cache to clear the stored pages for that site.
On other managed hosts, look for a Purge cache or Clear cache button in the site or environment menu, and ask support if none is shown.
Some hosts also cache at the server level with no plugin involved. Our explainer on server-level caching describes how that layer works and why it sits outside WordPress.
If your host has no cache button, ask support whether server caching is on for your plan. Some shared plans cache pages at the web server with no panel switch, and only support can purge it.
After the host purge, reload the page in a private window. A normal reload can still show your browser copy, so the private window is the honest check.
How do you clear the CDN cache?
You clear the CDN cache from the CDN dashboard, and you need this step when visitors in other places still see the old version.
A CDN stores copies of your files on edge servers near visitors. Even after you clear the plugin and host caches, an edge server can keep serving the old file until its copy expires or you purge it.
Purging the CDN does not clear copies already saved in a visitor's browser, so check the browser step too.
For Cloudflare, open the dashboard, pick your site, and go to Caching > Configuration. Under Purge Cache, click Purge Everything to clear the whole zone, or Custom Purge to clear one URL.
The Cloudflare docs state that purging everything clears all resources from the CDN cache in all Cloudflare data centers, and that the next request for each purged resource returns a CF-Cache-Status header of MISS.
Cloudflare also states on the same page that it strongly recommends single-file purging instead of a full purge. A full purge forces every page to rebuild from your origin at once, which can slow the site for a short time. Use Custom Purge with the exact URL when only one page changed.
Our guide on Cloudflare cache rules covers which files Cloudflare caches by default.
Our Cloudflare setup guide covers the first install.
If you use a different CDN, the idea is the same. Open its dashboard, find the purge or invalidate section, and purge the changed URLs first. A full purge is the last resort, not the first step.
How do you clear your browser cache?
You clear the browser cache when only you see the old version and other people see the new one.
Your browser saves stylesheets, scripts, and images on your own computer. When you reload a page, it may reuse those saved files instead of asking the server for new ones. That is why a change can look live on a phone and stale on your desktop.
Try a hard refresh first: on Windows, press Ctrl + Shift + R, and on a Mac, press Cmd + Shift + R. A hard refresh tells the browser to fetch fresh copies of the page files instead of using its saved copies.
If the hard refresh does not work, clear the browser cache by hand. In Chrome, open Settings > Privacy and security > Delete browsing data, tick Cached images and files, and click Delete data.
In Firefox, open Settings > Privacy and Security > Cookies and Site Data, and click Clear Data. In Safari, open Settings > Privacy > Manage Website Data and remove the site entry.
A private or incognito window is a faster check than a full clear. It starts with an empty cache, so it shows what a new visitor sees. Open your page in a private window after each purge step, and compare it with the normal window.
Do not ask every visitor to clear their browser cache. You cannot reach their browsers, and the old copy expires on its own when its cache headers run out. Fix the server layers first, and the browser copies catch up.
How do you check the new version is live?
You check the new version by loading the changed page in a private window and looking for the exact edit you made.
Open a private or incognito window, go to the page, and find the text, image, or layout change. If the change is there, the purge worked. If it is not there, one layer still holds the old copy, so work back through the layers in order.
Check the page headers if you want proof instead of a visual check. Open the browser developer tools, go to the Network tab, reload the page, and click the page request.
A CF-Cache-Status header of MISS after a Cloudflare purge means the edge server fetched a fresh copy from your origin. A HIT means the edge server served its saved copy.
Check a second device or a second network if you can. A phone on mobile data skips your office network cache and your desktop browser cache at once. If the phone shows the change and the desktop does not, the fault is the desktop browser cache.
Check the page source for a cache comment too. Many caching plugins add a short comment at the bottom of the HTML, such as a generation time. If the time is old, the page is still a saved copy.
What if changes still do not show?
If changes still do not show after every layer is purged, the cause is usually not the cache at all.
First, check whether you edited the right page. A staging site, a draft, or a duplicate page can look like the live page while the live page stays untouched. Confirm the URL in the address bar matches the page you edited.
Second, check for a second caching plugin. Two caching plugins on one site can fight, and one may rebuild the cache from the other. Keep one caching plugin active, and remove the other.
Third, check for minified CSS or JS that did not rebuild. A caching plugin can merge stylesheets into one file, and a purge may not rebuild that file, so in LiteSpeed Cache use Purge All - CSS/JS on the Toolbox page, and in WP Rocket use Clear Used CSS from the top menu.
Fourth, check the object cache if your site uses Redis or Memcached. A page cache purge does not flush the object cache. Our guide on page cache vs object cache explains which layer holds what, and when to flush each one.
Fifth, check for a theme or builder cache. Elementor and Divi keep their own CSS files, and a page builder cache can outlive a plugin purge. Regenerate the builder CSS from its own settings screen, then purge again.
If none of these steps helps, read our guide on fixing changes not showing on your site for the full fault order.
When only styles are stale, read our guide on fixing CSS changes not showing instead.
What mistakes should you avoid?
The most common cache mistakes waste time or slow the site for no reason.
First, do not purge everything for a one-page edit. A full purge drops the whole cache, so every page rebuilds at once and the site runs slower until the cache warms up again. Purge the one URL that changed, and save the full purge for a site-wide change.
Second, do not purge in the wrong order. Clear the layer closest to WordPress first, then work outward: plugin, host, CDN, browser. If you purge the CDN while the host cache is stale, the edge servers refill from the stale host copy.
Third, do not purge on a fixed schedule. A cache purge is a fix for a stale copy, not a daily chore. Purging every hour keeps the cache cold and throws away the speed the cache exists to give.
Fourth, do not run two caching plugins at once. Each one writes its own cache files and headers, and they can serve each other's stale copies. Pick one plugin that fits your host, and remove the other.
Fifth, do not forget the private window check. A normal reload can show your browser copy and hide a successful purge. Always confirm in a private window before you purge again.
Frequently asked questions
Does clearing the cache delete my content?
No. Clearing the cache only deletes saved copies of pages and files. WordPress rebuilds them on the next visit, and your content, theme, and settings stay untouched.
In what order should I clear cache layers?
Clear the layer closest to WordPress first: plugin, then host, then CDN, then browser. If you purge the CDN while the host cache is stale, the edge servers refill from the stale host copy.
When should I use Purge Everything in Cloudflare?
Use Purge Everything only for a site-wide change or a security fix. For a one-page edit, use Custom Purge with the exact URL, since a full purge forces every page to rebuild at once.
Why check in a private window after clearing cache?
A private window starts with an empty cache, so it shows what a new visitor sees. A normal reload can show your own browser copy instead, which hides a successful purge.
What if my changes still do not show after purging everything?
That usually means a second cache is at work: a second caching plugin, a builder CSS file, or an object cache. Purge those layers too, or check whether you edited the right page.
Sources
- Purge everything Cloudflare Docs
- Toolbox: Purge Tab LiteSpeed Docs
- When should I use the top menu options WP Rocket Docs
- How to Clear the Cache of WP Super Cache Jetpack
- 503 Error SiteGround
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.
