Opening several browser tabs can make your system start struggling after a certain point. You may naturally respond by closing what you feel are the heaviest tabs, in hopes that the system settles down. Firefox has a quieter built-in solution that you may not be aware of.
This feature unloads inactive tabs to free memory without discarding them. Once you start using it, you’ll be freeing memory before Firefox has to do the same thing automatically under memory pressure.
Firefox doesn’t simply unload your biggest tab
It starts with tabs you’ve ignored the longest
Last week on my Firefox browser, I opened about:unloads in the address bar. I had an ordinary number of tabs open: my Gmail, which I hadn’t touched in hours; YouTube playing in the background; some sports websites; a few music streaming sites; a Google Doc I was typing in; and some websites I often visit for news stories.
What I expected to see at the top of the tab list were the YouTube and Docs tabs. I assumed these two tabs were doing the most work; however, neither featured even close to the top.
That made one thing clear: about:unloads lists tabs in the order Firefox would unload if it needed to start closing tabs to save itself. These don’t have to be the heaviest or most memory-intensive tabs. In fact, my heaviest tabs — YouTube and the music streaming tab — were at the bottom of the Priority column.
The factor deciding when Firefox unloads a tab isn’t simply how much memory it uses. With fewer tabs, Firefox primarily considers how recently you accessed each one, while larger tab collections trigger additional calculations that include estimated memory use.
At the top of the Priority column, I had a HowToGeek tab, simply because it was the one I had ignored the longest. It wasn’t the heaviest of the bunch. Ignoring a tab is a bigger red flag than the memory it actually consumes. Not all ignored tabs are cut off first. If a tab is playing media, using Picture-in-Picture, or involved in a WebRTC call, Firefox avoids unloading it. Pinned tabs are also given lower priority for unloading. Firefox’s priority list tries to prioritize unloading the safest tabs without accidentally ruining your work or interrupting something important.
Unloading isn’t closing
The tab survives; the page doesn’t
In Firefox 140 and later, when you right-click a tab, you’ll find an option called Unload Tab. I clicked it on the same HowToGeek tab, the one that was currently destined to unload first based on Firefox’s priority ranking. The only thing I physically noticed was that its favicon was greyed out.
When I clicked the greyed-out tab, Firefox reloaded the page from scratch just as if I had typed the address afresh. Unloading didn’t close the tab; it removed the page’s active resources while keeping the tab itself in place.
This is a distinction worth noting, especially when our browsing habits lead us to pile up tabs. If a research thread requires you to open several links, you don’t need them all active; you just want them all held. Unloading makes sense here.
If you are mid-task on a specific tab — a half-filled form, unsaved documents, etc. — unloading may reload the page and cause unsaved form data to be lost. I now save that unload button for my tabs that are just waiting.
From the about:unloads Firefox page, you see the exact order Firefox would unload tabs without ever consulting you. However, the unload option in the context menu allows you to unload a tab on the spot, without waiting for Firefox.
Firefox waits for memory pressure before unloading tabs
The manual option lets you do it before Firefox has to
Automatic tab unloading in the background isn’t a routine Firefox housekeeping. This activity only kicks in after a memory-pressure detector decides the computer is running low on available memory. In this case, it’s a reaction to a problem you’re most likely already feeling.
The manual button fills the gap. You don’t need to wait for Firefox to decide which tabs to unload. You usually feel the lag even before Firefox’s detectors kick in. It may present itself as a stutter in switching tabs or web apps using more gigabytes than you can explain.
about:unloads is useful because it shows which tabs Firefox considers safer to unload. Looking through this list before closing tabs helps you avoid closing tabs that may still have useful activity running.
Keep active work loaded and everything else can wait
Closing a page can feel too final, and most people would rather end up with so many browser windows they don’t want to touch. You can sidestep the fear by unloading, leaving the tab exactly where you want it while reducing the memory pressure it would otherwise cause.
I settled on a simple rule: all tabs I am using right now stay loaded, and all tabs I would need later stay unloaded. If all I need is the information from a tab, I bookmark and close it. I open several tabs, especially after segmenting with its native Container feature, but now I regulate memory pressure using the Unload feature.