This page asks a narrow question and answers it with 6 inputs: open tabs right now (all windows), tab hygiene habits, browser windows and age of your oldest someday-tab. The output is one number, a browser memory usage score. Of those, tabs carries the largest weight, which is why small changes there shift the result more than anywhere else.
Anything under 25 reads as the settled case; the top band, bankrupt, begins where the pattern is consistent rather than occasional. The published weights are the whole model: tabs at +1 and findrate at -0.8. They are shown in the table below rather than hidden, so you can disagree with a specific number instead of the result as a whole. The model is a weighted sum passed through a sigmoid, which is what keeps the result inside 0–100 no matter how extreme one input gets. Tabs, windows and oldest age push the number up; hygiene and findrate pull it down.
The useful reading is the band, not the exact figure. Two results a few points apart describe the same situation; it is the 4 thresholds that carry the meaning. The more informative move is to change one input and watch how far the result travels. That sensitivity tells you which lever is real and which is noise, which is more actionable than any single reading. It is a model built on self-reported inputs, so it inherits whatever bias is in your own estimates, and it describes a pattern rather than predicting an outcome. Everything runs in your browser; nothing you enter is sent anywhere or stored.
The formula
w1·tabs- Open tabs right now (all windows) (weight +1)
w2·hygiene- Tab hygiene habits — bookmarks, read-later, weekly closes (weight -0.6)
w3·windows- Browser windows (weight +0.5)
w4·oldest age- Age of your oldest someday-tab — 0 = hours, 10 = a fossil over a year old (weight +0.7)
w5·findrate- When you need a tab, you find it… — 0 = never (open a duplicate), 10 = always (weight -0.8)
σ, μ- Sigmoid squash to 0–100, centered on typical values
How it works, step by step
- Rate each input honestly — the Browser Memory Usage score is only as good as your self-assessment.
- Watch the live score and note which factor the result panel names as your strongest driver.
- Read your band below — each range comes with a concrete recommended next step.
- Change one input to simulate a change in behavior and see how much the score moves — that sensitivity is the real insight.
- Re-take the assessment after a few weeks; trends across readings mean far more than any single score.
Worked examples
A low-signal scenario
With every input set well below typical — the quiet version of this situation — the model returns 36, landing in the “Cluttered” band. Your tabs map to live tasks and retrieval works — this is a working memory, not a warehouse. Exactly what browsers were designed for.
A high-signal scenario
Push the main drivers well above typical and the score rises to 69 — the “In debt” band. Your tab bar is a monument to intentions, taxing memory and attention while returning nothing. Bookmark-all into a dated folder and close everything — it preserves every intention while ending the daily tax.
How to read your score
Frequently asked questions
What does the Browser Memory Usage Calculator score represent?
It converts your tab situation into a debt figure — combining sheer count (log-scaled, since tab 80 hurts less than tab 8), how old and unretrievable the oldest tabs are, and whether you have any offsetting hygiene habits.
Is declaring tab bankruptcy safe?
Yes, if you bookmark-all into a dated folder before closing everything. In practice people reopen under 5% of bankrupted tabs — which reveals how few of those intentions were ever real.
Why do I keep opening duplicate tabs?
Because retrieval has failed: finding the existing tab costs more effort than opening a new one. Rising duplicates are the clearest signal you have crossed the write-only threshold.
How much memory do browser tabs really use?
Modern browsers average roughly 50–150MB per active tab, though they discard background tabs to save RAM. The catch: discarded tabs reload on click, so a huge tab bar feels sluggish even when memory is managed.
Why is closing tabs so hard?
Each tab is a stored intention, and closing it feels like abandoning that intention — a small loss your brain resists. The fix is relocation, not willpower: bookmarking moves the intention somewhere durable so closing costs nothing.
What is the write-only threshold?
The point where you keep adding tabs but stop retrieving them — you open a duplicate rather than hunt for the original. Past it, your tab bar is storage that only accepts deposits, and searching again beats looking again.