Hubstaff Idle Time: What Happens When You Stop Moving

Hubstaff flags a stretch as idle when it sees no mouse or keyboard input for longer than a threshold your organization sets. When that happens you may get a prompt asking whether you were working, and your answer decides whether that time stays on your timesheet.

The prompt reads like an accusation, which is why it makes people uncomfortable. Mechanically it is much duller than it feels: a counter hit a number, and the software is asking what to do with the result. This guide covers what triggers it, what each answer does, and what stops running when you pause.

What counts as idle in Hubstaff?

A continuous run of seconds with zero mouse and keyboard input. Once that run exceeds the configured idle threshold, the tracker marks the stretch as idle time.

The threshold is set by the organization owner and commonly sits in the range of a few minutes. There is no universal value, which is why one person's tracker prompts after five minutes and another's after ten.

Idle detection uses the same per-second input check that produces your activity percentage. It is not a separate sensor. A run of inactive seconds long enough to cross a threshold becomes idle time, and shorter runs simply lower your percentage. The underlying mechanic is covered in how Hubstaff activity tracking works.

The 'were you working?' prompt explained

When idle time is detected, Hubstaff can show a dialog asking whether to keep or discard that period. Whether the prompt appears at all, and what options it offers, depends on the organization's settings.

There is a genuinely useful implication in the second row. Discarding idle time usually improves your activity percentage, because the inactive seconds are removed from the calculation rather than counted as zeros. Keeping a 30-minute idle block drags the day's average down considerably.

So the honest answer and the favourable answer often point the same way. If you were genuinely away, discarding is both accurate and better for your number.

When you were working but got flagged anyway

This is the frustrating case, and it is common. The prompt fires because input stopped, and input stops during plenty of real work.

• •A long video call where you were listening rather than typing
• •Reading a specification, contract, or long document on screen
• •Watching a colleague's screen share or a training video
• •Thinking through a problem before writing anything
• •Waiting on a long build, render, upload, or query
• •Working on paper, a whiteboard, or a second device

In these cases keeping the time is the accurate answer, and it is worth doing even though it lowers the percentage. A timesheet that reflects reality is more defensible than a good-looking number, and if the pattern repeats it is a reason to talk to your manager about how the metric fits your role.

Does Hubstaff track anything when the timer is paused?

No. When the timer is paused or stopped, Hubstaff records no time, takes no screenshots, calculates no activity, and logs no apps or URLs. Tracking is driven by the timer, not by the app being installed.

This is the single most reassuring fact in this whole topic and the one people most often disbelieve. The desktop app continues running as a process so it can present the timer interface, but a running process is not a running tracker.

The same applies to being signed out or having quit the app entirely. More detail on what the app collects in each state is in does Hubstaff record your screen.

Does Hubstaff take screenshots when paused?

No. Screenshot capture is tied to tracked time, so pausing the timer stops it immediately. There is no delayed capture that fires after you pause.

One thing that does cause confusion here: a screenshot taken shortly before you paused may finish uploading after the pause. Seeing an upload indicator after pausing does not mean a new capture happened. Full detail is in our screenshot guide.

Does idle time affect your activity percentage?

It depends entirely on whether you keep it. Kept idle time counts as inactive seconds in the calculation. Discarded idle time is removed from the calculation altogether.

The difference is larger than most people expect. Consider an eight-hour day that would otherwise sit at 60 percent, with one 40-minute idle stretch in the middle of it.

So a single long idle block kept across a day costs several percentage points, and repeated across a week it is the difference between a normal-looking record and one that invites questions. What counts as normal by role is in Hubstaff activity levels explained.

The 'no activity' warning

Some organizations enable a warning that appears when the tracker has seen no input for a while, separate from the keep-or-discard prompt. It is a nudge rather than an action, and it exists mostly to catch the case where someone forgot to stop the timer.

Forgetting to stop the timer is genuinely the most common cause of a bad activity day. An hour of tracked lunch at zero percent does more damage to a daily average than most people realise, and it is entirely avoidable.

Practical habits that avoid idle problems

1. 1Stop the timer for real breaks. It is honest and it protects your average.
2. 2During calls, take notes in a document rather than listening passively. Typing is input.
3. 3When reading on screen, scroll as you go instead of leaving the page still.
4. 4If a long build or render is running, stop the timer or switch to another tracked task.
5. 5Answer the idle prompt truthfully rather than defaulting to whichever option looks better.

The realistic ranges these habits produce, by role, are in what is a good Hubstaff activity level.

Where Ghost Mode fits

Ghost Mode generates natural mouse movement, window focus changes, and keystroke timing during input-free stretches, which means the idle threshold is not crossed during work that genuinely involves little typing. That addresses the reading and call cases described above.

We want to be plain about the boundary. It affects the input signal, and therefore idle detection and the activity percentage. It does not affect screenshots, app logs, or URL logs. It is also not a substitute for stopping the timer when you are actually away, which remains the right thing to do. Setup details are in the FAQ.