Hard Refresh Chrome or Any Browser: Free Shortcut Finder

How to Hard Refresh Chrome

1. Go to the page that looks wrong

   Click anywhere on the page so the tab has focus. A hard refresh only affects the tab you are in, not your other tabs.

2. Press the hard refresh shortcut

   On Windows, Linux and ChromeOS press Ctrl + Shift + R. On a Mac press Cmd + Shift + R. On Windows, Ctrl + F5 and Shift + F5 do the same thing.

3. Or use the mouse

   Hold Shift and click the reload button to the left of the address bar. This gives the same result as the shortcut.

4. Go further with “Empty cache and hard reload”

   If the page still looks stale, open DevTools with F12 (Cmd + Option + I on a Mac), then right-click the reload button and choose “Empty cache and hard reload”.

5. Check your own browser above

   The finder at the top of this page detects your browser and system and shows the exact keys. Use the picker to look up a different browser, or press a shortcut in the test area to see what it does.

How This Shortcut Finder Works

The finder runs entirely in your browser. When the page loads, it reads the user-agent string and, in Chromium browsers, User-Agent Client Hints to work out which browser and operating system you are using. It then looks up the matching shortcuts in a table that ships with the page. Nothing is sent to a server, and there are no analytics calls with your details.

The test area listens for key presses while this tab is active. It turns each combination into readable keys, such as Ctrl + Shift + R, and tells you what that combination does in your browser. It doesn’t block or change the shortcut, so a reload shortcut really does reload the page. Before the reload happens, the page saves one small note in session storage: the keys you pressed and the time. After the reload it reads the note, deletes it, and checks the Navigation Timing API to confirm the page was reloaded rather than opened fresh.

Session storage belongs to this tab only and is cleared when you close it. The page never records ordinary typing, only combinations that use Ctrl, Alt, Option, Cmd or a function key, and it forgets them straight away.

A web page can’t tell a hard reload from a normal one. The browser reports both as “reload”. The finder shows the keys it saw just before the reload, which tells you which one you asked for, but it can’t confirm that the cache was skipped.

What Is a Hard Refresh?

A hard refresh reloads the page you are on and tells the browser not to use its cached copies of the page or the files it loads. Browsers keep a cache of pages, stylesheets, scripts, images and fonts so that sites open faster the next time. Usually that is what you want. But when a site has just been updated, the cache can hold on to an old stylesheet or script, and the page looks broken or out of date until the cached copy expires.

A normal reload still leans on the cache. For each file the browser asks the server whether its stored copy is still current, using the If-None-Match and If-Modified-Since headers, and the request carries Cache-Control: max-age=0. If the server replies 304 Not Modified, the browser reuses what it has. That check is quick, but it relies on the server and any caches along the way getting the answer right.

A hard reload skips that check. The browser sends every request for the page and its subresources with Cache-Control: no-cache and Pragma: no-cache, and without the conditional headers, so the server has to send a full, fresh response. MDN’s HTTP caching guide shows both requests side by side, and the Fetch standard defines the same behaviour as the “reload” cache mode. The new copies then replace the old ones in the cache.

Two things a hard refresh doesn’t do: it doesn’t delete the cache for other sites, and it doesn’t clear cookies, local storage or saved logins. That is why it is safe to use at any time. You stay signed in, your other tabs are untouched and nothing else changes.

Chrome, Edge, Brave, Opera, Vivaldi and Arc all use Chromium, so they share the same hard reload command and, by default, the same keys. Firefox and Safari have their own versions. Safari calls it Reload Page From Origin.

Hard Refresh Shortcuts for Every Browser and OS

This table lists the hard refresh keys for each desktop browser. The Chromium shortcuts come from Chromium’s accelerator table, the source file that defines Chrome’s keyboard shortcuts on Windows, Linux and ChromeOS, and from Google’s own help page. The Firefox shortcuts come from Firefox’s source. Where a browser doesn’t exist on a system, the cell says so.

On a Mac, Shift + F5 and Ctrl + F5 don’t hard refresh in Chrome. The F5 shortcuts are only defined for Windows, Linux and ChromeOS. Vivaldi lets you change its shortcuts, so a customised setup may differ from this table.

Clear Cache Shortcut and DevTools Keys

The clear cache shortcut opens the browser’s clear browsing data window. It doesn’t clear anything on its own; you pick the time range and the kinds of data, then confirm. In Chrome the window is now called “Delete browsing data”. To clear only the cache, tick “Cached images and files” and untick the rest, so you keep your history, cookies and passwords.

Normal Reload vs Hard Reload vs Empty Cache and Hard Reload

Chromium browsers offer three levels of reload, and it helps to know which one to reach for. The first two have shortcuts. The third lives in a menu that only appears while DevTools is open: right-click or long-press the reload button and choose “Empty cache and hard reload”.

Hard reload re-downloads the files the page asks for when it loads. Empty cache and hard reload goes one step further and throws away the cached files for that page first, which also catches files a script loads later, after the page has appeared. That matters on sites that fetch code or images on demand. Despite the name, it isn’t limited to one page: it runs the same “clear browser cache” command as the Network panel, so other sites may load a little slower on their next visit. Cookies and logins are still untouched.

Our verdict: start with a hard reload. It is instant and changes nothing else. Use empty cache and hard reload next. Clear all browsing data only as a last resort, because ticking cookies signs you out of sites.

How Do I Clear the Cache for One Site Only?

You often don’t need to clear everything. Every major browser lets you remove the stored data for a single site, which fixes that site without touching the rest of your browsing. Removing a site’s data also removes its cookies, so you will be signed out of that one site.

• Chrome, Edge, Brave, Opera, Vivaldi: open DevTools on the site, go to Application, then Storage, and click “Clear site data”. This clears the cache, cookies, local storage and service workers for that site only.
• Chrome without DevTools: open chrome://settings/content/all, search for the site and click the bin icon next to it.
• Firefox: click the padlock in the address bar and choose “Clear cookies and site data”.
• Safari on Mac: Settings, then Privacy, then Manage Website Data. Select the site and click Remove.
• Safari on iPhone: Settings, then Apps, then Safari, then Advanced, then Website Data. Swipe left on the site and tap Delete.

How to Hard Refresh on iPhone and Android

Phones don’t have a hard refresh. Tapping reload or pulling the page down does a normal reload. To force a fresh copy, clear that site’s data, or clear only the cached files, and then reload. Pick Android or iPhone in the finder above for steps that match your browser.

On Android, Chrome’s “browsing history” option includes your open tabs, so deleting history also closes them. Untick it if you only want to clear the cache.

When a Hard Refresh Doesn’t Fix It

A hard refresh only replaces what is in your browser’s HTTP cache. If the stale copy lives somewhere else, you need a different fix.

• Service workers. Sites that work offline install a service worker that can answer requests from its own cache. A hard reload skips the service worker for that one load, but the next normal load goes through it again. Use “Clear site data” for the site, or close all its tabs so the new version can take over.
• A CDN or server cache. If the site’s own cache still holds the old file, a hard reload fetches the old file again. Only the site owner can purge it. Waiting a few minutes often helps.
• DNS. If a site moved to a new server and you still reach the old one, the problem is the address lookup, not the page cache. Restarting the browser, or flushing the system DNS cache, fixes that.
• Cookies and logins. Sign-in loops and “session expired” errors come from cookies, which a hard refresh leaves alone. Clear that site’s cookies instead.
• Extensions. An ad blocker or script blocker can break a page in exactly the same way on every reload. Try a private window, where most extensions are off by default.

For Developers: Disable the Cache While DevTools Is Open

If you are working on a site, pressing a hard refresh after every change gets old quickly. In Chrome, Edge and the other Chromium browsers, open DevTools, go to the Network panel and tick “Disable cache”. As long as DevTools stays open, that tab doesn’t use the cache, so every normal reload behaves like a hard reload. Firefox has the same “Disable Cache” checkbox in its Network panel.

Two related tools help with stubborn cases. Right-clicking in the Network request list offers “Clear browser cache”. And the Application panel’s Service workers section has “Update on reload”, which installs a fresh service worker on every navigation, and “Bypass for network”, which sends requests past the service worker to the network.

For your visitors, the lasting fix is cache busting: put a content hash in each asset’s file name, such as app.3f9c2a.js, and serve those files with a long max-age. Serve the HTML itself with Cache-Control: no-cache so browsers always check for a new version. Then nobody has to hard refresh after you deploy.