Speed & performance · Guide
How to Clear W3 Total Cache (Step by Step)

Short answer
Log in, hover over Performance in the admin bar and click Purge All Caches. To clear one page, open it and choose the purge current page option. You can also empty a single cache type from its settings page or run wp w3-total-cache flush all over SSH.
Key takeaways
- Purge All Caches in the admin bar clears every layer.
- You can purge a single page while viewing it.
- Each cache type has its own empty cache button.
- WP-CLI users can run wp w3-total-cache flush all.
- Purge Cloudflare and host caches separately.
How do you clear W3 Total Cache?
Hover over Performance in the WordPress admin bar and click Purge All Caches, which empties the page, minify, database and object caches in one go.
That one click solves most cases where changes do not show up. W3 Total Cache also lets you clear a single page, a single cache type, or everything from the command line.
This guide covers each method, when to use it, and the other cache layers you may need to clear after W3 Total Cache.
If you are new to the plugin, our explainer on what W3 Total Cache is covers how its different caches fit together.
Why would you need to clear W3 Total Cache?
You clear the cache when visitors still see an old version of a page after you edit content, change the theme, update CSS or JavaScript, or install a plugin.
W3 Total Cache saves ready-made copies of your pages and files. That makes the site faster, but the saved copy can go stale.
The plugin clears the cache for a post automatically when you update it. It does not always know about changes elsewhere, such as:
- Edits to widgets, menus or the Customizer.
- Changes to theme files or custom CSS.
- Updates to plugins that change the page layout.
- Changes in a page builder that do not trigger a normal post update.
- Moving to a new domain or switching to HTTPS.
In those cases, a manual purge makes sure everyone sees the new version.
How do you purge all caches from the admin bar?
While logged in, hover over the Performance menu in the top admin bar and click Purge All Caches to clear every W3 Total Cache layer at once.
Follow these steps:
- Log in to WordPress.
- Look at the black admin bar at the top of the screen.
- Hover over Performance.
- Click Purge All Caches.
- Wait for the confirmation notice.
This works from both the dashboard and the front of the site. It is the fastest option and the one you will use most.
Older versions of the plugin label this option Empty All Caches. The result is the same.
How do you clear the cache for just one page?
Visit the page on the front end while logged in, hover over Performance in the admin bar, and choose the option to purge the current page.
Purging one page is useful on large sites, where clearing everything means the server has to rebuild thousands of pages.
The current page option clears that page's cached copy only. The next visitor gets a freshly built version, which is then cached again.
If the page uses a shared minified CSS or JavaScript file you just changed, clearing one page is not enough. Purge the minify cache or use Purge All Caches instead.
How do you clear a specific cache type?
Open the settings page for that cache under Performance, such as Page Cache, Minify, Database Cache or Object Cache, and use the empty cache button at the top of the page.
W3 Total Cache keeps separate caches for different jobs. Clearing just one is handy when you know where the problem is.
| Cache type | What it stores | Clear it when |
|---|---|---|
| Page cache | Full HTML pages | Content or layout changes do not show |
| Minify | Combined, compressed CSS and JS | Style or script changes do not show |
| Database cache | Results of database queries | Data looks outdated after imports |
| Object cache | Stored PHP objects | Settings or options seem stuck |
| Browser cache | Rules for visitors' browsers | You changed static files and need a new version |
The Dashboard page under Performance also has a button to empty all caches, which matches the admin bar option.
To learn which of these caches you should even have turned on, see our guide to W3 Total Cache recommended settings.
How do you clear browser caches for visitors?
You cannot clear a visitor's browser cache from the server, but W3 Total Cache can change the version string on your static files so browsers download fresh copies.
Browser caching tells visitors' browsers to keep CSS, JavaScript and images for a set time. That is set with headers like Cache-Control, which MDN explains in its guide to HTTP caching.
When you change a file, returning visitors may keep the old copy. W3 Total Cache can update the media query string it adds to file URLs. Browsers treat the new URL as a new file and download it.
Look for the option to update the media query string on the Performance Dashboard or Browser Cache settings. Then purge all caches.
How do you clear W3 Total Cache with WP-CLI?
Run wp w3-total-cache flush all from your site's folder over SSH to clear every cache without opening the dashboard.
W3 Total Cache adds its own commands to WP-CLI. They are useful for scripts, deployments or when the dashboard will not load.
# Clear every W3 Total Cache layer
wp w3-total-cache flush all
# Clear the cache for one post by ID
wp w3-total-cache flush post --post_id=123
Run wp help w3-total-cache to see every subcommand your version supports.
The general wp cache flush command only clears the WordPress object cache. It does not empty W3 Total Cache's page or minify caches, so use the plugin's own command.
How do you clear the cache if you cannot reach the dashboard?
Delete the contents of the cache folders inside wp-content using FTP or your host's file manager, which removes the stored files W3 Total Cache serves.
This is a last resort for when the dashboard is down or stuck in a redirect loop.
- Connect with FTP, SFTP or your host's file manager.
- Open wp-content/cache.
- Delete the contents of the page cache and minify folders, not the cache folder itself.
- Reload the site in a private window.
Do not delete the plugin's config files in wp-content/w3tc-config. Those hold your settings.
If the plugin itself is causing the outage, rename its folder in wp-content/plugins to disable it. WordPress's guide to managing plugins covers plugin folders.
What other caches should you clear?
After W3 Total Cache, also purge any CDN, host-level cache or Cloudflare cache, because those layers keep their own copies of your pages and files.
Many sites have more than one cache layer. Clearing W3 Total Cache does not touch the others unless you link them.
- Cloudflare. Purge from the Cloudflare dashboard. Cloudflare's guide to purging cache shows single-file and full purges.
- Host caching. Managed hosts often run Varnish or Nginx caching with their own purge button.
- CDN in W3 Total Cache. If you set up a CDN under Performance, use its purge option there.
- Your own browser. Use a private window to see what visitors get.
Our general guide on how to clear cache in WordPress covers hosts and plugins beyond W3 Total Cache.
Why do changes still not show after clearing the cache?
If clearing every cache does not help, the change may not have saved, a different cache layer is still serving old files, or you are viewing a cached copy in your own browser.
Work through these checks:
- Open the page in a private window.
- Confirm the change saved by viewing it in the editor.
- Purge your CDN and host cache, not just W3 Total Cache.
- Check that you are editing the right site, not a staging copy.
- Turn off minify briefly to rule it out.
If CSS changes are the issue, our guide on fixing CSS changes not showing goes deeper.
For changes of every kind, see fixing changes not showing on your site.
How do you set W3 Total Cache to clear itself automatically?
Use the purge policy in the Page Cache settings to choose which pages are cleared when you publish or update a post, such as the home page, feeds and archives.
By default, updating a post clears that post's cached page. You can also tell W3 Total Cache to purge the front page, the posts page, category and tag archives, and feeds.
Turning on more purge targets keeps the site fresher but means more pages need to be rebuilt after each update. On busy news sites, purge the home page and archives. On static business sites, the default is usually fine.
Frequently asked questions
Where is the clear cache button in W3 Total Cache?
It is in the Performance menu in the WordPress admin bar at the top of the screen. Hover over Performance and click the purge all caches option. The Performance Dashboard page in the admin menu has a matching button.
Does clearing W3 Total Cache slow down my site?
Only briefly. After a purge, the first visit to each page builds a fresh copy, which is a little slower. Later visitors get the new cached copy at full speed, so the effect passes quickly.
Will clearing the cache delete my W3 Total Cache settings?
No. Purging only removes stored copies of pages, files and queries. Your settings are kept in separate configuration files and stay the same. Just avoid deleting the config folder if you clear files by FTP.
How often should I clear W3 Total Cache?
Only when you need to. The plugin clears updated posts automatically, so you only purge manually after theme, widget, menu, CSS or plugin changes, or when visitors report seeing an old version of a page.
Does W3 Total Cache clear Cloudflare automatically?
Not by default. Cloudflare keeps its own cache, so purge it from the Cloudflare dashboard or connect the two using an integration. Otherwise visitors may keep getting old files from Cloudflare after you clear W3 Total Cache.
Sources
- W3 Total Cache WordPress.org
- WP-CLI WP-CLI
- wp cache flush WordPress Developer Resources
- HTTP caching MDN Web Docs
- Purge cache Cloudflare Docs
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.


