Excel Out of Memory on Large Files: 32-bit vs 64-bit

You open a 40 MB workbook and Excel stops with Excel cannot complete this task with available resources. Word says there is not enough memory to open the document. The machine has 32 GB of RAM, nothing else is running, and the same file opens fine on a colleague’s laptop.

The RAM number is usually beside the point. What matters is which build of Office you installed, because a 32-bit build has a ceiling no amount of memory can lift. Here is how to confirm it, how to stay under it, and when switching is worth the disruption.

Why a 32-bit build hits the ceiling

A 32-bit program runs inside a 32-bit address space, so it can only address a couple of gigabytes at once regardless of how much physical memory exists. Modern builds are large-address-aware, which buys some room on a 64-bit Windows, but the ceiling stays in the low single-digit gigabytes.

A workbook is not one block of memory. Excel holds the parsed cell table, the style table, pivot caches, the calculation chain and a copy of recent changes, and each of those is a separate allocation. When the process can no longer find one large enough contiguous region, it fails — the error names resources, not size, because the resource that ran out is address space.

File size on disk is a poor guide. An .xlsx is zipped XML, so a 30 MB file expands several times over once parsed, and a workbook that is mostly formatting and formulas expands further than one that is mostly numbers.

Fix 1 — Confirm which build you are running

Open the app and go File → Account → About Excel. The first line of the dialog ends with either 32-bit or 64-bit.

Two cross-checks if the dialog is not reachable: in Task Manager → Details, right-click a column header → Select columns → tick Platform, then read the row for EXCEL.EXE. Or open regedit and look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration, where the Platform value reads x86 or x64.

Do not judge by the folder. Click-to-Run installs both builds under C:\Program Files (x86)\Microsoft Office, so a 64-bit install sits in an x86-named directory.

Fix 2 — Shrink what the workbook has to hold

Reduce demand before you change the installation. Data → Get Data → From File → From Workbook, pick the file, then Transform Data and keep only the columns and rows you actually need before pressing Close & Load. The full sheet is never parsed into the model.

Two habits inflate the in-memory copy: whole-column references such as A:A pull over a million rows into every dependent calculation, and thousands of distinct cell formats cost more memory than the data they decorate. When a file is genuinely huge, save a copy as .xlsb — same features and formulas, binary storage, smaller on disk and quicker to parse.

Fix 3 — Free address space inside the running app

Close every other workbook and every other Office window. Each document opened in the same process takes its share, and a second 20 MB workbook can be what pushes the first one over.

Then strip the graphics layer: File → Options → Advanced → Display → tick Disable hardware graphics acceleration. Next, unload add-ins via File → Options → Add-ins → set Manage to COM Add-ins → Go → clear the ticks. Every COM add-in maps its own DLLs into that same limited address space, and a document-management or BI add-in can occupy more of it than the spreadsheet does. If an add-in keeps coming back, safe mode is the fast way to prove it is the cause.

Fix 4 — Split the workbook instead of the machine

If the data has to stay complete, keep one workbook per quarter, region or product line, and build a summary sheet that pulls from those parts with Power Query. You accept one maintenance step and gain years of headroom on a 32-bit build.

The same logic applies to Word. A 300-page manual with tracked changes and embedded objects behaves like a database, not a document; splitting by chapter and assembling at the end costs a step and removes the crash. If a file has already ballooned without gaining content, that is a different problem with a different fix.

Fix 5 — Move to 64-bit Office, and what it breaks

Uninstall the 32-bit build first; the two cannot coexist. For Microsoft 365, sign in at office.com, choose Install Office → Other install options, then pick 64-bit and the language before downloading. For managed deployments, the Office Deployment Tool does it with <Add OfficeClientEdition="64" Channel="Current">.

Check three things before you switch. 32-bit COM add-ins will not load and need 64-bit replacements. 32-bit ODBC drivers and the Access Database Engine must be reinstalled to match, or Access-linked queries and Power Query connectors stop working. VBA that calls the Windows API needs PtrSafe on each Declare and LongPtr where a handle was declared Long.

Microsoft still ships 32-bit as the default for Microsoft 365 precisely because third-party tooling lags, so treat this as a compatibility trade rather than an upgrade. The 64-bit build also uses more memory per object, since every pointer doubles in width.

When it is not worth fixing

If the same file opens on another 32-bit machine, bitness is not your problem — the difference is an add-in, a mapped drive, or a full temp folder. If the error appears on a file that used to open on this exact setup, the file probably changed, and repair is the right step before reinstalling anything.

And if 64-bit Office still refuses the workbook, the file is not merely large. Sending a copy for an assessment is cheaper than an afternoon of reinstalling; nothing is modified until you agree to it.

FAQ

How much memory can 32-bit Excel actually use? A process of that width can address a couple of gigabytes, less whatever the DLLs in it consume. Adding RAM changes nothing, because the limit is address space rather than physical memory.

Will 64-bit Excel open a file that 32-bit refused? Yes, when memory was the binding constraint, which is the usual case for large models. No, if the workbook is damaged or carries an unsupported feature — the error text is similar and the cause is not.

Is .xlsb safe to send to someone else? It opens in Excel without extra software and keeps every formula, but non-Microsoft tools read it poorly. Convert a copy back to .xlsx for recipients who only need to read the numbers.

Does 64-bit Office use more RAM? Somewhat more for the same workbook, because pointers and handles are twice as wide. The trade is a ceiling you will not reach against a footprint that is modestly larger.