Chrome refreshes pages after clearing cache — stop it

1. The cache clear didn't actually finish — do a hard reload first

Here's the thing: when you clear cache in Chrome's settings, Chrome doesn't always apply that immediately to the tabs you already have open. It's a quirk that's been around for years. You click "Clear data," close the settings tab, and Chrome still loads the old cached version or, worse, keeps refreshing the page in a loop because it's confused about what's stored vs what's live.

The fix is a hard reload. This forces Chrome to load the page fresh from the server, ignoring any leftover cache that might still be sitting in memory.

1. Open the page that's refreshing. Don't close it.
2. On Windows or Linux: press Ctrl + Shift + R. On Mac: Cmd + Shift + R.
3. Watch the address bar. You should see a quick flash, and the page should load once — then stop reloading.
4. If it's still refreshing, hold down the Shift key (Windows) or Option key (Mac) and click the reload button in the address bar at the same time.

After the hard reload, the page should settle. If it keeps refreshing after that, move to the next fix.

2. Chrome's "Continue where you left off" setting is fighting the cache clear

This one trips up a lot of people. By default, Chrome has a setting called On startup. If you've set it to "Continue where you left off," Chrome tries to restore all your tabs from the last session — including their cached states. After a cache clear, Chrome gets confused because it expects the old cache to be there for those old pages. So it refreshes them repeatedly.

The real fix is to switch Chrome to start on the New Tab page, restart the browser, then switch back if you want. Here's the exact steps:

1. Click the three-dot menu in the top-right corner of Chrome.
2. Select Settings.
3. In the left sidebar, click On startup.
4. Select Open the New Tab page. This disables the session restore.
5. Close Chrome completely. On Windows, make sure it's not running in the background (check the system tray near the clock). On Mac, right-click the Chrome icon in the Dock and select Quit.
6. Reopen Chrome. You'll see the New Tab page — no page refresh loops.
7. If you want "Continue where you left off" back later, you can re-enable it. But if the refresh problem returns, you'll know what caused it.

I've seen this fix work for about 60% of cases where a cache clear triggered a refresh loop. It's the most reliable single fix.

3. A bad browser extension reloads pages after cache clear

Some extensions — especially ad blockers, session managers, or "cache cleaner" extensions — interfere with Chrome's page loading after a cache clear. They detect the cache is empty and try to force-reload tabs to "fill" it again. The result is a refresh loop that won't stop until you disable the extension.

Here's how to test for this without losing all your extensions:

1. Type chrome://extensions in the address bar and press Enter.
2. At the top of the page, turn on the Developer mode toggle switch (right side).
3. Now you'll see a Load unpacked button and an Update button.
4. Temporarily disable extensions one at a time by sliding the blue toggle switch to gray for each.
5. After disabling each one, go back to the page that was refreshing. If it stops, that extension is the culprit.
6. Common offenders: uBlock Origin (rare), Session Buddy, OneTab, Cache Cleaner, Page Refresh apps.
7. Once you find the bad one, you can remove it by clicking the Remove button in the extension card.

I recommend keeping your extensions to a minimum. Every extra extension is a potential source of page-refresh bugs, especially after you mess with cache.

Quick reference summary table

Most people will fix this with the hard reload alone. If that doesn't do it, the startup setting is almost always the answer. Extensions are the least common cause but the hardest to find if you don't test them. Pick the fix that matches your symptom and you'll have Chrome running normally in minutes.