Ghost ModeGhost Mode
ยท7 min read

How Hubstaff Activity Tracking Actually Works (2026 Guide)

๐Ÿ“ŠActivity tracking

If your employer or client uses Hubstaff, you've probably noticed a small percentage next to each block of tracked time โ€” your 'activity level.' Most people assume it measures how hard they're working. It doesn't. It measures something far simpler, and understanding exactly what it counts changes how you think about the number entirely.

This guide breaks down the real mechanics of Hubstaff activity tracking in 2026 โ€” what it measures, how the percentage is calculated, what its screenshots actually capture, and the things it fundamentally cannot see.

What the activity percentage actually measures

Hubstaff's activity percentage is based on one thing: whether you moved your mouse or pressed a key during each second of tracked time. That's it. It is not a measure of productivity, focus, or output quality โ€” it's a measure of input frequency.

The tracker divides time into 10-minute windows (600 seconds). For each second in that window, it asks a single yes/no question: was there at least one mouse or keyboard event? If yes, that second counts as 'active.' The percentage you see is simply:

Activity % = (active seconds รท 600) ร— 100

So if 270 of the 600 seconds in a window had at least one input event, your activity level for that window is 45%. It doesn't matter whether you moved the mouse once or a hundred times in that second โ€” a single event makes the whole second count.

10-minute window600 secondsโ–  active secondActivity = 28 / 60 โ‰ˆ 46%
Each square is one tracked second. Only seconds with mouse or keyboard input count toward your activity percentage.

What counts as 'activity'

Only two categories of input register with the tracker:

  • โ€ขMouse activity โ€” movement, clicks, and scrolling all register as input events.
  • โ€ขKeyboard activity โ€” any keypress, including modifier keys, arrows, and shortcuts.

Notably, the content of what you type or click is never part of the percentage. Typing a single space registers exactly the same as writing a paragraph of code. The algorithm is deliberately content-blind at this layer โ€” it only sees that an input happened, not what it was.

What a 'normal' activity level looks like

Here's the part that surprises most people: a real human doing focused desk work rarely scores anywhere near 100%. Reading a document, watching a screen-share, thinking through a problem, or talking on a call all produce long stretches with zero mouse or keyboard input โ€” and those seconds count as inactive.

In practice, genuine knowledge work tends to land somewhere between 40% and 70% activity over a full day. A constant 95โ€“100% is actually unusual for humans and can look suspicious to a reviewer, because it implies non-stop input with no pauses to read or think.

What the screenshots capture

Alongside the activity percentage, Hubstaff can take periodic screenshots โ€” by default, a few times per 10-minute window, at randomized intervals so they can't be predicted. Depending on the employer's configuration, it may capture every connected monitor (you'll often see '3 screens' on a multi-display setup).

Screenshots are a visual record of what was on screen at that moment. They are separate from the activity percentage โ€” the percentage comes from input timing, while the screenshot is just an image. Some organizations blur screenshots or disable them entirely for privacy reasons.

Idle time and the away threshold

If the tracker detects no input for a sustained period, it flags the time as idle and may prompt you to confirm whether to keep or discard it. The exact idle threshold is configurable by the account owner, but the underlying logic is the same second-by-second input check โ€” sustained inactivity simply means a long run of inactive seconds.

What Hubstaff cannot see

Because the activity layer only measures input timing, there's a lot it has no visibility into:

  • โ€ขWhether the work you produced was good, relevant, or even real.
  • โ€ขTime spent reading, thinking, or on calls โ€” all of which look 'inactive.'
  • โ€ขWork done on a second device, on paper, or in a meeting away from the keyboard.
  • โ€ขThe difference between deliberate work and idle fidgeting โ€” both are just 'input events.'

This is the core limitation of input-based tracking: it confuses motion with productivity. The most valuable parts of many jobs โ€” planning, reviewing, problem-solving โ€” generate the least input.

Keeping a healthy, realistic activity level

Because the metric rewards consistent input rather than output, long reading or thinking sessions can unfairly drag your numbers down even when you're fully engaged. That's the problem tools like Ghost Mode are built to solve โ€” they generate natural, varied mouse and keyboard activity so that genuine work time (including the parts spent reading or thinking) isn't misread as idle.

The goal isn't a fake 100% โ€” that pattern is unnatural and easy to spot. The goal is a realistic, human-looking activity level that reflects the fact that you were actually at your desk and working, even during the quiet, input-free moments that input-based trackers penalize.

Want the full picture on compatibility, privacy, and setup? See the Ghost Mode FAQ โ€” or compare plans on the pricing page.

Hubstaff's activity percentage is a useful signal, but it's a narrow one: a second-by-second tally of whether your mouse or keyboard moved. Once you understand that it measures input, not effort, the number stops being mysterious โ€” and you can make sure it reflects the work you're genuinely doing.

Keep your activity level accurate

Ghost Mode simulates natural mouse and keyboard activity so genuine work time isn't misread as idle.