Online Interval Timer vs an App: When a Browser Timer Is Enough and When It Stalls

You want to run 8 rounds of 40/20 tonight and you do not want to download anything for it. So you search "online interval timer", open the first result, type in your work and rest times and press start. It is free, it has no account, and for the first two minutes it is perfect.

Then you lock your phone to save battery, or the laptop dims, or you switch tabs to change the music. When you look back, the timer is a round behind, or it never beeped at all. Nothing is wrong with the site's maths. The browser simply stopped giving it time to run.

Why a web timer stalls when the tab sleeps

A browser has to protect your battery from thousands of open tabs, so it rations work in any tab you are not looking at. Chrome slows timers in background tabs to roughly once per second, and after a few minutes hidden it can cut them to about once per minute. Safari on iPhone goes further: once the screen locks or you switch apps, the page is usually suspended outright, with no JavaScript running and no sound playing.

For an interval timer that is fatal, because the whole job is to fire a cue at an exact second while you are not looking. A well-built web timer recalculates from the clock when it wakes up, so the countdown looks right again when you return. But the beep for "rest" that was due 40 seconds ago never played, and that missed cue is the one that mattered.

Some sites ask the browser to keep the screen awake while the timer runs, which helps a lot. It only holds while that tab stays in front, though. Switch tabs, open another app or press the side button, and the browser releases the lock and the throttling starts again.

When a browser timer is perfectly fine

There are setups where a web timer is the right call, and an app adds nothing:

• A laptop or TV you leave open and in front. If the tab is visible and the screen is set not to sleep, a browser timer is as accurate as anything else. Cast it to a garage TV and you have a big, readable clock for free.
• A one-off session. Trying Tabata for the first time, timing a single workout at a friend's place, or running a class from a borrowed laptop. Not having to install anything is the whole benefit.
• Simple, even intervals. One work time, one rest time, a round count. Most web timers handle that well. Where they get thin is prep phases, different work times across a ladder, or saving a workout to run again.

A good check before you rely on one: start it, switch to another tab for three minutes, and listen. If every cue still sounds on time, that site and browser combination is fine for a laptop session.

When you need an installed app

The moment the timer lives on your phone and the phone goes in a pocket, on the floor or face-down by the dumbbells, a browser tab is the wrong tool. Native apps can register a running workout with the operating system, so the cues keep firing with the screen locked, over your music, and through a quick switch to another app.

That is the gap Peak Interval is built for. A session keeps playing its audio cues with the phone locked, shows the current phase and countdown on the lock screen, and on Apple Watch taps your wrist at each transition so you do not need sound at all. You also save the workout once, with its prep phase and its rest lengths, instead of typing it in each time. If you are on iPhone, our iPhone interval timer checklist shows how to test any app for this in ten minutes, and the Android version covers battery managers that can kill a timer there too.

An app is also the only option for leaving the phone behind: a browser cannot run on your wrist, and an Apple Watch interval timer without your phone can.

How to choose in ten seconds

Ask where the timer will sit while you train. If it is on a screen that stays awake and in front of you the whole time, use a browser timer and save yourself the install. If it is on a phone that will lock, sit in a pocket, or share the screen with your music, use an app, because the browser will throttle the one thing you need it to do.

If you are not sure, run the three-minute background test above. It tells you more than any feature list.