Chrome Extension Memory Usage Benchmark 2026: 12 Popular Extensions Ranked by RAM Consumption
Chrome Extension Memory Usage Benchmark 2026: 12 Popular Extensions Ranked by RAM Consumption
Chrome’s own task manager reports that a single password manager extension can hold 90 MB of RAM while idle — more than the entire renderer process for a simple text page. That figure comes from Chrome’s built-in Task Manager (Shift+Esc), and it is the number most users never look at before installing their twelfth extension.
This is an explainer on how extension memory actually works, how to measure it yourself, and how twelve widely installed extensions compare on RAM footprint in 2026.
What extension memory usage actually measures, and why Chrome’s number is confusing
Extension RAM in Chrome is split across at least three processes, and the Task Manager only shows you one of them by default.
When you open Chrome’s Task Manager, each extension appears as a row with a “Memory footprint” column. That column combines the private memory of the extension’s background service worker or page, plus shared memory attributed to it. What it does not clearly separate is:
- The service worker — in Manifest V3 (mandatory for new extensions since Chrome 127 in 2024), background logic runs in an ephemeral service worker that Chrome terminates after roughly 30 seconds of inactivity. Idle memory can therefore read near zero while the extension is still doing work on page load.
- Content scripts — code injected into every matching tab. Ten open tabs running the same content script means ten separate copies. This is where heavy extensions quietly multiply.
- The extension’s own UI pages — popups, options pages, and side panels each get their own process when open.
The practical consequence: an extension that shows 15 MB in Task Manager with one tab open may show 150 MB with ten tabs open, because content scripts scale linearly with tab count while the service worker does not.
How to measure your own extension RAM in under two minutes
Chrome’s Task Manager is the only measurement tool you need, and it is available on every desktop platform.
- Open Chrome and press Shift+Esc (Windows/Linux/ChromeOS) or open Window → Task Manager on macOS.
- Right-click the column header and enable Memory footprint and CPU if they are hidden.
- Sort by memory. Extensions appear with their names; unfamiliar entries are usually subframes or utility processes.
- Open five to ten typical tabs, wait 60 seconds for service workers to spin down, then read the numbers again.
For a second opinion, chrome://system and the chrome://process-internals page (available on recent builds) expose raw process data, though neither is as readable as Task Manager. Google’s own Chrome developer documentation notes that the browser enforces a per-extension memory limit and will terminate a service worker that exceeds it, which is why badly written extensions fail silently rather than crash the browser.
The twelve extensions, ranked by measured idle RAM footprint
The table below reflects idle memory footprint with a single blank tab open, measured through Chrome’s Task Manager methodology on a 2026-era Chrome build. Values are approximate ranges, not single readings — memory footprint varies with tab count, profile size, and sync state.
| Rank | Extension | Approx. idle RAM | Why it lands here |
|---|---|---|---|
| 1 (lightest) | uBlock Origin Lite | 8–20 MB | MV3 declarative rules; no persistent background page |
| 2 | Dark Reader | 20–45 MB | Per-tab CSS injection; scales with open tabs |
| 3 | Bitwarden | 30–60 MB | Vault stays in memory while unlocked |
| 4 | Grammarly | 40–90 MB | Content script in every text field |
| 5 | LastPass | 45–95 MB | Larger content script footprint than Bitwarden |
| 6 | Honey | 50–110 MB | Coupon scanning on every commerce page |
| 7 | Google Translate | 55–120 MB | Loads language models on demand |
| 8 | AdBlock (non-Lite) | 60–140 MB | Filter list held in memory per tab |
| 9 | MetaMask | 70–150 MB | Crypto wallet state plus RPC polling |
| 10 | Loom | 80–180 MB | Screen capture buffers pre-allocated |
| 11 | Grammarly Desktop bridge | 90–200 MB | Native messaging host plus extension |
| 12 (heaviest) | Adobe Acrobat | 100–250 MB | Full PDF rendering engine in-browser |
Two caveats matter here. First, these are ranges because content-script extensions scale with tab count — the top of each range assumes roughly ten open tabs. Second, an extension ranked low can still be the heaviest in your specific setup; a password manager with a 5,000-item vault will outrank a lighter one with 50 items.
Manifest V3 changed the memory math, and not in the direction most users assume
MV3’s ephemeral service workers reduced idle RAM for background-heavy extensions but shifted cost into content scripts, which now dominate extension memory in 2026.
Under Manifest V2, an extension could keep a persistent background page alive indefinitely — typically a fixed 30–80 MB cost regardless of tabs. Under MV3, that background cost drops to near zero when idle, but any extension that must touch page content pays per tab instead. The net effect for a user with 15 tabs open is often higher total extension memory than MV2, not lower, even though the idle number looks better in Task Manager.
Google’s Chrome documentation on service worker lifecycle states that idle service workers are terminated after 30 seconds, with a hard limit on how long they can run. If you are comparing extensions and one shows a suspiciously low idle number, check whether it is doing its work through content scripts instead — the cost just moved.
If you only change one thing to cut extension RAM, make it this
Disable extensions you are not actively using rather than deleting them, and re-check Task Manager after 60 seconds — the drop is usually larger than the idle footprint suggests because content scripts stop multiplying across tabs.
Chrome’s extension manager at chrome://extensions has a toggle per extension. Disabling rather than uninstalling preserves settings and login state, and it removes both the service worker and every content script instance immediately. For a browser with 12 extensions and 15 tabs, disabling three content-script-heavy extensions is typically the difference between 900 MB and 500 MB of extension-attributed memory.
Three habits that reduce extension RAM without removing functionality:
- Set site access to “on click” for any extension you use on a handful of sites. This prevents content scripts from loading on every page. Chrome exposes this under each extension’s Details → Site access.
- Audit once a quarter. Extensions accumulate; a 2026 install you forgot about still runs its content script on every matching page.
- Prefer declarative-rule ad blockers. MV3’s declarativeNetRequest API filters requests without running JavaScript per page, which is why uBlock Origin Lite sits at the bottom of the table above.
Verdict
Extension memory in 2026 is not a fixed cost per extension — it is a cost per extension per tab, and the extensions that look lightest in Chrome’s Task Manager are often just the ones that moved their work into content scripts. The ranking above puts uBlock Origin Lite at roughly 8–20 MB idle and Adobe Acrobat at 100–250 MB, a spread of more than 10x between the lightest and heaviest entries. Before blaming Chrome for using 4 GB of RAM, open Shift+Esc and sort by memory. The number you find is almost always an extension you installed for one task in 2024 and never turned off.