The Tab Hoarder's Guide to Getting Control of Firefox
If you have 80+ tabs open and Firefox is using 4GB of RAM, you know the problem. The hard part isn't finding tools — it's building a system that doesn't collapse the next time you're in a research rabbit hole.
Why You Have Too Many Tabs (It's Not a Discipline Problem)
Tabs serve as a form of working memory. You open a tab because you intend to read it, return to it, or act on it. The problem isn't that you opened it — it's that there's no trusted system to catch those intentions when you're ready to close the tab.
Closing a tab feels like losing something. Until you have a system that reliably captures "I'll come back to this," you'll keep the tab open.
The solution isn't willpower — it's a capture system.
The Two Types of Open Tabs
Before deciding what tool to use, classify your open tabs:
1. Active context tabs — Things you're actively working on right now. These should stay open. It's normal to have 5-15 of these.
2. "I'll read this later" tabs — Articles, forum threads, documentation, videos. These are the hoard. They're not active work; they're deferred decisions.
Most tab management advice targets type 2 while leaving type 1 intact. That's correct — you need different systems for each.
For "Later" Tabs: Three Options
Option A: Close Them
Radical, but often correct. Most tabs you've had open for more than a week, you won't read. Ask: "If this tab disappeared right now, would I notice?" If no, close it.
The mental block: "But I might need it." You probably won't. And if you do, search history or Google will find it again faster than scrolling through 80 tabs.
Option B: Pocket or Bookmarks
Firefox has Pocket built in (save button in the address bar). It syncs across devices, lets you add tags, and has a reader mode.
Bookmarks work too — create a "To Read" folder. The problem: bookmark folders become cemeteries. Most bookmarks are never reopened.
Pocket slightly better because it shows article previews and has a "read" filter.
Option C: Named Sessions
For sets of tabs that belong together as a project or context — not just "read later" but "actively working on this area" — save them as a named session using Tab Manager & Session Saver.
A "session" captures the whole context: "Client A research", "weekend reading", "interview prep". You restore the whole context when you need it, and it's out of the way when you don't.
This is more than Pocket: it's for tabs you'll open again as a group, not individual articles.
For Active Work Tabs: Windows
Use browser windows to separate active contexts. Firefox window 1 = work project. Firefox window 2 = personal stuff. Cmd/Ctrl+Backtick to switch between windows.
This is simpler than tab groups (which Firefox doesn't have natively) and works without extensions.
A System That Actually Holds
Weekly tab review (5 minutes, Sunday):
- Any tabs open for 7+ days that aren't active work → close or save to Pocket
- Any "tab groups" (5+ tabs on the same project/topic) → save as a named session and close
- Active work tabs → leave open or put in their own window
The key: a weekly deadline creates accountability that "I'll handle this later" doesn't.
What Doesn't Work
Tab suspenders: Extensions that freeze tabs to save memory. They help with RAM but don't fix the underlying problem (too many tabs) — they just make it cheaper to have too many.
One-click "session savers" that auto-save everything: Too much noise. You want named, intentional sessions, not an automatic archive of every tab you ever had open.
Closing everything and starting fresh: Produces anxiety and you'll be back to 80 tabs within a week.
The Realistic Approach
You probably won't get to 5 tabs and never go back. A realistic target is keeping active-work tabs in reasonable range (under 20) and having a system that prevents the "read later" pile from overwhelming them.
Named sessions + weekly review gets you there. Everything else is optimization.
Top comments (0)