How to Audit and Fix Firefox Memory Usage (Step-by-Step)

Firefox has a well-known problem: it uses more RAM than Chrome for equivalent workloads. The gap has closed significantly in recent versions, but it's still real, and it gets worse the more extensions you install.

Here's how to audit your Firefox memory usage and cut it down without sacrificing functionality.

Step 1: Baseline with about:memory

Open about:memory in Firefox. Click "Measure" under "Show memory reports." This generates a detailed breakdown.

Look at:

• Top-level total: Total memory Firefox is using right now
• Extensions: Filter the output for extension GC heaps — these show how much each extension is consuming

For most users, two or three extensions account for 70%+ of extension memory. Password managers and ad blockers tend to be heaviest (for good reason — they're doing real work on every page).

Step 2: about:performance for Per-Tab Costs

about:performance gives you real-time CPU and memory usage per tab and per extension.

Sort by memory to identify which tabs or extensions are consuming the most. A tab showing a complex SPA (web app) can easily use 200-400MB. A tab showing a static article should use under 50MB.

Step 3: The Extension Audit

Not all extensions are equal in memory cost. Common patterns:

High cost (by necessity):

• Password managers (must inject into every page)
• Content blockers (must parse every page's requests)
• Grammar checkers (must read every text field)

Medium cost:

• Tab managers (scale with number of open tabs)
• Screenshot tools

Low cost:

• New tab replacements (only run when a new tab opens)
• Color pickers (idle except when activated)
• Bookmark extensions (minimal injection)

Weather & Clock Dashboard falls in the low-cost category — it's a new tab replacement that only runs when you open a new tab, not on every page you visit. It requests no "access to all websites" permission. If you want the function (weather + world clocks in a new tab), this is a low-overhead way to get it.

Step 4: Unload Inactive Tabs

Firefox's built-in tab unloading (about:config → browser.tabs.unloadOnLowMemory) automatically suspends background tabs when RAM gets low. You can also force-unload individual tabs: right-click a tab → "Unload Tab."

For consistent results, install Tab Auto Unload (or similar) to automatically unload tabs you haven't visited in X minutes.

Step 5: The Real-World Impact

On my machine (16GB RAM, ~35 tabs open):

• Before audit: Firefox using ~3.8GB
• After removing 3 redundant extensions and unloading 15 tabs: ~2.1GB

That's 1.7GB freed without closing any tabs or losing any functionality.

The extensions I removed were:

1. A screenshots tool I replaced with Firefox's built-in screenshot (Shift+F1)
2. A tab session manager that duplicated Firefox's native session restore
3. A weather widget that ran on every page (replaced with Weather & Clock Dashboard, which is new-tab-only)

The Takeaway

Memory issues in Firefox are usually extension-driven, not Firefox itself. An audit takes 15 minutes and typically recovers significant RAM. about:memory and about:performance are the right starting points — both are built in, no extension needed.