Chromebook Aw, Snap! Error — Chrome Page Crash Fix

What it means

Chromebook 'Aw, Snap!' is the Chrome browser's page-crash error.
The exact wording on the page is: 'Aw, Snap! Something went wrong while displaying this webpage. To continue, reload or go to another page.'
It means Chrome's renderer process for that specific tab crashed — usually from a memory issue, a misbehaving extension, or a problem with the page itself.
The rest of Chrome and ChromeOS keep working; only the affected tab is broken until reloaded.

Affected Models

Every ChromeOS device — all Chromebook brands (HP, Acer, Lenovo, ASUS, Samsung, Google Pixelbook)
Same error appears in Chrome on macOS, Windows, and Linux — fixes are the same
Common on devices with 4 GB of RAM running many heavy tabs
Common after a Chrome auto-update that hasn't been followed by a restart
Common on pages with heavy JavaScript, ads, or video

Common Causes

Tab ran out of memory — ChromeOS killed the renderer to keep the system stable
Browser extension crashed or interfered with the page
Page itself has a JavaScript error that took down the renderer
Cached data for the site is corrupted
Chrome itself needs a restart after a background auto-update

How to Fix It

Reload the page.

Click the Reload button next to the address bar, or press Ctrl+R.
About 70% of Aw, Snap! errors are one-off renderer crashes that don't repeat — a single reload is all they need.
Close other tabs and reload.

Right-click the tab strip and choose 'Close other tabs' to free up memory.
Reload the crashed page.
If you're often hitting Aw, Snap!, you may be running near the Chromebook's memory limit — closing tabs you don't actively need is the simplest fix.
Restart the Chromebook.

Sign out and sign back in to give the browser a fresh start — or hold the power button for 3 seconds and choose Power off, then power back on.
A restart clears any background state Chrome accumulated since the last reboot.
Open the page in Incognito mode.

Press Ctrl+Shift+N to open an Incognito window and try the same URL.
Incognito disables all extensions by default.
If the page loads cleanly in Incognito, an extension is the cause — go to chrome://extensions and disable them one at a time until you find the culprit.
Clear the site's cookies and cache.

Click the padlock icon to the left of the address bar.
Choose Site settings > Clear data.
Reload the page.
Stale cached data is a common cause of Aw, Snap! on a single specific site.
Update ChromeOS.

Open Settings > About ChromeOS > Check for updates.
Install any pending update and restart.
A Chrome version mismatch between the browser process and the system can cause repeated Aw, Snap! crashes that an update fixes.
Powerwash as a last resort.

If Aw, Snap! happens on every page across multiple sites and survives all other fixes, open Settings > Advanced > Reset settings > Powerwash.
This factory-resets the Chromebook.
Your Google account files are preserved in Drive, but anything local will be wiped — back up Downloads first.

When to Call a Professional

Aw, Snap! is never a hardware service issue.
If reloading, clearing site data, and disabling extensions doesn't fix it, the page itself is the cause — try the same site on another device to confirm.
If every page on the Chromebook crashes constantly, the Chromebook is genuinely low on RAM or storage and Powerwash (full reset) is the last step.

Frequently Asked Questions

Does Aw, Snap! mean my Chromebook is dying?

No.
It's a Chrome-side error, not a hardware error.
The Chromebook itself is fine — only the tab's renderer process crashed.
If you only see Aw, Snap! occasionally and on heavy pages, that's normal Chrome behaviour under memory pressure.
If every page crashes every time, the device is genuinely low on RAM or storage and a Powerwash usually fixes that — still not a hardware fault.