How To Clear Cache In WordPress (2026 Step-by-Step Guide)

For: Small business owners, freelancers, and WooCommerce store managers who made a change to their site and can’t see it reflected—or whose visitors are seeing an outdated version. No developer knowledge required.

Disclosure: Some links in this guide are affiliate links. If you buy through them, we earn a small commission at no extra cost to you. We only recommend tools we’ve tested on real client sites.

Clearing the cache in WordPress takes under 60 seconds once you know where to click. The confusion comes from having four different caches—plugin, hosting, browser, and CDN—that each need to be cleared separately. Miss one and your site still shows stale content.

Answer Capsule

WordPress cache is a saved copy of your pages that speeds up load times by skipping repeated database queries. Clearing it forces WordPress to rebuild those copies with your latest content. Most users clear it from a caching plugin dashboard (like WP Rocket) or their hosting panel, then clear their browser cache to verify the result.

Last verified: April 2026

Prerequisites Before You Start

Role required: WordPress Administrator
WordPress version: 6.4+ (steps are identical back to 6.0)
Time: 5–10 minutes
Backup: Take a full backup before clearing cache if your site is live and serving customers. Most caching plugins don’t affect content, but hosting-level cache purges occasionally surface configuration issues that were previously hidden.
What you’ll need: Access to wp-admin, and optionally your hosting control panel login.

Why Does WordPress Cache Go Stale?

Cache stores static HTML copies of your pages so the server doesn’t regenerate them on every visit. When you update a page, publish a post, change a menu, or modify a plugin, that stored copy can be out of date. WordPress doesn’t always know to rebuild it automatically—especially when changes happen outside the standard post editor, like theme customizer tweaks or plugin settings changes.

In our testing across 200+ client sites, the most common trigger for a stale cache complaint is a homepage update that the client can’t see in their own browser. That’s almost always a combination of a plugin cache that hasn’t been purged and a browser cache serving the old copy.

Method 1 (Recommended): Clear Cache With WP Rocket

WP Rocket is the caching plugin we recommend for most business sites. It costs $59/year for a single site (see current pricing on the WP Rocket site) and handles cache clearing with one click from the admin toolbar—no settings archaeology required.

Step 1: Log in to wp-admin. In the black admin toolbar at the top of your screen, look for WP Rocket. You’ll see a drop-down with two options: Clear Cache and Preload Cache.

Step 2: Click Clear Cache.

You should see a green notification bar across the top of the screen that reads: “WP Rocket: Cache cleared.” This takes roughly 2–5 seconds on an average site. Larger WooCommerce stores with 500+ products can take up to 30 seconds—this is normal.

Step 3: Reload your site’s front end in a new incognito/private browser window. Opening incognito bypasses your browser’s own cache, which means you’re seeing exactly what a new visitor sees.

What you should see: Your updated content live on the page.

Step 4 (optional): If you changed performance settings inside WP Rocket itself—like enabling or disabling minification—go to WP Rocket > Dashboard and click Preload Cache. This rebuilds the cache proactively so the first visitor after clearing doesn’t hit a slow uncached load.

WP Rocket Settings-Level Cache Clear

When we installed a new page builder template in our testing and the layout broke, a standard cache clear wasn’t enough. Go to WP Rocket > Tools > Cache, then scroll to Clear Cache and Preload. This is the nuclear option—it wipes all cached files including per-user cache, REST API cache, and feed cache. Use it after major design changes.

Method 2: Clear Cache With W3 Total Cache (Free)

W3 Total Cache is the most widely installed free caching plugin, with over 1 million active installs on WordPress.org. It’s more complex than WP Rocket but capable.

Step 1: In the admin toolbar, look for the Performance menu (W3 Total Cache adds this to the toolbar).

Step 2: Click Purge All Caches.

You should see: “Performance: Page cache flushed.” If you have object cache or database cache enabled, those will also purge.

Step 3: Go to Performance > General Settings and confirm that Page Cache shows Enabled at the top. If it shows disabled, your cache was never active—content freshness isn’t the issue and you need to diagnose elsewhere.

Gotcha: W3 Total Cache’s browser cache settings are separate from page cache. If you’ve enabled browser cache headers through W3TC and a visitor is still seeing old content, that’s their browser respecting the cache headers you set. Clearing server-side cache doesn’t fix this—they need to do a hard refresh (see Method 4 below).

Method 3: Clear Cache From Your Hosting Panel

Most managed WordPress hosts run their own server-level cache that operates independently of any plugin you install. This cache is often the fastest layer and the hardest to notice when it’s stale. Even if you clear your plugin cache, the host cache can still serve old content to visitors.

SiteGround (Site Tools)

SiteGround’s caching tool is called SuperCacher. After logging in to your SiteGround client area:

Go to Site Tools > Speed > Caching.
Click the Dynamic Cache tab.
Click Flush Cache (the icon that looks like a refresh arrow next to your domain).

You should see: a confirmation toast that reads “Cache flushed successfully.”

SiteGround also offers Memcached and Static Cache tabs in the same panel. Flush all three if you’ve made structural changes like updating permalink settings.

Kinsta (MyKinsta)

Kinsta charges a premium ($35/month minimum) but their server cache is one of the fastest we’ve measured—under 20ms TTFB on cached pages in our Kinsta benchmarks.

Log in to MyKinsta.
Click on your site, then go to Tools.
Find Clear Cache and click the Clear Cache button.

Kinsta also gives you a Force HTTPS toggle in the same Tools panel—confirm it’s enabled if your site recently moved to SSL.

WP Engine (User Portal)

WP Engine’s hosting infrastructure purges cache differently—per environment (production, staging, development).

Log in to the WP Engine User Portal.
Click on your environment name.
Under Utilities, click Purge All Caches.

Expect a 5–10 second delay. WP Engine confirms with: “All caches have been successfully purged.”

Original insight: WP Engine’s cache is tied to the wpe-auth cookie. If you’re logged in as admin and testing your own site, you’re bypassed from the cache by default—meaning you’re always seeing the live version regardless. To test what a real visitor sees, open a private browser window or use a tool like GTmetrix to load the page from an external server.

Cloudways

Log in to your Cloudways account.
Go to Applications and click on your app.
Under Application Management, click Clear Varnish Cache (Varnish is Cloudways’s default server cache layer).

Method 4: Clear Your Browser Cache

Browser cache stores CSS, JavaScript, and images locally on a visitor’s computer. Even after clearing every server-side cache, a visitor’s browser can still show them the old version because it’s loading files from their own hard drive.

For yourself during testing, use a hard refresh:

Windows/Linux (Chrome, Firefox, Edge): Ctrl + Shift + R or Ctrl + F5
Mac (Chrome, Firefox): Cmd + Shift + R
Mac (Safari): Cmd + Option + R

For a full browser cache wipe in Chrome:

Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
Set Time range to All time.
Check Cached images and files.
Click Clear data.

You should see: the dialog closes and Chrome reloads with a clean cache.

You cannot force a visitor to clear their browser cache. What you can do is set aggressive cache-busting headers on assets that change frequently. WP Rocket handles this automatically via its Browser Cache module in Settings > Browser.

Method 5: Clear Cloudflare CDN Cache

If your site uses Cloudflare (free or paid plan), Cloudflare caches assets at the edge—meaning in data centers around the world. Clearing your WordPress cache doesn’t touch Cloudflare.

Log in to your Cloudflare dashboard.
Select your domain.
Go to Caching > Configuration.
Click Purge Cache and then Purge Everything.

Cloudflare warns: “Purging everything removes all cached files and may slow site performance temporarily while caches rebuild.” On a small site, this takes under a minute. On a large WooCommerce store with hundreds of product images, expect up to 10 minutes before all edge caches are fully rebuilt.

Faster option: If you only updated one page, use Custom Purge and enter that page’s URL. This purges just that URL’s edge cache without affecting the rest of the site.

Troubleshooting: Why Is the Cache Still Showing Old Content?

You cleared the plugin cache but changes still aren’t visible

You have multiple cache layers active. Work through this order: plugin cache → hosting cache → Cloudflare (if used) → browser hard refresh. Missing any layer means the old version survives somewhere in the chain.

WP Rocket shows “Cache cleared” but the old page loads in incognito

Your hosting panel cache is still warm. In our testing, SiteGround’s SuperCacher is the most common culprit—it runs independently of WordPress plugins and has a 12-hour default TTL. Go to your hosting panel and flush it manually.

After clearing cache, site loads slower for a few minutes

This is expected. Cache is empty after a purge, so the server has to regenerate pages on first visit. If you use WP Rocket, run Preload Cache immediately after clearing—this crawls your site and rebuilds the cache proactively so visitors don’t hit the slow cold-load state.

Clearing cache broke my site layout

CSS or JavaScript minification files are cached separately. If clearing cache reveals a broken layout, go to WP Rocket > Dashboard and disable Minify CSS and Minify JS temporarily. Reload the site. If it fixes the layout, re-enable them one at a time to identify which file is causing the conflict.

My client says they still see the old site

Clients almost always have browser cache serving the old version. Send them this instruction: open a new incognito/private window (not just a new tab) and paste your URL. If they see the new version there, the issue is their personal browser cache—not your server.

Full Cache-Clearing Order of Operations

When you need to be certain every cache layer is clean, follow this sequence:

Step	What to Clear	Where
1	Plugin cache	WP Rocket or W3TC in wp-admin toolbar
2	Hosting cache	SiteGround SuperCacher / Kinsta Tools / WP Engine Utilities
3	CDN cache	Cloudflare > Caching > Purge Everything
4	Browser cache	Hard refresh (`Ctrl+Shift+R`) or incognito window
5	Object cache (if active)	WP Rocket > Tools > Object Cache

Skip step 5 unless you have Redis or Memcached configured—most shared hosting plans don’t include it.

FAQ

How often should I clear my WordPress cache? Only when you need to—after updating content, changing settings, or updating plugins. Good caching plugins like WP Rocket clear the relevant cache automatically when you publish or update a post. Manual clearing is for changes that happen outside the normal post-publishing flow.

Does clearing cache delete my content or settings? No. Cache contains temporary copies of your pages, not your actual content. Clearing it is safe and reversible—WordPress rebuilds the cache on the next page load.

What is the difference between page cache and browser cache? Page cache lives on your server and stores HTML copies of your WordPress pages. Browser cache lives on a visitor’s device and stores images, CSS, and JavaScript files. Both need to be cleared independently; clearing one does not clear the other.

Can I clear cache without a plugin? Yes, via your hosting panel. SiteGround, Kinsta, WP Engine, and Cloudways all offer cache flush tools in their dashboards that work even if you have no caching plugin installed. The plugin gives you a faster in-admin button, but it’s not required.

Will clearing cache slow my site down? Temporarily, yes. The first visitor after a purge triggers a fresh page build, which takes longer than serving a cached copy. On WP Rocket, run Preload Cache immediately after clearing to rebuild the cache before real visitors arrive.

Why does my WordPress cache keep filling up? Cache stores copies of every unique URL, including search result pages, pagination, and filtered product pages on WooCommerce. A store with 1,000 products and active faceted filtering can generate tens of thousands of cached pages. WP Rocket’s Cache Lifespan setting (under Settings > Cache) lets you auto-expire cache on a schedule rather than letting it grow indefinitely.

Does clearing cache affect my Google rankings? No. Google caches its own indexed version of your pages; that’s separate from your server cache. Clearing your WordPress cache does not trigger a recrawl or change how Google has indexed your content.

What to Do Next

Once your cache is cleared and your site is showing the latest version, the next step depends on why you were clearing it:

After a speed optimization change: Run a fresh PageSpeed Insights test to confirm your Core Web Vitals scores reflect the new configuration.
After a design update: Check your site on mobile as well as desktop—responsive breakpoints sometimes behave differently when CSS cache rebuilds.
If you’re still having performance issues after clearing cache: The bottleneck is likely not cache at all. Read our guide on WordPress speed optimization to diagnose TTFB, LCP, and render-blocking resources.
If you don’t have a caching plugin yet: WP Rocket at $59/year is the option we recommend for non-technical site owners managing business or client sites. It automates most of what this guide covers manually.