# Keep Every Page Alive — full reference (keepalive.page) > A free, install-free browser tool that keeps an idle login warm with a timed reload, or holds an OSHA/SCORM training player in place without advancing the course. You enter a URL and an interval. Reload opens that site in a tab and reloads it on a timer so the site's idle (inactivity) timeout resets. Hold in place never navigates: it moves the pointer, focuses the page, may click a non-control surface, and keeps a video that was already playing. It does not click Next or Continue, submit a form, answer a quiz or attention check, or certify a course. This is the long-form companion to /llms.txt. It restates the condensed summary and adds the citable detail an answer engine is likely to quote: the two strategies, the honest limits, the named sites where refreshing is refused and why, the OSHA/SCORM vendor notes, and the recommended intervals. Everything here is accurate as of 2026 and was checked against the product's own code. Where a fact depends on a vendor, the vendor is named. Runs entirely client-side in any modern browser on any OS. No account, no ads, no cross-site tracking. The website records self-hosted, cookieless pageview counts (Plausible CE), plus the bare hostname of a public site when a user adds one — never the full address, never intranet or local addresses, and never on refreshes, and at most once per browser per site. The kept-page list itself stays on the user's device. The only server-side component for the public tool is a small counter that powers the on-site leaderboard: it stores a public hostname and a running total, nothing more (no visitor identifier, no IP address), and a hostname only surfaces once at least three distinct browsers have added it. ## What it does - Two strategies: Reload the tab (ordinary idle logins) and Hold in place (OSHA 10/30 and similar SCORM shells such as ClickSafety, CareerSafe, 360training, HSI). - Auto-refreshes a page you give it, on an interval you choose — or holds it without navigating. - Interval presets in ordinary minutes; an optional "prime stagger" mode uses the prime numbers from 17 to 887 seconds (primes rarely share factors, so multiple kept pages don't sync into simultaneous reloads); custom intervals accept any integer with units from seconds up to centuries. - Keeps any number of pages alive at once; each can be paused, refreshed or nudged immediately, re-timed, or released. - Fine tuning: ±15% interval jitter; hard refresh (cache-busting query parameter); a leash that stops a page after N refreshes or at a set time; opt-in desktop notification when a kept page stops being refreshable. - The tab title carries a live countdown and a warning mark if any kept page needs attention. - The kept-page list can be exported/imported as JSON, and links like https://keepalive.page/?url=example.com&every=10m arrive pre-filled. Hold can be preselected with ?strategy=hold. - A screen wake lock ("Keep screen awake") holds the display awake while pages are being kept alive. - An on-site leaderboard shows which public hostnames get kept alive most, tallied across everyone who uses the tool (hostname + count only, no visitor identifier), plus a local activity log, a per-watch nickname, and a one-click pause for every running watch at once. ## The two strategies, precisely Reload the tab. Each reload is a real HTTP request, so a server-side idle-inactivity timer — measured from the last request the server received for that session ID (per the OWASP Session Management guidance) — starts over. A reload discards unsaved work in that tab: form input, in-progress uploads, unsaved edits, and place/video position in a training player. Use Reload on pages you are keeping logged in, not pages you are typing into. Hold in place. No navigation. A pulse moves the pointer, focuses the page, may click only a non-control surface, and resumes a video that was already playing. Pasting a recognised training URL selects Hold automatically. Hold events are synthetic (isTrusted is false), so a player that requires a real device hand still wins. From the website alone, Hold can reach a tab only while that tab stays on keepalive.page's own origin; a course on another site needs the macOS helper or the browser extension. ## What it cannot do (honest limits) - It cannot defeat an absolute or time-boxed session lifetime (one that expires a fixed period after login regardless of activity). - It cannot defeat auth that depends on rotating a short-lived token rather than on page activity. - It cannot defeat sites that detect real mouse or keyboard input, daily seat-time caps or exams, or systems that continuously re-evaluate access. - It cannot complete, skip, certify, or pass an attention check on a course. - A website cannot see or reload a browser tab it did not open — the same-origin policy isolates sites, so no web page can enumerate or control your other tabs. This is a platform security boundary, not a missing feature. - Embedding a third-party site in an iframe usually fails, because most logged-in sites send X-Frame-Options or a CSP frame-ancestors directive that forbids framing; cross-origin fetch() also cannot read responses without CORS opt-in. Hence the tool opens a real tab and re-navigates it (Reload) or pulses it in place (Hold). - Background tabs are throttled (Chrome intensively throttles chained timers to roughly once per minute after a tab is hidden for 5 minutes), so the tool runs its clock in a Web Worker and favours intervals over a minute. Chrome Memory Saver can still freeze or discard a hidden tab; pinning the tab and adding a performance exception avoids this. - It will not keep Microsoft Teams or Webex status green — presence is computed from device activity, not from a refreshing tab. ## Where refreshing is refused, and why (the blacklist) Six targets are compiled into the app and matched by hostname before a page is ever kept; the tool says so instead of showing a green light it cannot honour: - Atlassian Cloud (Jira, Confluence): Atlassian counts a session as idle when the user takes no action and names an automatic page refresh as a passive interaction that does not count, so refreshing cannot extend it. - Citrix / NetScaler: client inactivity timeouts key on real mouse and keyboard input; HTTP traffic is invisible to them, and the tool will not simulate input. - Microsoft sign-in (Entra / Azure AD endpoints): an identity endpoint is not an application session; with Continuous Access Evaluation a logout is usually a revocation, not a timeout. - Google Workspace Admin: session length is an absolute lifetime measured from sign-in, not an inactivity timer. - Microsoft Teams and Webex: presence is set from activity the service can see; a reload is not activity, and you go Away after idle or screen lock. - Okta admin consoles, VPN and ZTNA gateways: these end a session when the IP address they see changes; refreshing cannot survive a VPN reconnect or a wifi-to-cellular handoff. Categories the tool cannot detect by hostname but that still will not work: PCI-scoped and administrative accounts (PCI DSS 4.0 requirement 8.2.8 mandates re-authentication after 15 idle minutes); electronic health records and clinical workstations (HIPAA automatic logoff is enforced below the browser); anything inside a remote-desktop or VDI session (a single video stream, nothing to reload); apps that do not slide the session on an unmodified request (Django's default SESSION_SAVE_EVERY_REQUEST is False computes expiry from the last modification, not the last request); queues, waiting rooms and virtual holding pages (a reload can cost your place); browser terminals and remote-desktop gateways (a reload tears down the live connection). ## OSHA 10/30 and SCORM players (when to Hold) Choose Hold in place for OSHA 10/30 Outreach courses and SCORM shells; a reload drops place and video position. Vendor notes: - ClickSafety: Hold; reload drops place. Daily limits and seat-time rules still apply. - CareerSafe: Hold; STOP/audio gates and seat time are yours to finish. - 360training: Hold for the player idle problem; not for exams. - HSI: documents a 15-minute inactivity session timeout on OSHA courses; Hold is the strategy that does not reload. Hold keeps the player from a stupid idle logout while you watch. It does not complete, skip, or certify the course, pass an attention check, or click Next. ## Recommended usage For ordinary idle logins: pick an interval roughly two-thirds of the site's idle window (e.g. every 20 minutes for a 30-minute timeout). Refreshing far more often is usually wasteful and sometimes useless: ASP.NET Core cookie auth re-issues the session cookie only on a request more than halfway through the window, and Salesforce ignores activity in the first half, so an early refresh renews nothing and the session expires on schedule. Pin the controlling tab and keep the machine awake. The second-tab pattern, for a page you are typing into: a reload destroys in-page state, so keep a cheap second tab on the same site reloading (or held) while you work in your original tab. Which tool runs the second tab depends on the site's session cookie: the website's own twin works where the session cookie travels on a cross-site navigation; the extension or the macOS helper works for a tab you already have open, including where the cookie is SameSite=Strict. For OSHA 10/30 and SCORM players: choose Hold in place (or paste the course URL and let the tool select it). Use the extension or macOS helper for a course already open on another site. ## Caveats and ethics Idle timeouts frequently exist as a security or compliance control, particularly on banking, healthcare, and shared-account systems. Deliberately defeating one may breach a site's terms of service, and a held-open session on a shared or unattended device is a real security risk. Check the relevant terms before relying on this for anything sensitive. Hold is marketed as keeping the player from idling out while you watch — never as cheating an LMS, skipping seat time, auto-completing OSHA training, passing an attention check, or finishing the course for you. ## Pages - The tool: https://keepalive.page/ - OSHA / SCORM Hold: https://keepalive.page/osha-scorm.html - How it works: https://keepalive.page/how-it-works.html - Compare (vs Session Alive, Easy Auto Refresh): https://keepalive.page/compare.html - The Blacklist (where refreshing is refused): https://keepalive.page/refusals.html - The Whitelist / directory (135 apps with documented timeouts): https://keepalive.page/directory.html - What else it keeps alive: https://keepalive.page/uses.html - Download (desktop app + clairvoyant macOS helper): https://keepalive.page/download.html - Support: https://keepalive.page/support.html - Privacy: https://keepalive.page/privacy.html