Why You Have 80 Tabs Open (And Why That's Actually Fine)
You opened your browser this morning and saw the number in the corner: 47. Or 80. Or, somewhere on the spectrum, "two arrows because the count gave up."
You've felt the small jolt of guilt — I should really close some of these — followed by the small jolt of fear: but I'll lose them. Then you opened seven more tabs over the course of the day, because that's how the day went.
This piece is not going to tell you to close them. Most articles do, and most articles are missing what's actually happening. By the end you'll have a clearer picture of why your tab count climbs, why every "fix" you've tried hasn't stuck, and a calmer framing for what to do that doesn't involve declaring tab bankruptcy at 4pm on a Friday.
The thing nobody names: tabs are working memory
Cognitive psychologists who study browser behavior keep finding the same thing in their interviews. People with a lot of tabs open are not failing at organization. They're using the browser as an external thinking surface — what some researchers call "external memory" or "context scaffolding." The tabs hold the threads of a project, a research session, a comparison shop, a debugging trail. Closing them isn't tidying. It's deleting your notes.
Mental Floss, summarizing the multitasking research, puts it bluntly: people don't multitask, they "task switch," and tabs end up holding the breadcrumbs between switches. Fast Company called it "the twisted psychology of browser tabs" — a tug-of-war between not wanting to lose context and not wanting to feel cluttered. Researchers at Carnegie Mellon documenting tab-hoarding behavior described it as a coping strategy, not a moral failure.
The picture that emerges across all of those is consistent: the open tab is an unfinished thought. Your brain trusts it more than it trusts a bookmark. And it has a point.
Why "just close them" doesn't work
The most common advice is some version of "use bookmarks" or "set a hard limit of 9 tabs." If that worked, you'd be doing it. The reason it doesn't is structural, not motivational.
Bookmarks are a folder you never open. They're invisible by design — collapsed into a menu, sorted alphabetically, stripped of the spatial memory that helped you find the tab in the first place. When the cost of saving something is "I'll never see it again," your brain correctly votes to keep the tab.
Hard limits punish the actual workflow. A research session might legitimately need 30 tabs open for an afternoon. Forcing yourself to nine forces you to close things you'll re-search for later. You haven't tidied; you've just moved the cost from "tab clutter" to "Google clutter."
Closing without saving is loss aversion's worst nightmare. Loss aversion — losing things hurts roughly twice as much as gaining them feels good — is doing a lot of work here. Your brain isn't being dramatic. It's being a normal brain.
The advice doesn't fail because you lack discipline. It fails because it doesn't engage the actual job the tabs are doing.
Tab hoarding has a profile (and it's mostly knowledge work)
If you've ever Googled "am I a tab hoarder," you'll have seen the meme version of the answer: a checklist of self-diagnostic horrors. The honest version is calmer.
The people who keep many tabs open the longest tend to be:
- Researchers, designers, writers, devs — anyone whose work requires holding multiple sources in view at once.
- People who flip between several active projects within a day.
- Folks with ADHD or AuDHD profiles who use spatial / visual cues to anchor working memory. The Hacking Your ADHD podcast on this is generous, accurate, and worth a listen.
- Founders, PMs, and analysts running on "context-heavy" days where the next decision depends on something you saw earlier.
If that's you: your tab count is a side effect of doing real cognitive work, not a sign that you're disorganized. The thing to fix isn't the count — it's the medium.
A reframe: tabs are not the problem, what happens when you close the browser is
Watch yourself for one day. The friction isn't really when you have 80 tabs open. The friction is the moment your laptop reboots, or you accidentally Cmd+Q, or your browser updates overnight. That's when the system fails — not because you had too many tabs, but because the browser is the only thing holding the context, and the browser doesn't owe you anything.
A tab manager fixes the persistence gap, not the count gap. The point isn't to close everything; it's to make closing safe. When the cost of "save and close this 30-tab research session" drops to one click and the cost of "open it back up tomorrow" drops to one click, the tab count starts taking care of itself — not because you got more disciplined, but because there's nothing at stake anymore in the act of closing.
How Toby fits
Toby is the new tab page that makes saved tabs look like the actual things you saved them for. Each collection is a card-and-favicon row of the tabs you grouped together; opening one is one click. (See: apps/landing/src/pages/index.astro, apps/landing/src/pages/save-session.astro.)
The interaction we built the product around is Save Session: one click closes every tab in the current window and tucks them into a named collection. Open the browser tomorrow, and the collection is still there, on the new tab page, exactly the way you left it. (See: apps/landing/src/pages/save-session.astro.) That's what we mean when we say the brand promise is "It's okay, Toby has it now." — it's not a tagline, it's the literal interaction. (See: product/strategy/soul.md.)
The bet behind the design choices: visual recognition beats hidden hierarchy. You don't have to remember a folder name; you scan the new tab page and see the project you were working on. Bookmarks ask you to retrieve. Toby asks you to recognize. Your brain is much, much better at the second one.
We're not the right tool for everyone. If five tabs is your number, you don't need us. But if "too many" is the number you keep landing on — and you keep landing on it because that's what the work calls for — Toby is the place to set them down without losing them.
Practical steps that don't involve closing 70 tabs
If you only do one thing this week:
- Stop trying to lower the count. It's measuring the wrong thing.
- Identify your "context windows." Most people have two to five active themes (project A, client B, ongoing research, that recipe collection, side-project rabbit hole). The tabs cluster around these whether you've named them or not.
- Save one of those windows. Pick the most-cluttered one, give it a name, save the whole session, and close it. Notice — honestly — what you feel. If it's relief, you've found the medium your brain wanted.
- Repeat tomorrow with the next one. Don't try to reorganize everything in one afternoon. The relief is the signal.
- Treat the open tabs as live work. Once your saved sessions are stored, the open tabs you keep are by definition the ones you're using right now. The count drops because the medium changed, not because you forced it to.
That's it. No tab limit. No quarterly bankruptcy. No bookmarks folder you'll never reopen.
FAQ
Is having too many tabs open actually bad for my brain? The research is mixed. The evidence for performance cost is real but smaller than the headlines suggest — what hurts focus is attention residue (thinking about closed work while doing new work), not the visual presence of tabs themselves. The bigger cost is anxiety: feeling like you're losing track. That's the cost a tab manager actually addresses.
Is OneTab or a tab manager better than browser bookmarks? For temporary, project-shaped collections, yes. Bookmarks are designed for "permanent reference" links — your bank, your style guide, your timesheet. They were never built for the working-memory job most tab hoarders are doing. A tab manager handles the active work; bookmarks handle the long-term reference. Use both.
Why do I keep tabs open instead of just bookmarking the page? Because bookmarks disappear into a menu and tabs stay visible. Visibility is the feature. The fix isn't to bookmark more — it's to find a tool that keeps things visible without keeping the actual browser tab open.
How many tabs is "too many"? However many makes you anxious. The number isn't a productivity metric; it's an emotional one. If 47 feels fine, 47 is fine. If 12 feels stressful, 12 is your number. The point is having a place to put the rest.
Editor notes
Suggested internal links (verify they exist before publishing):
- Toby landing — natural anchor: "the new tab page" / "Toby"
- Save Session feature — natural anchor: "save the whole session" / "Save Session"
- Existing post: Workona Alternative — natural anchor: "if you've also looked at Workona"
- Existing post: Smart Strategies to Organize — natural anchor: "if you want practical organization tactics" (only if it lives at this URL)
Suggested distribution:
- X angle: "47 tabs is not a personality flaw. It's a research pattern. New post on what's actually going on when your tab count climbs — and a calmer way to handle it than just closing them. <link>"
- Reddit angle: r/productivity or r/ADHD — pitch as "Why 'just close your tabs' advice doesn't stick (and what does)"; do not link the blog directly in the body, leave it in profile / comments per subreddit rules.
- Hacker News: "Show HN" framing not applicable — this is essay content. "Ask HN: Do you treat browser tabs as working memory?" could be a discussion-style submission that links the post in the first comment.
SEO references (top SERP results reviewed when picking the angle):
- Fast Company — twisted psychology of browser tabs — 403 on programmatic fetch, but cited via SERP summary; sets the "psychology" framing the SERP expects.
- MaxFocus — psychology of tab hoarding — ~1200 words, three H2s, hard-recommends limits + bookmarks. We deliberately reject that recommendation set.
- Mental Floss — yes you have too many tabs open — ~850 words, no H2s, mainstream-consumer voice. We give better structure.
- Hacking Your ADHD — Digital Declutter — 2,400 words, cites Toby explicitly. We can lean into the AuDHD-shaped reader without claiming clinical authority.
- Workona — How to Fix The Problem of Too Many Tabs — ~900 words, leads with their product. Direct competitor on this query; we differentiate via the "tabs as memory" reframe instead of "close, organize, suspend".
- Carnegie Mellon — Overcoming Tab Overload — research summary; useful citation for credibility.
Voice fingerprint check: anchor lines drawn from product/strategy/soul.md ("It's okay, Toby has it now") and toby/x-strategy.md ("47 tabs is not a personality flaw"). Length: ~1,300 words. Reading level: conversational. No 🚀, no "supercharge", no "delve into", no "in the realm of".
Open questions / TODOs for the editor:
- Confirm the internal links above resolve to current canonical URLs on
gettoby.com— Astro routing may differ fromgettoby.com/blog/<filename>. - The "47 tabs" line is also queued as a standalone X post (
toby/x-content-pipeline.md, Post 1). Decide whether the blog drops the line or whether the X post links to the blog (preferred — gives the X post a click-through destination). - We claim "one click" save-session and recognition over retrieval; verify the current Save Session UI still matches that copy in
apps/extension/before publishing. Last verified ship date for save-session was extension v1.13.0 on 2026-04-14 pertoby/00-state-of-the-project.md. - Consider whether to mention pricing at all. Per
toby/00-state-of-the-project.mdthere's an unresolved $4.50 vs $6/$10 contradiction; safer to say nothing about price and let the landing page handle it. - The post does not include OneTab as a primary comparison even though OneTab is dormant and the SERP overlap is tempting. Decision: a separate OneTab Alternative post is queued in the pipeline for next cycle. Keep this one focused on the foundational reframe.
- Image hand-off: needs a hero showing a Toby new tab page with several named collections. Reuse the existing
~/assets/images/blog/...pattern from prior posts.