How to Fix Chrome "Aw, Snap!" Page Crashes

By FixMyError · Updated October 13, 2026 · 6 min read

What "Aw, Snap!" crashes means

"Aw, Snap!" is Chrome's friendly face for an unfriendly event: the renderer process behind a tab crashed or was killed. Each Chrome tab runs its own renderer, so one misbehaving page can die without taking the whole browser down — and you get the sad folder icon with the "Aw, Snap!" message instead of the site.

The crash can come from the page itself (a heavy site eating too much memory), from your side (a buggy extension, corrupted cached files, or an out-of-date Chrome), or from the system (low RAM, an overzealous antivirus injecting code into Chrome). Because the causes are varied, the fix is a process of elimination: start with the quickest checks and move toward the deeper ones.

Common causes

• Buggy or outdated extensions: a misbehaving extension can inject broken scripts into every page and crash the renderer — this is the single most common cause.
• Corrupted cached files: damaged cache or cookie data for a specific site can crash its tab every time it loads.
• Out-of-date Chrome: older builds contain renderer bugs that are fixed in later releases.
• Low system memory: when RAM runs out, Chrome kills the hungriest tab — often a heavy page with lots of media or dozens of open tabs.
• Antivirus or security software interference: some security tools hook into Chrome's processes and destabilize them, especially after either program updates.

How to fix "Aw, Snap!" crashes — step by step

Work through these fixes in order. Most "Aw, Snap!" crashes are fixed by step 2 or 3.

1. Reload the page. Press Ctrl + R (or Cmd + R on a Mac), or click the circular Reload button in the address bar. A one-off crash from a momentary memory spike or a network hiccup often clears on a simple reload. If the crash only happens on one specific site, that site is likely the trigger — but still work through the steps below before blaming it.
2. Disable your extensions one by one. Type chrome://extensions in the address bar. Toggle off every extension, then reload the crashing page. If the crash stops, re-enable extensions one at a time, reloading the page after each, until the crash returns — the last one you enabled is the culprit. Remove or update it, and check whether it has a known crash issue in its reviews. Start with ad blockers, coupon finders, and any extension you installed recently.
3. Clear your browsing data. Press Ctrl + Shift + Delete to open the Clear browsing data dialog. Set the time range to All time, check Cached images and files and Cookies and other site data, then click Clear data. Restart Chrome afterward. This wipes the corrupted files that can crash a tab on load. You will be signed out of most sites, so keep your passwords handy — consider using Chrome's saved-passwords feature or a password manager.
4. Update Chrome. Click the three-dot menu, then Help, then About Google Chrome. Chrome checks for updates automatically on this page; if an update is available, click Relaunch to install it. Renderer crashes are frequently fixed in newer builds, so running the latest version matters. While you are at it, restart your computer — a reboot frees up the RAM that low-memory crashes feed on.
5. Check your antivirus and firewall. Temporarily disable your third-party antivirus (keep Windows Defender or your Mac's built-in protection in mind as a fallback) and reload the crashing page. If the crash disappears, add Chrome to the antivirus's exceptions or allowlist, then re-enable protection immediately. Some security suites also offer a "browser protection" component that injects into Chrome — try disabling just that component first.
6. Reset Chrome settings or create a fresh profile. As a deeper fix, open Settings, then Reset settings, then Restore settings to their original defaults, and confirm. This disables extensions, clears temporary data, and resets the startup page and search engine without deleting bookmarks, history, or saved passwords. If you want an even cleaner test, add a new Chrome profile (click the profile icon, then Add) — if the new profile never crashes, your old profile's data was the problem and you can migrate to the fresh one.

Did this fix it? Quick checklist

• Pages reload without the "Aw, Snap!" screen
• The previously crashing site loads and stays open
• Chrome is on the latest version
• No crashes after restarting Chrome and your computer

If "Aw, Snap!" appears on every single page, even chrome://settings, the problem is system-level: scan for malware, check that your RAM is not failing (run Windows Memory Diagnostic from the Start menu), and make sure Chrome is not being blocked by enterprise policy software. In that case a full Chrome reinstall — uninstall, delete leftover profile data, then install fresh from google.com/chrome — is the reliable last resort.