Chrome 'Aw, Snap!' on Large PDFs: Quick Fix

Quick answer (for advanced users)

Open Chrome, paste chrome://flags/#renderer-process-limit in the address bar, disable the flag, then restart Chrome. This lifts the per-tab memory cap and usually stops the crash on PDFs over 50 MB.

Why Chrome throws 'Aw, Snap!' on big PDFs

I've seen this error a thousand times—user tries to open a 100-page scanned manual or a massive engineering drawing, and Chrome just gives up. The 'Aw, Snap!' screen is Chrome's way of saying the renderer process ran out of memory. By default, Chrome limits each tab to around 1 GB of RAM on 64-bit systems, but that's not always enough for PDFs with embedded fonts, high-resolution images, or hundreds of layers. I've personally hit this on Windows 10 with a 120 MB PDF of an assembly guide—Chrome died at 85% loaded.

The real culprit is Chrome's process management. It's designed to keep your whole browser stable, but it's too aggressive with memory-hungry tabs. The fix is simple: remove the cap.

Step-by-step fix: Remove the renderer memory limit

1. Type chrome://flags in your address bar and press Enter.
2. In the search box, type renderer process limit.
3. You'll see a flag called Renderer process limit. Click the dropdown and select Disabled.
4. A warning pops up—click Relaunch to restart Chrome.
5. After restart, try opening your large PDF again. It should load without crashing.

Note: This flag tells Chrome not to kill the renderer when it uses a lot of memory. It might slow down your system slightly if the PDF is enormous (over 300 MB), but it works 9 times out of 10.

If that doesn't work: Alternative fixes

Use Chrome's native PDF viewer in incognito mode

Extensions sometimes interfere. Open the PDF in an incognito window (Ctrl+Shift+N). Extensions are disabled there, so if it loads, you've got a bad extension. Remove them one by one until you find the troublemaker—I've seen ad blockers and 'save to PDF' extensions cause this.

Disable hardware acceleration

Graphics bugs can crash the PDF renderer. Go to chrome://settings/system and toggle off Use hardware acceleration when available. Relaunch Chrome. This helped a user I supported who was on an older Intel HD Graphics 4000 GPU—the PDF rendered fine after that.

Open the PDF in Adobe Acrobat Reader

This is my go-to workaround. Download the PDF, right-click it, and choose Open with > Adobe Acrobat Reader (or any dedicated PDF reader). Chrome's built-in viewer is lightweight but fragile. Adobe handles 500 MB files without flinching.

Use the command-line flag to increase memory per process

If the flag above didn't work, you can launch Chrome from the command line with a higher memory limit. Close Chrome, then open Command Prompt (cmd) and run:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --max_old_space_size=4096

This sets the max memory to 4 GB for the tab. It's a bit hacky, but it's saved me twice when debugging massive technical documents.

Prevention tip: Stop this from happening again

Once you've fixed the current PDF, you can prevent future crashes by keeping Chrome updated—Google's been tweaking the memory manager in every release since v110. Also, avoid opening PDFs from file servers directly in Chrome if they're over 30 MB. Download them first, then open locally. That way Chrome doesn't have to stream and render at the same time—a common trigger for the 'Aw, Snap!' error.

And if you regularly work with giant PDFs (think 200+ pages), just use Adobe Acrobat or Foxit Reader as your default. Chrome isn't built for heavy lifting, and that's okay—use the right tool for the job.