Hubstaff idle timeout: the exact timers, explained

Idle time is not the same as low activity

These two words get used interchangeably, and confusing them is the single biggest source of anxiety about Hubstaff. Low activity means the tracker saw input during a 10-minute interval, just not much of it — 30% instead of 70%. Idle means it saw nothing at all for a sustained stretch: no keystroke, no mouse move, no click, no scroll. Low activity is a number sitting on an otherwise complete timesheet; idle is a hole in the timesheet where hours should be.

That distinction matters because the two are handled completely differently. A low percentage still counts as tracked, billable time — the interval is there, it just scored quietly. Idle time, by contrast, is usually removed from the record entirely. So a research-heavy afternoon that scores 25% is still a paid afternoon, while forty silent minutes reading a long document off-screen can vanish from the day altogether.

How the idle timer actually trips

Hubstaff watches for mouse and keyboard input the same way it does for the activity percentage — it is looking for events, not content. The idle timer is simply a countdown that resets to zero every time any input arrives. As long as you touch the mouse or keyboard inside the threshold window, the timer never fires. The moment the machine goes completely silent for longer than the configured period, that stretch gets flagged as idle.

The key word is completely. A single event anywhere in the window keeps you active — one arrow key, one small mouse nudge, one scroll of a page. This is also why real work rarely trips the timer during hands-on tasks and almost always trips it during the quiet ones: reading a spec, watching a recorded call, or thinking through a bug produces no input for minutes at a time, which is exactly the pattern the timer is built to catch.

• Any keystroke resets the timer — including navigation keys.
• Mouse movement, clicks and scrolling all count as input.
• Only total silence across the whole window flags the stretch as idle.

Who sets the timer — and why there is no single number

There is no universal Hubstaff idle timeout, and any article quoting one exact figure is guessing. The threshold lives in organization settings, and an admin chooses how long the silence has to run before the timer trips. Different teams land on very different values depending on the kind of work they track, so the honest answer to "what is the idle timeout" is always: ask whoever manages your organization.

Alongside the threshold itself, admins control the surrounding behaviour — whether you get a prompt on return, whether the timer can stop tracking on its own after a long silence, and how idle minutes are treated once they are detected. None of these are yours to set on a managed account, which is why understanding them matters more than trying to change them.

• The idle threshold — measured in minutes, but fully configurable.
• Whether a keep-or-discard prompt appears when you come back.
• Whether tracking stops itself automatically after a long silence.

The keep-or-discard prompt on your return

On many configurations, when you come back to a machine that went idle, Hubstaff shows a prompt asking what to do with the silent stretch: keep it as worked time or discard it. If the setting is on, this is your one chance to account for time the tracker could not see — the two hours you spent reading printed documents, or a call taken away from the desk.

The catch is that an unanswered prompt usually defaults to discarding the time. If you step away, the machine idles, and you never return to that session — you shut the laptop, or the day ends — those minutes are quietly dropped. This is the most common way honest hours disappear: not because anyone judged them, but because nobody was there to click "keep".

What happens to the minutes it takes back

Idle minutes are not billable. Once a stretch is flagged and discarded, Hubstaff removes it from the timesheet rather than recording it as zero-percent activity — so the effect is on your hours, not your activity percentage. A day that genuinely felt like eight hours at the desk can post as seven, and the difference is exactly the quiet time the tracker could not attribute to input.

For salaried staff this is mostly a reporting quirk; for anyone paid or invoiced by tracked time it is real money. The way to protect against it is not to fight the metric but to see it early: your own timeline shows where the gaps fell, and a discarded stretch that lines up with a two-hour review is easy to explain the moment someone can see the shape of the day.

Why a gap reads differently than a low number

To a manager scanning the day, a low activity percentage and an idle gap send opposite signals. A dip to 40% during an afternoon of reading looks like ordinary knowledge work — the interval is present, the screenshots show a real screen, the story holds together. A blank stretch with no input and a frozen screen behind it reads as absence, and absence is what draws a second look.

Occasional short gaps are invisible, because everyone reads, takes calls, and steps away — that texture is what a normal day looks like. What stands out is a repeated hole: the same forty-minute blank every afternoon becomes a pattern, and patterns are what managers notice. The goal is not a perfect line but an honest one, without holes that misrepresent time you actually spent working.

How to handle idle time honestly

The first move is to open your own report before anyone else does and read it by its shape. Find where the day went idle, check whether those stretches line up with meetings, reading, or time away from the desk, and use the keep-or-discard prompt to account for real work the tracker could not see. Understanding the timer is what lets you talk about a quiet day on your terms instead of apologising for a gap you did not understand.

It also helps to know the difference between the timers you can influence and the ones you cannot. Keeping the screen awake with a display-sleep setting does nothing for idle detection, because the idle timer measures input, not the screen — a screen can stay lit for hours while the input log shows total silence. The only thing that keeps a session out of idle is genuine input arriving inside the window.

Where Reaction fits

Reaction sits in one narrow place: the stretches when you step away from the keyboard but the session should stay alive — the coffee, the stretch, the school run, the long read on a second screen. As an anti-idle presence app it keeps a natural, human-like level of input within a range you set — varied cursor motion, a living keyboard rhythm, occasional scrolling and window switches — so a normal break does not turn into a discarded idle gap. It starts only when the computer is genuinely idle and steps aside the instant you touch the mouse.

What it does not do is make low-input work look like high-input work while you are actually at the desk doing it — that is a limit of the metric, not a feature. Unlike a plain mouse jiggler, which repeats one motion and leaves you chained to the desk, Reaction only fills the silence while you are away. Use it within your agreements with your employer; keeping an idle session alive during a genuine break is very different from claiming time you did not work.