The Window Sprawl Calculator looks at one specific question inside digital clutter and attention management: what do your window sprawl actually add up to? Instead of a vague feeling, it converts the everyday signals you already notice — open tabs right now (all windows), same page open more than once?, anxiety about closing a tab, age of oldest someday-tab — into a single score you can track, compare and act on.
The model is built on open-loop cognition, task-switching research and the Zeigarnik effect on unfinished intentions, the same foundation as our flagship browser tab calculator. Each input is weighted by how strongly that factor predicts real outcomes in the research; the formula and every weight are published below, so you can see exactly why your score is what it is — and argue with it if you like.
Adjust the sliders to match your situation honestly and the score updates live, along with the strongest factors pushing it up or down. Like everything on Quirkulator, the computation runs entirely in your browser: nothing you enter is ever transmitted or stored.
The formula
w1·tabs- Open tabs right now (all windows) (weight +1)
w2·dupes- Same page open more than once? — 10 = definitely, several times (weight +0.5)
w3·close anxiety- Anxiety about closing a tab — "but I’ll need it!" (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 Window Sprawl 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 24, landing in the “Tidy” 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 61 — 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 Window Sprawl 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.
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 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.
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.
Is my browsing data collected?
No — you enter counts, not URLs, and all computation is local to your browser.