Deep Work Timer
Embed this timer
Copy and paste this snippet into your website or blog post. Free to use — please keep the credit link so others can find the timer.
Add to Home Screen
Tap Share in Safari, then choose "Add to Home Screen".
Common uses for a deep work timer
- Deep focus work blocks
- Writing sessions
- Research deep dives
- Coding without interruption
- Creative project time
Deep work — the ability to focus without distraction on a cognitively demanding task — is measured in quality hours, not total time. Research on elite performers across domains (chess, music, writing, programming) converges on a maximum of 4 hours of truly deep work per day. This 90-minute timer represents one full deep work block — the duration most consistently reported as sustainable for high-cognitive output without significant fatigue accumulation. A 5-minute warning alerts you to begin wrapping up your current thought before the session ends.
Cal Newport's deep work framework and K. Anders Ericsson's research on deliberate practice both identify the 90-minute block as optimal for sustained cognitive performance. This aligns with the ultradian rhythm — the 90-minute biological cycle that governs alertness and cognitive capacity. Working within natural 90-minute windows, then taking a genuine rest, produces more total output than grinding continuously through fatigue-degraded attention.
The cost is in the reload, not the interruption
A thirty-second interruption does not cost thirty seconds. Work that requires holding a structure in your head — a proof, a design, a long argument — has to rebuild that structure afterwards, and the rebuild is where the time goes.
That is the whole case for long uninterrupted blocks. It is not that focus is virtuous; it is that the reload is expensive and the only way to avoid paying it repeatedly is to not be interrupted repeatedly.
Three or four hours a day is the honest ceiling
Sustained deep work has a daily limit far below the working day, and accounts of people who do a lot of it converge on three to four hours as the realistic maximum sustained over months rather than days.
Planning six hours and achieving two is worse than planning three and achieving three, because the shortfall becomes a reason to abandon the structure rather than an accurate picture of capacity.
Decide what the block is for before it starts
A block with no defined output drifts into whatever was easiest to pick up, which is usually email dressed as work. Naming the deliverable — this block produces the first draft of that section — is what makes the time defensible.
It is also what lets you tell afterwards whether the block worked. A vague block always feels productive, and that feeling is uncorrelated with whether anything was finished.
Longer blocks suit work with an expensive reload. Shorter ones suit starting when you are avoiding something.
| Block | Break | Suits | Daily ceiling |
|---|---|---|---|
| 25 min | 5 min | Starting, avoided tasks | Many |
| 50 min | 10 min | General focused work | 4-5 blocks |
| 52 min | 17 min | Deep work with a warm-up | 3-4 blocks |
| 90 min | 20 min | Long analytical work | 3 blocks |
| 120 min | 30 min | Rare, single-task days | 2 blocks |
| Shallow work | — | Email, review, admin | Fill the rest |
- Three to four hours a day is the realistic sustained ceiling, not a target to exceed.
- Name the deliverable before the block starts — a vague block always feels productive regardless of output.
Source: Block lengths and daily ceilings are widely reported practice rather than a single published finding
Sources
- Block lengths and daily ceilings are widely reported practice rather than a single published finding , TheTimerLab — accessed 2026-07-28