FIX Chrome Memory Leak with Word Online and Office 365 (2026)

Key takeaways

• A Word Online tab open for 60 minutes can hold 1–3 GB of RAM Chrome never reclaims — V8 GC does not aggressively clean up long-lived web app heaps.
• Closing and reopening the document tab resets the heap instantly. Not elegant, but it works.
• Chrome Memory Saver is dangerous here — it can discard your active document tab while you’re in another app.

Your fan spins up 40 minutes into editing a Word document you haven’t even scrolled. Task Manager shows Chrome consuming 2.5 GB — for a 30-page doc in a browser tab. This is a known pattern with Office 365 web apps, and it is not a Chrome bug in the traditional sense. It is what happens when complex web apps accumulate memory faster than Chrome’s garbage collector reclaims it.

As of June 2026, there is no patch from Microsoft or Google that eliminates this. There are workarounds that keep the problem manageable.

Why Office 365 Leaks RAM in Chrome

Word Online, Excel Online, and the rest of the Office 365 suite are single-page applications that maintain three separate memory-hungry systems simultaneously.

First, undo history. Every keystroke, format change, and paste operation is stored in memory as a reversible action. A 60-minute editing session on a large document can build an undo stack with hundreds of entries, each holding a snapshot of document state.

Second, real-time collaboration. Office 365 maintains a persistent WebSocket connection for co-authoring and auto-save — even if you are working alone. That connection accumulates state as the document changes.

Third, auto-save. Every 30-60 seconds, Office 365 serializes the current document state, computes a delta, and transmits it. The data from previous save cycles is often held in memory longer than necessary.

Chrome’s V8 garbage collector is optimized for typical web browsing — pages you load, interact with briefly, and navigate away from. A JavaScript heap that grows steadily for an hour without the page navigating falls outside its aggressive reclamation window. Memory grows, GC runs occasionally but incompletely, and the remainder accumulates.

The numbers worsen with document complexity. A document with embedded images, tracked changes, or many contributors builds the undo stack faster and maintains more collaboration state.

Fix 1: Close and Reopen the Document Tab Every 30–60 Minutes

Blunt, but effective. When you close a Chrome tab, the renderer process for that tab is terminated. All V8 heap memory — including every cached document state, undo snapshot, and WebSocket buffer — is returned to the OS. When you reopen the document, Word Online reloads from the auto-saved cloud state.

The RAM reset is immediate. A tab that was consuming 2.5 GB drops to zero on close. The fresh tab starts around 150–300 MB and only climbs after editing resumes.

Office 365 auto-saves every 30–60 seconds, so no work is lost when you close a document tab that has been auto-saving normally. Check the “Saved to OneDrive” or “Saved to SharePoint” indicator in the Word Online toolbar before closing — if it shows a pending save, wait for it to confirm first.

This works for Excel and PowerPoint Online too. Any Office 365 tab that has been open for an hour and shows elevated memory in Shift+Esc → Task Manager benefits from a forced close and reload.

Fix 2: Open Chrome Task Manager and Monitor Before It Becomes a Problem

Press Shift + Esc to open Chrome’s built-in Task Manager. Sort by the Memory Footprint column.

Look for the tab row representing your Office 365 document. The number in that column is the renderer process memory for that tab — this is the figure that leaks upward over time.

If you have multiple Office tabs open, each row in Task Manager shows its own footprint. The cumulative number is what matters for system performance — multiple Office tabs can collectively consume 5–8 GB on a 16 GB machine, leaving Chrome struggling to serve even lightweight tabs alongside.

Fix 3: Disable Browser Extensions on Office 365 Domains

Extensions that inject content scripts run inside the same renderer process as Word Online. Their code competes for the same heap space, and some injection-heavy extensions interact poorly with complex SPAs — holding references to DOM nodes that Office 365 would otherwise release.

To test whether an extension is worsening the leak:

1. Open a fresh Word Online document in a normal window and work for 30 minutes. Note the memory in Task Manager.
2. Open a Chrome window in Guest mode or Incognito (with “Allow in incognito” disabled for your extensions). Open the same type of document and work for 30 minutes.
3. Compare the Task Manager memory between the two windows.

If the Incognito window stays materially lower, an extension is contributing. Go to chrome://extensions/, open Details for any extension with broad permissions, and toggle On specific sites. Add office.com and microsoft365.com to the blocked list.

Extensions most likely to interact with Office 365: AI writing assistants (Grammarly, Copilot extensions), grammar checkers, and any extension with <all_urls> host permissions.

Fix 4: Use Fewer Simultaneous Office Tabs

Each open Word Online, Excel, or SharePoint tab maintains its own WebSocket connection, its own undo stack, and its own serialized document state. Three open Office tabs triple the baseline memory cost before any editing accumulates.

The practical advice is direct: keep one Office tab open at a time for heavy work sessions. If you need to reference one document while editing another, open a second tab, do the reference check, and close it before returning to primary editing. The auto-save state persists in OneDrive — reopening is instant.

For spreadsheets specifically, Excel Online with complex formulas, pivot tables, or large datasets has a higher memory ceiling than Word Online. Do not run both simultaneously unless your machine has 16 GB or more available for Chrome.

Fix 5: Suspend Everything Else While Editing Office Documents

The most sustainable fix is not reducing Office 365’s memory — it cannot be reduced without closing the tab. The fix is freeing RAM everywhere else so that Office’s growing heap has room to expand without hitting system limits.

When Chrome runs out of available RAM, the OS starts writing to the pagefile (on Windows) or swap (on macOS), which degrades performance significantly. If you keep 15–20 tabs open while editing a Word document, the combined memory pressure forces this earlier.

Discarding inactive tabs before they accumulate is the structural solution. Chrome’s chrome.tabs.discard() API terminates a tab’s renderer process while keeping the tab visible in the bar — it reloads on click. Each discarded tab drops from 70–400 MB to approximately 5 MB of metadata.

SuperchargePerformance does this automatically. Tabs inactive for a configurable period (15 minutes at level 1, 5 minutes at level 2) get discarded while you edit. For Office 365 specifically: go to the extension’s whitelist settings and add office.com — this ensures your Word Online or Excel tab is never discarded mid-session, while everything else clears aggressively.

The 25+ auto-protected web apps in SuperchargePerformance include Google Docs, Sheets, and Slides. They are never suspended. Office 365 requires a manual whitelist addition since it is a Microsoft property rather than a default-protected app. Adding it takes 10 seconds and stays persistent.

The math across a typical session: suspending 12 inactive tabs frees 70–75% of total Chrome RAM, creating headroom that delays or prevents the point at which Office 365 memory pressure forces OS-level swapping. Per-discarded-tab savings are 90–95% of that tab’s renderer memory.

Why Chrome Memory Saver Is the Wrong Tool Here

Chrome’s built-in Memory Saver (Settings → Performance → Memory Saver) seems like the obvious fix. It is not — for Office 365 use specifically.

Memory Saver applies the same inactivity detection to all tabs. If you switch to a different app (a terminal, Slack, or your email client) for a few minutes while a Word document is open, Memory Saver can classify that tab as inactive and discard it. When you return to Chrome, your document tab has been suspended. Word Online reloads from the last auto-save, but any unsaved changes in the current editing state are gone.

There is no per-domain exception in Chrome Memory Saver. You cannot tell it “never suspend office.com.” It is an all-or-nothing setting.

For general RAM management with many tabs, Memory Saver is fine. For protecting active document editing while clearing idle tabs, it is not the right tool.

When to Switch to the Desktop Office Apps

Not every document belongs in a browser tab. Three cases where switching to the desktop app is the right call:

Documents over 50 pages with images. The web versions of Word and PowerPoint are not optimized for large multi-media documents. They render the entire document state in the browser tab, whereas the desktop apps stream sections on demand. Memory usage is categorically different.

Long editing sessions (2+ hours). If you are in a document for two hours, the accumulated undo stack and WebSocket state make the leak inevitable regardless of how you manage other tabs. Desktop Word starts fresh on each save rather than maintaining a continuously growing JS heap.

Collaborative documents with 3+ simultaneous editors. Each active co-author adds a collaboration channel in Office 365’s WebSocket layer. The memory cost scales with co-authoring activity. The desktop app handles this more efficiently.

For quick edits, short documents, and solo work on moderate-length files, Office 365 in Chrome works well. The memory problem only becomes significant after 30–60 minutes of continuous editing.

Technical Background

Chrome’s multi-process architecture assigns each tab its own renderer process with a separate V8 heap. When a tab is closed, the renderer is terminated and the OS reclaims the memory. The memory leak with Office 365 is not a traditional leak in the software engineering sense — it is a GC deferral pattern. V8 schedules garbage collection based on allocation rate and available memory pressure. For long-lived SPAs that allocate steadily and rarely trigger hard GC runs, the heap grows until it either hits physical limits or the GC finally triggers a major collection.

Microsoft’s Office team has made incremental improvements to how Office 365 apps schedule their own internal cleanup (Web Workers, IndexedDB cleanup, and stale WebSocket pruning), but this is an ongoing engineering problem with no complete solution while Office 365 remains a browser-hosted SPA.

The fan noise that users report during document editing is typically the CPU running V8’s GC major collection — a scan of the entire live heap to identify collectible objects. On large heaps (2+ GB), this is a computationally significant operation and it runs on the main thread, causing the brief UI stutter users notice while typing.

For broader Chrome memory management, see Fix Chrome High Memory Usage and Fix Chrome Memory Leaks on Windows 11.

If you’re editing a Word Online document right now and your fan is spinning: close and reopen the tab to reset the heap immediately.

If you regularly edit large documents: whitelist office.com in SuperchargePerformance and let tab suspension handle everything else automatically.

If you hit 2 GB+ consistently regardless of other tab count: switch to the Word desktop app for that document. The browser version is not designed for it.