How to Hard Refresh Chrome: Shortcuts, Empty Cache and Hard Reload, and When Neither Works

To hard refresh Chrome, press Ctrl+Shift+R on Windows or Command+Shift+R on a Mac. Chrome reloads the page and asks the server for fresh copies of its files instead of using the ones it saved last time.

That fixes most "I can't see the change" moments. When it does not, the stale copy is usually somewhere a hard refresh cannot reach. This guide covers every shortcut, the hidden Empty Cache and Hard Reload menu, and what to do when a site still shows its old version.

The short answer#

• Shortcuts: Ctrl+Shift+R or Ctrl+F5 on Windows and Linux, Command+Shift+R on Mac, or Shift-click the reload button.
• Stronger: open DevTools, then right-click the reload button and choose Empty Cache and Hard Reload.
• Still old? A service worker is probably serving the page. Clear that site's data.
• Phones have no shortcut. Delete cached files for the last hour, then reload.

Normal reload vs hard refresh#

A normal reload (F5, or Command+R) lets Chrome reuse files it already has if the site says they are still fresh. That is why pages reload quickly.

A hard refresh tells Chrome to ignore those saved copies for this one load and fetch everything again. Nothing is deleted. The next normal reload may use the cache again.

That difference matters. A hard refresh is safe to use any time: it never signs you out and never deletes anything.

Hard refresh Chrome shortcuts for every system#

On a laptop where F5 needs the Fn key, Ctrl+Shift+R is easier to remember.

Empty Cache and Hard Reload: the hidden menu#

Chrome has a stronger reload that most people never see.

1. Press F12, or Command+Option+I on a Mac, to open DevTools.
2. Right-click, or click and hold, the reload button next to the address bar.
3. Choose Empty Cache and Hard Reload.

The menu has three options: Normal Reload, Hard Reload and Empty Cache and Hard Reload. The third one deletes cached files before reloading, so nothing stale can sneak back in from the cache on that load.

If you right-click the reload button and see no menu, DevTools is closed. That is the whole reason it "isn't showing".

Why a hard refresh sometimes does nothing#

You press Ctrl+Shift+R. Your teammate sees the new version. You still see the old one. Here are the usual reasons, in order of how often we run into them:

1. A service worker is serving the page. Many web apps install a service worker that answers requests before they reach the network. A hard refresh bypasses it for that load in Chrome, but the old worker can still be active and serve the old app on your next visit. Clearing the site's data removes the worker. Our guide to Chrome showing an old version of a website covers this in depth.

2. The cache is somewhere else. A CDN, a proxy at work, or the site's own server cache can hold the old file. Your browser gets the old version even when it asks for a fresh one. Try the page on your phone using mobile data. If it is still old there, the problem is upstream.

3. The change has not shipped. It happens. Check the deploy before you blame the browser.

4. Local or session storage holds old data. Some apps keep settings or content in local storage, which no reload clears.

When to go past a hard refresh#

If two hard refreshes do not help, clear that one site's data:

• DevTools: Application panel, then Storage, then Clear site data. Untick Cookies if you want to stay signed in. Our DevTools clear site data guide explains each box.
• Address bar: the View site information icon, then Cookies and site data, then Manage on-device site data. This also clears cookies.
• One click: Cleaner, our free extension, has a Fix broken page button that clears the current site's cache and service workers, keeps your cookies, and reloads the page for you. Alt+Shift+D does it without opening the popup.

All three touch only the site you are on, so every other tab stays signed in. For a wider clean, see how to clear cache in Chrome.

Hard refresh vs clear cache vs clear site data#

These three get mixed up all the time, and they do very different amounts of work:

Start at the top and move down only when the step above did not work. Each step down costs a little more: a slower next visit, a lost session, or in the last row, logins on every site you use. If you ever find yourself at the bottom row for one broken page, a one-site clear would have done the job with none of the fallout.

Hard refresh on Android and iPhone#

Chrome on phones has no keyboard and no hidden reload menu. The closest thing to a hard refresh:

1. Open the three-dot menu, then Delete browsing data (on Android it is under History; on iPhone, under Settings, then Privacy and security).
2. Choose Last hour and tick only Cached images and files.
3. Delete, then reload the page.

Because you only ticked cache, you stay signed in. An Incognito tab is the other quick test: it loads the page with none of your stored data.

For developers: stop needing hard refresh#

If you hard refresh your own site fifty times a day, set it up once:

• Tick Disable cache in the DevTools Network panel. It applies while DevTools is open.
• In the Application panel, under Service workers, tick Update on reload while you work on a PWA.
• Use versioned file names (for example app.3f9a1.js) so a new deploy never collides with an old cached file.

Then hard refresh becomes what it should be: a rare, one-key fix.