You make edits to a theme, change text on a page, update a plugin, and the site looks like nothing happened. Sound familiar? Almost certainly you've run into WordPress cache. And no, this isn't a bug and there's no need to restart the server.

Cache is a useful thing. It speeds up page loading several times over, saves hosting resources, and improves behavioral metrics. But only until it starts showing an outdated version of the site to you and your visitors. Then cache turns from a helper into a problem.

Good news: clearing WordPress cache takes seconds. No console, no developer, no magic incantations. In this guide, all four types of cache that exist on any WordPress site, plus step-by-step instructions for clearing each one. From browser to CDN.

💡 Quick overview:

• Open your browser, press Ctrl+Shift+Del, and you're already halfway to clearing browser cache
• In the WordPress admin, click one button in the caching plugin, and it clears the plugin cache in a second
• If your site is on managed hosting (WP Engine, Flywheel, Cloudways), the hosting panel has a native server cache reset button
• For sites behind Cloudflare or Sucuri, clearing is done through the CDN provider's dashboard, also in one click

What is WordPress cache

Cache is temporary data storage. Instead of building a page from scratch on every request (PHP + database + theme files), the server or browser delivers an already prepared, saved copy. The result: the page loads not in 2 seconds, but in 0.4.

An everyday analogy: you moved the TV remote from the closet to the couch. Next time you don't need to get up and walk across the room, the remote is already at hand. Cache works the same way: "hot" data is stored nearby, access to it is instant.

In the WordPress ecosystem, caching happens at several levels simultaneously. And to understand which specific cache is preventing you from seeing the fresh version of the site, you need to know these levels by sight.

4 types of cache on a WordPress site

Every WordPress site, regardless of hosting and plugin setup, passes through four caching layers. Let's break down each one.

Browser cache

Any modern browser (Chrome, Firefox, Edge, Safari) automatically saves static content from visited sites to your computer: images, CSS files, JavaScript, fonts, and even entire HTML pages. When revisiting a site, the browser doesn't download these files again but retrieves them from local storage.

For the site owner this is a plus: regular visitors see pages faster, server load decreases. The downside appears when you've updated your logo, recolored buttons, or changed fonts, but your browser continues showing old versions of files. The solution: manual browser cache clearing (instructions below).

Plugin cache

Caching plugins are the main tool for speeding up WordPress. They create static HTML copies of dynamic pages and serve them to visitors, bypassing the heavy PHP+MySQL cycle. The two most popular free solutions are W3 Total Cache on WordPress.org (1M+ active installations) and WP Super Cache from Automattic (1M+ active installations, developed by Automattic).

A plugin can cache pages, compressed CSS/JS, database queries, objects, and even integrate with CDN. But if visitors see the old version after publishing a new post or editing the design, the culprit is almost certainly the plugin cache. The "Delete Cache" button in the admin solves the problem instantly.

Server cache

Most managed WordPress hosts build server caching directly into their architecture. WP Engine adds a clear button right to the WordPress admin. Flywheel places it in the top bar. Pagely uses its own PressArmor panel with a Purge All option.

Some hosts go further and use a reverse proxy: several cache servers stand "in front" of the main one and handle repeated requests. Server cache is cleared through the hosting panel or by contacting support; there's no universal button here, each host implements it differently.

Third-party cache (CDN)

If the site is routed through a CDN provider (Cloudflare or Sucuri), another cache layer appears, distributed across dozens of data centers worldwide. The CDN stores copies of static files and even entire HTML pages geographically close to each visitor.

Interesting fact: a properly configured CDN can serve a site's static content even if the origin server itself is temporarily unavailable. Visitors won't notice, pages continue opening from cache. But the price of such convenience is the need to purge the CDN cache with every significant site update. Otherwise, visitors from different regions will see different versions of pages.

Why clear WordPress cache at all

Cache handles its job excellently almost always. But there are three specific situations when you need to clear it immediately:

You updated content but don't see the changes. Rewrote a headline, replaced text on the homepage, added a new block, press "Update" in the admin, but the site shows the old version. This is the plugin or server cache holding onto the old copy.

Design broke after edits. Changed CSS, updated the theme, installed a new plugin, and the layout fell apart. Often the problem isn't in the code but in the browser continuing to load old styles and scripts. Clearing browser cache + purging plugin cache together solves most such cases.

Visitors see outdated content. Improperly configured cache can show an old page version for weeks to users who've already visited the site. CDN cache is especially sneaky: a visitor from Berlin sees one thing, while someone from Tokyo sees another. Purging all cache layers synchronizes the output.

How to clear browser cache

Browser cache is the simplest to clear and the most common reason why site owners don't see their own edits. Let's cover three main browsers.

Google Chrome

Chrome caches aggressively; this is one reason for its speed. But clearing takes just three clicks.

Click the three-dot icon in the upper right corner, go to More tools and select Clear browsing data. The keyboard shortcut Ctrl+Shift+Del does the same thing.

In the window that opens, select the time range (I recommend "All time" for complete clearing), check Cached images and files and click Clear data.

Done. Reload the site page using Ctrl+F5 (hard refresh without cache), and you'll see the current version.

Mozilla Firefox

Firefox matches Chrome in cache clearing convenience. Click the menu icon (three lines), then the History tab.

In the dropdown panel, select Clear Recent History.

In the window that appears, set the time range to "Everything," check Cache and click Clear Now.

Microsoft Edge

Edge is built on the same Chromium engine as Chrome, so the clearing logic is similar. Click the menu icon (three dots) and select Settings.

In the left settings menu, go to Privacy, search, and services and click the Choose what to clear button.

Check Cached images and files and click Clear now.

A useful Edge feature that Chrome lacks: you can enable automatic cache clearing every time the browser closes. Found in the same privacy settings section.

After clearing browser cache, open the site using Ctrl+F5. If the problem persists, move on to plugin cache.

How to clear plugin cache

The clearing method depends on the specific plugin, but almost always it comes down to pressing one button in the WordPress admin.

W3 Total Cache

W3 Total Cache in the repository is the most feature-rich free plugin for WordPress caching. It caches pages, objects, database queries, compresses CSS and JS, and integrates with CDN. Used on sites like AT&T and MakeUseOf.

To clear the cache, go to the WordPress admin and navigate to Performance → Dashboard. Click the empty all caches button, and the plugin will purge every cache layer in one operation.

WP Super Cache

WP Super Cache on WordPress.org is developed by Automattic, the company behind WordPress.com, Jetpack, Akismet, and WooCommerce. The plugin generates static HTML files from dynamic content and serves them instead of the heavy PHP cycle.

Clearing is straightforward: in the WordPress admin, go to Settings → WP Super Cache and click the Delete Cache button.

Both plugins also add a quick clear button to the WordPress admin bar, letting you purge cache in one click from any admin section.

How to clear server and third-party cache

For server cache, there's no universal instruction; each hosting provider implements the mechanism differently. The general principle: on managed WordPress hosts (WP Engine, Flywheel, Cloudways, Kinsta), the cache reset button is built into the hosting control panel or directly into the WordPress admin. On shared hosting (SiteGround, Bluehost), the caching function may be in the "Site Optimization" section of cPanel.

To clear Cloudflare cache, log into your account, select the site, and go to Caching → Purge Cache. The Purge Everything button clears all CDN cache for the domain. Sucuri has a similar path: Performance → Clear Cache. Both operations take 30 seconds to 2 minutes while the CDN sends the purge command to all data centers.

If the site uses both server cache and CDN, order matters: first clear the server cache, then the CDN cache. This ensures the CDN caches the fresh version from the server, not an old copy.

A short video on the topic: breakdown of all types of WordPress caching including Redis Object Cache and Full Page Cache, with a demonstration of clearing each layer.

⁉️🤔 Frequently asked questions

Why don't I see changes on the site after editing?

Most likely, you're looking at a cached version. Press Ctrl+Shift+Del in your browser, clear the plugin cache in the WordPress admin, then open the site using Ctrl+F5. If that doesn't help, clear the server cache through the hosting panel. Order of actions: browser cache → plugin cache → server cache → CDN. Go through the chain from simple to complex; in most cases the problem is solved at the first or second step.

Which caching plugin is better: W3 Total Cache or WP Super Cache?

W3 Total Cache has more features: caches pages, objects, database queries, minifies and compresses resources. WP Super Cache is easier to configure and developed by Automattic, the team behind WordPress itself. Choose W3TC if you're willing to spend 10 minutes on fine-tuning, WP Super Cache if you need "set it and forget it." Both are free and have over a million active installations each. For a typical blog or company website, the speed difference between them will be within 0.1-0.2 seconds.

Should I clear cache after updating WordPress plugins?

Yes, and this is mandatory. Updating a plugin or theme changes CSS and JavaScript files that the browser and caching plugin may have saved in the old version. After any plugin, theme, or WordPress core update, purge the plugin cache and clear browser cache; this prevents style and script conflicts. Especially critical after major updates (major WordPress versions, switching to new PHP): spend 15 seconds clearing cache now, save half an hour searching for "broken" layout later.

How often should I clear WordPress cache?

Only when truly necessary: after updating content, design edits, installing or updating plugins and themes. The rest of the time, let cache do its job; that's what it's for. There's no point clearing cache "preventively" every day. Exception: if the site is very dynamic (forum, online store with frequent price and inventory updates), set a shorter cache time-to-live (TTL), for example 2-4 hours instead of the standard 24. This way visitors will see current data without manual clearing.

Can I automate cache clearing?

Yes, most caching plugins support automatic clearing on events: publishing a new post, updating a page, changing themes. W3 Total Cache and WP Super Cache do this out of the box. For server cache and CDN, API calls via WP-CLI or HTTP requests to the provider's API work well. But full automation is a double-edged sword. Clearing too frequently reduces cache benefit to zero: the server builds pages from scratch each time. Set up auto-clearing only for truly significant events (new post, changes to critical pages).

Clearing WordPress cache: what and when to click

The universal algorithm for any situation looks like this:

• Don't see your edits? Ctrl+Shift+Del in the browser + Delete Cache button in the plugin.
• Visitors complain about old design? Clear plugin cache, then server cache, then CDN (if applicable).
• After updating theme or plugins everything broke? Browser + plugin cache, and reload using Ctrl+F5.

In most cases, the problem is solved by clearing browser and plugin cache. Server and CDN cache are needed less often, but when they're needed, you can't do without them. Now you have step-by-step instructions for each layer. Bookmark this page; it will come in handy.