Multi-Monitor Screenshot Support: What Time Trackers Actually Capture

Most time trackers advertise "screenshots" without saying what happens when an employee has two monitors — and the answer differs enough between products to change what your evidence is worth. Some capture every connected display, some capture one, and the ones that capture everything disagree about whether you get several images or one. Here is what the vendors' own documentation says, quoted and linked, plus the design trade-off nobody puts on a feature page.

The three behaviors

Every screenshot tracker on a multi-monitor desk does one of three things:

All displays, separate images. One screenshot per monitor per interval. Full resolution on each, and every downstream count multiplies with the number of screens.
All displays, one composite. Every monitor stitched into a single stored image. One capture stays one review unit; resolution per display is reduced to keep the canvas manageable.
One display. Either a fixed primary monitor or one the employee selects. Everything else is off the record unless the tracker reports the hardware separately.

None of these is inherently correct. They trade legibility, review workload and storage against each other, and the right pick depends on whether you are gathering evidence for a billing dispute or just keeping an honest work log.

What the documentation actually says

Learn how SCREENish saves you money Time tracking with screenshots, honest reports and hands-off payroll. Free to try — no credit card. Start free →

Hubstaff — all displays, separate images. The support documentation is explicit: "Hubstaff will capture all active monitors connected to a computer when the user is tracking time." It also gives the arithmetic, which is the part worth internalizing: "With a dual monitor setup and a screenshot frequency of 1x, Hubstaff will capture 2 screenshots — one from each monitor every 10 minutes." Multiple images per interval are grouped in the interface behind a "View Screens" control, and for multi-monitor users the thumbnail shown by default is the second monitor's.

Time Doctor — all displays. Its screencasts documentation states that "Screencasts will capture and display content from all the connected monitors."

SCREENish — one display today, composite announced. The tracking app currently captures the monitor the employee selects. Separately, and this is the part that usually resolves the underlying question, it records a hardware profile per machine: operating system, CPU, RAM, cameras, and every attached display with its label, resolution and refresh rate, plus the total screen count. So a single-screen screenshot arrives alongside the fact that the machine has two displays. Multi-monitor capture is announced as a composite — all monitors in one image, each downscaled to at most 1920x1080, with whole-screen blur or no blur rather than smart blur — and it requires the latest beta tracking app. It is not available yet; the dashboard option is visible ahead of the app that implements it.

Everyone else — check before you assume. Rather than reproduce claims we have not verified from primary sources, the honest instruction is to search your vendor's own support site for "monitors" or "displays." Marketing pages rarely address it; support documentation almost always does. If the documentation is silent, that silence is itself informative, and a support ticket will settle it in a day.

The multiplication problem

Separate-image capture has a consequence that is obvious in hindsight and almost never mentioned at purchase: everything downstream multiplies by the number of screens.

Take a developer with three monitors and a tracker set to three screenshots per ten-minute block. That is nine images per block, roughly fifty-four per hour, over four hundred in an eight-hour day — for one person. Now consider what your team actually does with screenshots. If a manager reviews them, review time triples. If your workflow approves or rejects screenshots before payroll, decisions triple. Storage and bandwidth triple. Audit exports triple.

Teams usually discover this at the moment it hurts: a manager who was comfortably reviewing one employee's day gives up when three-monitor setups arrive, and the review step quietly degrades into rubber-stamping. Rubber-stamped approval is worse than no approval, because it looks like oversight in an audit while providing none.

This is the reasoning behind composite capture. Stitching every display into one image keeps one capture equal to one review unit, one approval decision, one deletion record, one row in the work log. The price is honest and specific: each display is downscaled, so a dense IDE or a spreadsheet on a 4K panel may not be readable at full fidelity. If reading fine text on every screen is the point of your screenshots, separate images are the better tool and the extra review load is the cost of that requirement.

Choosing by what you actually need

Choose all-monitor capture, separate images, if you need to read detail on every screen — client-billing disputes where the exact document matters, regulated environments requiring a complete record, or post-incident security review. Budget for the review load honestly, and consider whether approval workflows still make sense at that volume.

Choose composite capture if you want completeness without multiplying the work: you want to know what was on all the screens, at a glance, and you are willing to trade pixel-level legibility for a review process that stays humane.

Single-display capture is enough if your screenshots exist to confirm that work is happening and roughly what kind, rather than to serve as forensic evidence. This covers most teams honestly — especially paired with hardware inventory, so a single screenshot is never ambiguous about how much of the desk it represents.

One thing worth deciding deliberately: whether the employee chooses the captured display. Letting them choose is more respectful and it is how browser-based capture works regardless, since the Screen Capture API requires a user-mediated picker. Fixing it to the primary display is more predictable for evidence. Both are defensible; drifting into one without noticing is not.

What to write in your policy

Whatever you pick, the employee should be able to read it before the first screenshot rather than infer it from a gap. In the EU and UK this is not just courtesy — monitoring has to be transparent and proportionate, and the number of screens captured is exactly the sort of specific that a monitoring notice should state. Our GDPR-compliant monitoring checklist and the breakdown of what a monitoring notice must contain cover it in full.

Two sentences are enough: whether one screen or all screens are captured, and whether managers can see the display inventory. Ambiguity here is what produces the accusatory conversation later — from a manager who assumes concealment, or an employee who assumes surveillance well beyond what is happening.