Why Firefox Is Using So Much Memory (and How to Fix It)
Firefox with 50 open tabs can use 3-5GB of RAM. Most "fix Firefox memory" articles suggest tweaks that make minimal difference. Here's what actually works.
What's Actually Using the Memory
Tabs: Each open tab holds the page's DOM, JavaScript state, images, and render data in memory. A simple news article: ~50MB. A complex web app (Gmail, Figma): 200-500MB. With 50 tabs, even modest sites add up fast.
Extensions: Extensions with "Access data on all sites" permission run on every page you load. Some are lightweight; some are not. Extensions that inject significant JS into every page (tab managers, page translators, productivity tools) can contribute 50-200MB each.
Media: Video and audio tabs are particularly heavy — they hold decoded media buffers in memory.
Firefox's own processes: Firefox splits itself into multiple processes (content processes, GPU process, extension process). The about:memory page shows the breakdown.
What Actually Helps
1. Close Tabs You're Not Actively Using
This is the biggest lever. Each closed tab frees its entire memory footprint immediately.
The objection: "But I need those tabs." If they're things you'll return to, save them. If they're "just in case," they're probably not worth the RAM.
For tabs you want to save: Tab Manager & Session Saver saves all open tabs as a named session. Close the group of tabs, restore the full set with one click when you need it. Sessions persist in browser.storage.local — no memory cost while closed.
This changes the trade-off: instead of keeping 40 tabs open (expensive) to avoid re-finding them, you save the session (free) and restore when needed.
2. Check about:memory
Go to about:memory in Firefox. Click "Measure" to get a breakdown.
The "Top memory consumers" section tells you what's actually using memory. Often it's one or two tabs or extensions that are outliers, not the browser itself.
3. Audit Your Extensions
Go to about:addons → each extension → "Run in Private Windows" and permissions.
Extensions that request broad permissions and inject JS into all pages are memory consumers. Disable extensions you don't actively use. You can keep them installed but disabled — they use near-zero memory when disabled.
4. Limit Content Processes (Low-RAM Systems)
In about:config, search for dom.ipc.processCount.
Firefox defaults to 8 content processes (fewer on low-RAM systems). Reducing this to 4 or 2 limits how many tabs can run in separate processes simultaneously, reducing total memory usage. Tradeoff: slightly more risk of a single tab crash affecting others.
On systems with 8GB+ RAM, leave this at default — the memory savings aren't worth the stability tradeoff.
5. Restart Firefox Periodically
JavaScript engines allocate memory that isn't always freed immediately. A fresh Firefox start recovers memory that accumulates over days of use. Firefox's session restore will reopen your tabs when you restart.
What Doesn't Help Much
Tab suspenders: Extensions that "suspend" inactive tabs to save memory. They work by discarding the rendered page and reloading it when you switch back. This does save memory on suspended tabs, but introduces reloading delays and can lose form state. Mozilla's own memory management already does partial version of this automatically.
Increasing RAM limit settings: Settings like javascript.options.mem.max and cache size settings have minimal real-world impact on typical browsing.
Running Firefox in "low memory mode": about:config browser.lowMemoryResponseMask — modifies how aggressively Firefox frees caches under pressure. Minor effect.
The Real Answer
Firefox's memory usage scales linearly with the number of active tabs. The only way to consistently reduce it is to have fewer active tabs. Everything else is optimization around the edges.
The systems approach: save contexts you're not actively working in, work from a smaller set of truly active tabs, and use a session manager to make that workflow comfortable rather than anxiety-inducing.
Top comments (0)