How to Fix a Crashed Tab in Chrome ("Aw, Snap!")

You're mid-scroll and the page goes gray: "Aw, Snap! Something went wrong while displaying this webpage." One tab, dead. The good news is right there in the name of the error — it's that tab, not your browser.

What "Aw, Snap!" actually means

Chrome runs every tab in its own separate process, isolated from the others. That's a deliberate design choice: it's why one broken page can't take down the tabs next to it, and why you can close a frozen tab without losing anything else you had open.

"Aw, Snap!" means that one tab's process crashed or was killed. Your other tabs, your extensions, and the rest of the browser keep running exactly as they were.

Fix it: the quick checklist

Work through these in order — most crashes resolve in the first step or two.

1. Reload the tab. Click the reload icon, or press Ctrl+R (Cmd+R on Mac). This alone fixes the majority of one-off crashes, especially if the page just hit a temporary script error or a bad response from the site.
2. Close a few other tabs, then reload. If Chrome is under memory pressure — a lot of tabs open, several of them heavy (video, editors, dashboards) — it may have killed this tab's process to free RAM for something else. Freeing memory elsewhere and reloading often stops the crash from repeating.
3. Restart Chrome. Close the whole browser and reopen it. This clears out any stuck background processes without touching your other windows' tabs, which restore automatically if you have "Continue where you left off" enabled.
4. Restart your computer. Rare, but a full system restart clears OS-level memory and GPU driver issues that a browser restart alone doesn't reach.

If the same specific page crashes every time you visit it, even after all four steps, move to the causes below — something about that page or your setup is triggering it consistently, not just a one-off.

Common causes, and the fix for each

Too many tabs, not enough memory

Every open tab holds real memory, and Chrome will kill background tab processes under pressure before it lets the whole browser crash. If you regularly run 40, 80, 100+ tabs, occasional "Aw, Snap!" pages aren't a bug — they're Chrome protecting itself. See How Many Tabs Can Chrome Handle? for what actually degrades as tab count climbs, and Why Chrome Uses So Much Memory for what Memory Saver does and doesn't fix.

Fix: close or save tabs you're not actively using, rather than leaving them open "just in case."

A GPU process crash

Chrome offloads rendering to your graphics hardware. A flaky GPU driver, an outdated one, or a conflict with another app using the GPU can crash that process — which shows up as "Aw, Snap!" on whatever tab was rendering at the time.

Fix: open chrome://gpu to check for reported crashes, update your graphics driver, or try toggling hardware acceleration off at chrome://settings/system and restarting Chrome to see if the crashes stop.

A misbehaving extension

Extensions run code on every page they're allowed to access. A buggy one can reliably crash specific pages or types of pages.

Fix: open chrome://extensions, disable them one at a time (or all at once, then re-enable one by one), and revisit the page that was crashing to isolate which one is responsible.

A corrupted cache or profile

Less common, but a damaged local cache can make one page consistently fail to render.

Fix: clear browsing data (chrome://settings/clearBrowserData) for cached images and files, or — as a last resort — create a new Chrome profile and see if the crash follows you there. If it doesn't, the old profile's data was the problem.

The part a reload can't fix

Reloading brings the page back, but it doesn't bring back what was in it: a half-filled form, a document you hadn't saved, or your place in a long research session. And a crash never asks first — you don't get a warning to save anything before the tab dies.

If the crashed tab was one of many you had open around a task, the bigger cost usually isn't the one tab — it's not being sure what else you had open, or where.

Amazing Tabs removes that uncertainty by making "save first" the default instead of an afterthought:

• Save a tab or a whole window in one click, before it becomes the one that crashes — so a dead tab is never the only copy of what you were doing.
• Press / to search everything you've saved by title or content, so finding the exact page you had open takes seconds, not a rebuild-from-memory.
• Sessions survive independently of the live browser state — a saved tab doesn't care whether the original tab crashed, closed, or is still open.
• Free for up to 100 saved links, so building this habit costs nothing.

Stop losing tabs to a gray screen. Add Amazing Tabs to Chrome — free, no signup. Save your open tabs once, and a crash on any of them stops being a problem.

Quick recap

• "Aw, Snap!" is process-isolated — one tab crashed, not your browser or your other tabs.
• Reload first. It fixes most crashes on its own.
• Still crashing? Free up memory, restart Chrome, then your computer — in that order.
• Same page crashing repeatedly points to memory pressure, a GPU/driver conflict, a bad extension, or a corrupted cache — work through them one at a time.
• A reload can't recover unsaved work or your place in a session — save what matters before it's the tab that crashes, not after.

Further reading: How Many Tabs Can Chrome Handle? if crashes are becoming a regular thing, How to Recover Closed Tabs in Chrome if you're here because a crash took a tab with it, or Chrome's "Leave Site?" Warning, Explained for why an orderly close sometimes prompts you and a crash never does.