Deep work timer: 90-minute focus blocks

A free deep work timer for your laptop or desktop browser: 90 minutes on one hard task, then a 15-minute break. Press play and brown noise plays in full, no account needed.

  • Runs in your browser on Windows, Mac or Linux: nothing to install, no account needed.
  • Sound is optional: brown noise plays in full for free, or turn the volume slider down for a silent timer.
  • When the 90 minutes are up, a two-note chime plays (and a desktop notification, if you allow it), then a 15-minute break starts on its own (30 minutes after every fourth block).

Ninety minutes on one demanding task, then fifteen off. Close the chat apps, write down the task, phone in another room, press play.

The timer runs on your laptop.

Send yourself this page and open it on your laptop. This is what it looks like there.

The real timer on a laptop: pick a sound, press Start, the block counts down. No sound in this clip.

What deep work needs

Cal Newport's Deep Work describes it as focused, distraction-free work on something cognitively demanding: writing, coding, analysis, research. It needs long, protected stretches, because hard problems take a while to load into your head and every interruption sends you back to the start. Ninety minutes is long enough to get properly into the problem and short enough to protect from meetings.

How to use the 90 minutes

Decide the task before you press play and write it down; deciding mid-block is how the block gets lost. Keep one window open for the work and this tab for the timer. When attention dips, and it will, stay with the task in a lighter way rather than switching. One or two blocks a day is a lot of deep work. How much is realistic is covered in how many hours a day you can really focus. If 90 minutes is too long today, the 52/17 timer is a good middle step.

Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central Publishing.

Pick a time and defend it

Deep work tends to fail in the calendar before it fails at the desk. Book the block as a real appointment, ideally at the same hour each day, and decline what collides with it. A set slot also removes the daily decision about when to begin.

A programmer's morning

  • 8:30: write down the bug or feature and the test that will prove it done.
  • 8:35–10:05: the block, chat closed, notifications off.
  • 10:05–10:20: walk.
  • 10:20: code review and messages, in shallow mode.

Measuring it honestly

Count hours of protected work per week in the session log, and leave out everything that was merely busy. A rising count over a month says more than how any single day felt. Kiri has no site blocking, so if you need that you would pair it with a separate blocker.

Who should not start here

On-call staff and anyone whose role depends on quick replies may get nothing but frustration from a 90-minute silence. Agree a shorter window with your team, or try the 52/17 cycle.

Questions

How long should a deep work session be?
Many people use 60 to 90 minutes. Ninety gives time to get into a hard problem; if that is too long at first, start with 50 or 52 minutes and build up.
How many hours of deep work a day is realistic?
For most people, two to four hours of real deep work is a full day. One or two 90-minute blocks is a good target.
Is the deep work timer free?
Yes. The timer needs no account, and brown noise plays in full without one. It runs in a desktop browser, not on phones.
What is the difference between deep work and a Pomodoro?
Pomodoro uses short fixed rounds and suits starting and steady tasks. Deep work usually means longer protected stretches on one demanding problem.