Calculators & Quizzes
Estimate how many hours of reading your browser is quietly asking future-you to finish.
Runs entirely in your browser. Nothing leaves your device.
How it works
- Enter your total open tabs.
- Estimate what percentage are being kept as "read later" reminders.
- Choose an average reading time from 3 to 15 minutes per tab.
- The calculator converts that backlog into hours, equivalents, and a payoff plan.
Open tabs are a quiet to-do list
Tab debt is the pile of future reading, deciding, checking, comparing, and remembering stored in your browser. It is not a moral failure. It is what happens when open tabs become the easiest place to keep tasks visible. Carnegie Mellon tab research describes this pattern directly: tabs become an external to-do list, and sunk cost makes closing them feel like throwing away effort.
This calculator uses three inputs because not every open tab is debt. Some tabs are active work. Some are reference material. Some are parked because you might want them someday. The default assumes 40% of tabs are read-later tabs and 7 minutes per read, then converts that into hours. Change those numbers and the emotional shape of the backlog becomes much clearer.
The recommended move is refinance, not panic. Save the read-later set into a named group, close it, and schedule a real reading block. That turns a nagging strip of tiny tabs into a deliberate backlog you can choose to revisit.
Frequently Asked Questions
Is tab debt real?
It is not a formal financial or clinical term, but it describes a real browser pattern. CMU tab research found that tabs often act as an external to-do list, and sunk cost makes people keep pages open because they already spent effort finding them. The calculator turns that vague pressure into estimated reading time.
Why does the calculator default to 7 minutes per tab?
Seven minutes is a practical midpoint for skimming or reading an article, support thread, product page, or research source. The slider runs from 3 to 15 minutes because some tabs are quick decisions and others are deep reads. Adjust it to match the kind of tabs you actually keep open.
What's actually wrong with keeping read-later tabs open?
The cost is attention, memory, and fragility. Open tabs add visual noise, consume RAM, and make crash recovery more stressful. If the page is not needed right now, saving it somewhere restorable is usually better than keeping it live.
What's the best way to triage 100 open tabs?
First, snapshot the full session so cleanup is reversible. Then sort tabs into active today, read later, project reference, and duplicates. Close duplicates immediately, move read-later tabs into one named group, and keep only the active-today set open.