Chrome 'Aw, Snap!' for specific sites — cache fix

You're not alone — and the fix is fast

Nothing worse than Chrome suddenly refusing to load a site you visit every day. Gmail works, YouTube works, but your bank's login page or your work's dashboard shows that dreaded tab with the broken puzzle piece and "Aw, Snap! Something went wrong while displaying this webpage."

The fix: clear your Chrome cache for that site only

I've trained dozens of techs. This is step one for any site-specific crash. Don't clear everything — just that one site's cache.

1. Open Chrome. Go to the site that shows the error. Leave it on the error page.
2. Click the lock icon (or the "Not secure" warning) just to the left of the URL in the address bar. It's in the top-left of the browser window.
3. Click Site settings from the dropdown. A new tab opens with permissions for that specific site.
4. In the new tab, look for the Storage section. Click the button that says Clear data. After you click it you'll see a small confirmation message at the bottom of the screen: "Data cleared."
5. Go back to the error tab. Click the reload button (the circular arrow, or press F5 on your keyboard).

That's it. The page should load normally now. If you still see the error, try step 6:

Step 6 (if still broken): Close and reopen Chrome completely. Then try loading the site again. I've seen cases where a lingering background process holds onto the old cache data.

Why clearing cache fixes this

Chrome caches parts of web pages — images, scripts, stylesheets — to make loading faster on repeat visits. When you visit a site, it checks if a cached version exists. If that cached version gets corrupted (a byte flips during download, a disk write fails, whatever), Chrome can't reconcile it with the live site. It throws up its hands and gives you "Aw, Snap!"

Think of it like a library book with pages glued together. You ask for page 45, but the glue makes the page unreadable. The librarian (Chrome) can't fix it, so it tells you the book is broken. Clearing the cache is like throwing that specific book away and requesting a fresh copy from the publisher.

The error shows only on specific sites because each site has its own cached data. Other sites with clean cache load fine.

Less common variations of the same problem

1. Corrupted cookies instead of cache

Sometimes a corrupted cookie — not a cache file — causes the same error. Cookies are tiny text files that store login state and preferences. If one gets corrupt, the site can't process it. The fix is similar: go to Site settings for that site, and instead of "Clear data" (which clears both cache and cookies), expand the Cookies section and click the trash icon next to any listed cookie. Then reload.

2. Outdated or corrupted extension

An extension can mess with specific sites. I've seen ad blockers break banking sites, and password managers corrupt form data. To test: open Chrome's menu (three dots top-right), go to More Tools > Extensions, and toggle off all extensions. Then try loading the site. If it works, turn extensions back on one by one until the error returns. That's your culprit.

3. Third-party cookies blocked

Some sites rely on third-party cookies for embedded content (like payment processors or video players). If you've set Chrome to block all third-party cookies (it's a default in newer versions), those embedded parts fail, triggering "Aw, Snap!" Fix: go to Site settings > Third-party cookies and set it to "Allow" for that specific site.

4. Hardware acceleration glitch

Chrome uses your GPU to render pages faster. Sometimes a driver update or bug causes GPU rendering to fail. When that happens, the whole page crashes. To check: go to Chrome settings > System > toggle off Use hardware acceleration when available. Relaunch Chrome and try the site.

How to stop this from happening again

You can't fully prevent cache corruption — it's a rare random event. But you can reduce the odds:

• Update Chrome regularly. Google fixes cache-handling bugs in each release. Go to Settings > About Chrome to check for updates.
• Don't close Chrome by killing the process. Use the X button or File > Exit. Force-killing Chrome (via Task Manager or holding power button) can corrupt its cache files.
• Use Incognito mode for sensitive sites. Incognito doesn't save cache or cookies at all. If a site crashes in normal mode but works in Incognito, you know it's a cache/cookie issue.
• Run Chrome's built-in cleanup tool every few months: go to Settings > Privacy and security > Clean up computer > Find. This removes harmful software that can corrupt browser data.

One last tip: if you see "Aw, Snap!" frequently on multiple sites, run a malware scan. Some adware strains deliberately corrupt Chrome's cache to inject their own ads. Free tools like Malwarebytes AdwCleaner catch these.