Mouse Jiggler FAQ

Yes, for most users. Teams Desktop monitors OS-level idle state and screen-lock status. KeepAwake's Wake Lock API prevents the screen from dimming and the OS from registering as idle. The Picture-in-Picture video keeps the display active even when the browser is minimized. Together, these keep Teams showing Available. Teams Web additionally benefits from browser-level activity detection.

Use this combination for maximum reliability: (1) Open KeepAwake in Chrome or Edge. (2) Click Start Jiggler. (3) Click Allow when prompted for Picture-in-Picture. (4) If using Teams Web, enable "Keep my current status when I'm active outside of Teams on the web" under Teams Settings → Notifications & Activity → Presence. This is the most reliable setup available from a browser.

Yes. Slack uses the same OS idle detection mechanism as Teams. By preventing the OS from registering as idle (via Wake Lock and PiP), your Slack status stays Active. This works for both the Slack desktop app and Slack Web.

Work through this checklist:

1. Use Chrome or Edge — these support Wake Lock API. Firefox does not yet.
2. Click Allow for Picture-in-Picture — this is the single most impactful permission.
3. Teams Web users: enable "Keep my current status when active outside Teams" in Settings → Notifications → Presence.
4. Check Windows Power Settings — set Display and Sleep to "Never" manually.
5. Corporate Group Policy: If IT has forced screen lock at the OS level regardless of browser activity, a browser tool cannot override this — ask IT to adjust the idle lock timeout.

A mouse jiggler is a tool that simulates activity to prevent your computer from detecting an idle state — keeping your screen on, your screensaver from activating, and your communication platform status showing as active. An online browser mouse jiggler does this using browser APIs with no download. KeepAwake uses 5 simultaneous techniques for maximum reliability.

Yes — and a better one for most people. PowerShell mouse jiggler scripts require script execution permissions, admin rights on many corporate devices, and technical knowledge to set up. They're often blocked by corporate PowerShell execution policies. KeepAwake requires only a browser tab. No permissions, no technical knowledge, not blockable by PowerShell policy. See the full comparison →

Completely free. No premium tier, no sign-up, no email required. KeepAwake is supported by non-intrusive display advertising shown in page margins. Your jiggler keeps running regardless of whether you see or interact with any ads.

KeepAwake installs nothing and appears only as a browser tab. It won't show up in Windows Task Manager or macOS Activity Monitor as a separate application. Standard idle-based and screen-lock monitoring won't detect it. Advanced enterprise monitoring tools (Teramind, ActivTrak) that track keystroke frequency or active application window focus operate at a different level — no browser tool can fool these.

Usually yes. KeepAwake is just a browser tab — corporate endpoint security tools rarely restrict websites the way they restrict installed software. However, if your company uses Group Policy to force screen lock at the OS level, that policy overrides browser-level wake locks. Check with IT if unsure.

Yes. Wake Lock API operates at OS level, independent of browser visibility. Picture-in-Picture creates an OS-level floating video window that persists even with the browser minimized. The Web Worker heartbeat is immune to browser tab throttling. The tab must stay open — just minimize it, don't close it.

Canvas animation runs inside the browser's rendering thread — it keeps the browser active but doesn't directly signal the OS. Picture-in-Picture is managed at the OS display compositor level. The OS sees a video playing and suppresses all idle timers — the same ones Teams monitors. PiP is also the only technique that reliably works when the browser window is fully minimized.

Chrome 84+: Full support — Wake Lock + PiP + Audio + Worker + Canvas
Edge 84+: Full support — same as Chrome
Firefox: No Wake Lock yet — PiP + Audio + Worker + Canvas (still effective)
Safari 16.4+: Partial PiP + Canvas + Audio
Chrome Android: Wake Lock + Audio + Worker + Canvas
Safari iOS: Canvas + Audio only

For the most reliable Teams-green experience, use Chrome or Edge on a desktop computer.

The techniques themselves use negligible CPU — under 0.1% on modern hardware. The main battery impact is simply that your screen stays on instead of dimming, which is the entire purpose. If you're plugged in, this is irrelevant. On battery, expect similar drain to having a browser tab with a paused video open.

All techniques stop immediately and cleanly. The Wake Lock is released back to the OS. PiP exits. The AudioContext is closed. The Web Worker is terminated. Your computer returns to its normal idle detection behavior within seconds.