Chrome 32-bit Out of Memory on 64-bit Windows: Real Fix

If you're seeing Out of Memory in Chrome on a 64-bit Windows machine, it's not your RAM. It's the browser. Chrome's 32-bit build is stuck with a ~2GB memory ceiling per process, and modern web apps like Figma, Google Sheets with big datasets, or Teams can blow past that in minutes. I've watched people throw 32GB of RAM at this problem and still crash. The real fix is switching to the 64-bit build. Here's how to confirm and fix it, from easiest to most thorough.

Quick check (30 seconds)

Open a new tab and paste this into the address bar:

chrome://version

Look at the first line. If it says something like Google Chrome 120.0.6099.130 (Official Build) (32-bit), you've found the problem. On a 64-bit Windows install, that (32-bit) tag is the whole reason you're hitting Out of Memory. A 32-bit process can only address about 2GB of RAM, no matter how much physical memory your PC has. Chrome will happily eat 3GB on a heavy page, then die.

Don't bother with flags like --max_old_space_size or --js-flags="--max-old-space-size=4096". People share those in forum threads constantly and they don't help here. You're fighting a pointer-width limit, not a V8 heap setting.

The moderate fix — reinstall the 64-bit build (5 minutes)

Chrome usually auto-updates to 64-bit on capable hardware, but it won't migrate itself if it was installed the old way, if it was pushed by a third-party installer (looking at you, bundled toolbars), or if a system policy pinned the 32-bit channel.

1. Go to chrome://settings/help first. If it doesn't offer a 64-bit update, move on.
2. Sync your bookmarks and passwords if you haven't (sign into your Google account, then chrome://settings/syncSetup).
3. Download the 64-bit installer directly from Google — the "Chrome offline installer" page has separate 32-bit and 64-bit links. Pick 64-bit.
4. Close every Chrome window. Check Task Manager (Ctrl+Shift+Esc) and end any lingering chrome.exe processes.
5. Run the installer. It overwrites the existing install — you don't need to uninstall first.
6. Reopen Chrome, visit chrome://version, and confirm it now shows (64-bit).

That's it for most people. The 64-bit build can address far more memory, and the Out of Memory error on big web apps goes away. If Chrome still refuses to switch, keep reading.

The advanced fix — clean reinstall when the 64-bit build won't take (15+ minutes)

If chrome://version still says 32-bit after installing the 64-bit package, something is dragging you back. The usual suspects:

• A stale Chrome Update service or scheduled task that reinstalls the 32-bit version.
• A registry entry under HKLM\SOFTWARE\WOW6432Node\Google\Update\Clients that flags the install as 32-bit only.
• Enterprise policy via Group Policy or HKLM\SOFTWARE\Policies\Google\Chrome that specifies an update channel or architecture.
• A third-party "system optimizer" that quietly reinstalls its preferred Chrome build.

Here's the clean path:

1. Uninstall Chrome from Settings → Apps → Installed apps. Don't just delete the folder.
2. Delete these folders if they remain (they usually do):

   %LOCALAPPDATA%\Google\Chrome
   %PROGRAMFILES%\Google\Chrome
   %PROGRAMFILES(X86)%\Google\Chrome

3. Open Services.msc and stop Google Update (gupdate) and Google Update (gupdatem).
4. Open Task Scheduler and disable the two GoogleUpdate tasks under GoogleUpdateTaskMachineCore and GoogleUpdateTaskMachineUA.
5. Delete HKLM\SOFTWARE\WOW6432Node\Google\Update and HKLM\SOFTWARE\Google\Update (back up first — export the keys).
6. Reboot. Yes, actually reboot.
7. Install the 64-bit Chrome offline installer again. Re-enable the Google Update services afterward.

After this, chrome://version should show (64-bit) and the Out of Memory error on large web apps stops. I've had to do this exactly once on a machine that had a crusty HP OEM image with 32-bit Chrome baked in — every other case resolved with the moderate fix.

Why the error shows up on specific sites

You probably noticed it isn't random. It hits on tabs with large in-memory datasets — a 200MB CSV open in Google Sheets, a Figma file with dozens of frames, an Excel Online workbook with pivot tables, a Teams call sharing a screen while you have Slack and Gmail open in the same browser. Each of those can push a renderer process past 1.5GB. On 32-bit, the process hits the wall and Chrome kills the tab with Out of Memory. On 64-bit, it just... doesn't.

If you only take one thing away: check chrome://version before you touch RAM, page files, or registry tweaks. Half the "Chrome out of memory" threads online skip this step and waste hours.

What NOT to bother with

• Increasing your page file. Doesn't help. Windows will happily hand out virtual memory; the 32-bit process just can't use it.
• Disabling hardware acceleration. Occasionally smooths crashes from GPU drivers, but has zero effect on a 32-bit address-space limit.
• Chrome flags for memory. --memory-pressure-off and --single-process are last resorts that trade one problem for three worse ones. Skip them.
• Adding more RAM. If Chrome is 32-bit, an extra 32GB of DDR5 changes nothing.

Once you're on 64-bit, if you still see Out of Memory errors, the next thing to check is a browser extension leaking memory — open chrome://extensions, disable everything, and see if the crashes stop. But that's a different article.