How to do a Hard Refresh in Any Browser

A hard refresh forces your browser to bypass its cache and reload a page from the server — useful when you have published changes to a site and the browser keeps serving the old version.

A standard refresh (clicking the reload arrow or pressing F5 on its own) only re-renders what is already in the cache. To actually pull fresh files, you need a hard refresh — also called a “cache-bypass reload.”

Hard refresh keyboard shortcuts by browser

Use the shortcut that matches your browser and operating system. Every shortcut below tells the browser to ignore the cached copy of the current page and fetch a new one from the server.

Google Chrome

• Windows: Hold Ctrl and press F5. You can also use Ctrl + Shift + R.
• Mac: Hold Cmd + Shift and press R.

Firefox

• Windows: Hold Ctrl and press F5, or use Ctrl + Shift + R.
• Mac: Hold Cmd + Shift and press R.

Safari (Mac)

Safari does not have a single hard-refresh shortcut. Use this two-step pattern:

1. Empty the cache: Safari menu → Empty Cache, or press Option + Cmd + E.
2. Reload the page: press Cmd + R.

If you do not see the Empty Cache option, enable the Develop menu first: Safari → Settings → Advanced → Show Develop menu in menu bar. The Develop menu also includes a one-click Empty Caches option.

Microsoft Edge and Internet Explorer (Windows)

• Hold Ctrl and press F5, or use Ctrl + Shift + R.

Opera

• Windows: Ctrl + F5 or Ctrl + Shift + R.
• Mac: Cmd + Shift + R.

What a hard refresh actually does

When you load a page, the browser stores files — HTML, CSS, JavaScript, images — in its local cache so the page loads faster next time. A standard refresh reuses those cached files. A hard refresh tells the browser to discard the cached copies of the current page and request fresh ones from the server.

This is different from clearing your entire browser cache, which removes stored files for every site you have visited. A hard refresh only affects the page currently open in the tab.

When you actually need a hard refresh

A hard refresh fixes problems caused by stale cache. Reach for it when:

• You updated your WordPress theme, CSS, or JavaScript and the change is not showing up.
• You deployed a new build and old assets are still loading.
• A page is rendering broken styles or a layout you have already fixed.
• An image was replaced at the same URL and the old image keeps loading.
• A logged-in dashboard or admin screen is behaving inconsistently after a release.

A hard refresh will not help with server-side issues, CDN edge caching, or service-worker caching — those need to be cleared separately.

If a hard refresh does not fix it

When the page still looks wrong after a hard refresh, the cached file is almost certainly being served from somewhere upstream. Work through these in order:

1. Open the same URL in a private or incognito window. If it looks correct there, the issue is local cache or a browser extension.
2. Clear the browser cache fully — not just the page — and reload.
3. If you use a caching plugin (WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache), purge the plugin cache from the WordPress admin.
4. If your site sits behind Cloudflare or another CDN, purge the CDN cache for the specific URL.
5. Check whether a service worker is intercepting requests. In Chrome DevTools, go to Application → Service Workers and click Unregister, then reload.

After every change, do another hard refresh to confirm.

Quick reference

Bookmark the shortcut for the browser you use most. Once you make a hard refresh part of your release checklist, you stop wasting time chasing bugs that were never real bugs — just a cached file.