How to Clear Cache on WordPress Without Breaking Your Site

WordPress caching stores copies of pages, styles, scripts, or database results so a site can load faster. After you change a page or design, an old cached copy may still appear. Clearing the relevant cache asks WordPress and related services to build or fetch a fresh copy.

Before you begin, save your work and make sure you can sign in to the WordPress dashboard. You usually do not need to clear every cache layer; start with the one most likely to be serving the outdated content. Menu names vary by plugin, host, and version, so use the equivalent cache or purge command if the labels differ.

What You’ll Need

Access to your WordPress dashboard, hosting control panel, or both.
The name of your caching plugin, if one is installed.
Access to your CDN dashboard if your site uses a content delivery network.
A browser in which to check the updated page.

Step-by-Step

Confirm what changed. Open the page in the WordPress editor and confirm that the update is saved or published. Note the exact page and what looks outdated, such as text, an image, layout, or styling. This helps you distinguish a cache issue from an edit that did not save.
Check for a caching plugin. In the dashboard, open Plugins and look for a caching or performance plugin. Common examples include plugins that offer page caching, optimization, or site performance controls. Do not install a second cache plugin just to find a purge button; overlapping cache tools can make diagnosis harder.
Purge the plugin cache. Look for a command such as “Clear Cache,” “Purge Cache,” or “Delete Cache” in the plugin’s settings, its dashboard menu, or the WordPress admin toolbar. The location and wording vary by plugin version. Use the command to clear cached pages, not a setting that disables the plugin or changes optimization features.
Check your hosting cache. Some web hosts cache pages outside WordPress. Sign in to the hosting dashboard and look for site tools labeled caching, performance, or cache management. Select the purge or clear option for the affected site. If you cannot find it, consult the host’s help documentation or support rather than changing server settings you do not recognize.
Purge the CDN cache, if used. If your site uses a CDN or reverse-proxy service, sign in to its dashboard and purge the relevant URL or the full cache, depending on what the service offers. A URL-level purge is often enough for one changed page; a full purge may cause more uncached requests while content is rebuilt. Follow the service’s own instructions.
Refresh the browser view. Open the changed page in a private or incognito window. This avoids many local browser-cache effects and gives you a useful comparison. If the private view is current but your usual window is not, clear that browser’s cached images and files, then reload the page. Browser menus vary by version.
Verify the result. Check the updated page and a few important site functions, such as navigation, forms, and images. If one page remains stale, clear the cache for that URL where possible and check whether a page builder or separate optimization tool has its own cache. Avoid repeatedly purging every layer without checking between steps.

Common Mistakes

Clearing only the browser cache: This affects the files stored in your browser, not a stale page being served by a WordPress plugin, host, or CDN.
Assuming WordPress has one universal cache button: WordPress does not provide a single built-in control that clears every cache. The right control depends on your setup.
Disabling or deleting the caching plugin: That is usually unnecessary and may change performance settings. Use its purge command instead.
Purging everything repeatedly: This can make the site temporarily slower as cached content is rebuilt and may not address the actual cause. Work from the page cache outward.
Forgetting saved changes: Clearing a cache cannot publish an unsaved draft or fix a change made to the wrong page, theme, or device preview.

Tips

Keep a note of which cache layers your site uses: plugin, host, CDN, and browser. Not every site has all four.
After changing a theme, plugin, or page-builder design, check for a separate option to regenerate files or clear generated assets. Use the tool’s documentation because the command and purpose vary.
When only one URL is affected, start with a URL-specific purge instead of clearing the entire site or CDN.
If you manage a live business site, make changes during a quiet period when practical, and check key pages soon after purging.
Do not change caching or minification settings just to force a refresh. Those settings can affect how scripts and styles load.

Troubleshooting

The old content still appears: Confirm the edit is published, then check each cache layer in order: plugin, host, CDN, and browser. If your CDN offers a page-specific purge, use the exact page URL. Wait briefly for the purge to complete before checking again.

The page is current in a private window only: Clear cached images and files in your regular browser, then reload. If the issue persists across browsers, the cause is more likely a site or CDN cache than a local browser copy.

Some styles or images look wrong after purging: Check whether an optimization or page-builder tool generates separate CSS or script files. Use its documented regeneration or cache-clear option, then reload. If the problem began after changing settings, restore the previous settings rather than disabling multiple tools at once.

You cannot find a cache control: Check the plugin’s settings and admin toolbar, then the host’s dashboard. A developer or hosting provider may manage caching outside your account. Ask them which cache layer is active and how to purge it safely.

The site becomes slow after clearing: Cached files may need to be rebuilt as pages are requested. Avoid repeated full purges. If the slowdown continues or pages fail to load, contact your host or the plugin’s support team and share the affected URLs and what you cleared.

Frequently Asked Questions

Does clearing cache delete WordPress content?

No. Clearing a cache removes temporary stored copies, not published posts, pages, or media. Still, save your edits before using any cache controls.

How often should I clear the WordPress cache?

Clear it when you need to see a change that is not appearing or when a cache tool’s documentation recommends it. Routine purging is not usually necessary if the site is displaying correctly.

Should I clear all caches at once?

Usually not. Start with the cache most likely to be responsible, then check the page before moving to the next layer. This makes it easier to identify the cause and avoids unnecessary full purges.

Will clearing cache log visitors out or remove comments?

A standard page-cache purge does not delete comments or user accounts. Some sites handle logged-in pages differently, so check your plugin or host documentation if you are unsure what a particular control does.

Why can I see the update but other people cannot?

Your browser may be showing a fresh copy while a host or CDN still serves an older one to other visitors. Purge those layers and ask someone using a separate browser or network to check the page.

Further reading: WordPress.org. Details can change, so check the official page for anything that matters to you. Spotted a mistake? Tell us. How we write an answer.