Most sites log you out after a period of inactivity. Keep Every Page Alive reloads a page on a timer, and because each reload is a real request carrying your session cookie, the site's inactivity clock starts over — so the logout never arrives.
Enter the address of the site, choose an interval, and the page opens in its own tab and refreshes itself on schedule. Nothing to install, no account, and the whole thing runs in your browser.
https://mail.google.com.A surprising number of apps only renew your session on a request that arrives past the halfway point of the window — ASP.NET Core's cookie authentication is documented to re-issue the cookie only on “a request more than halfway through the expiration window”, and Salesforce ignores activity in the first half of its own window. Refresh too early against one of those and every request lands before it counts — the session expires exactly on schedule while the countdown here looks perfectly healthy. Two-thirds clears halfway with margin to spare. See the directory for per-app numbers.
The presets are ordinary minutes; the prime stagger option uses prime numbers between 17 and 887 seconds — primes rarely share factors, so several kept pages don't drift into refreshing in lockstep. You can also set any interval you like, from a second to a century, including leap days and leap years.
Everything below lives under Fine tuning in the panel, collapsed by default so a first visit stays simple.
The tab's own title shows a live countdown and a ⚠ if anything needs you, so a glance at the tab strip is enough. Your list can be exported and imported as a plain JSON file, and a link like keepalive.page/?url=example.com&every=10m arrives with everything pre-filled.
Yes, for idle timeouts. An inactivity timeout is measured from the last request the server saw for your session, so a real reload resets it. It does nothing against an absolute session limit that expires a fixed time after login.
Mostly. Browsers throttle timers in hidden tabs, so the clock here runs in a Web Worker and the intervals are longer than a minute. But Chrome's Memory Saver and similar features can freeze or discard a hidden tab outright, which pauses it — pin the tab and add the site to your browser's performance exceptions.
No, and neither can anything else that runs in a browser. Microsoft computes your Teams presence from your device's activity rather than from the Teams page — using the keyboard or mouse in any application keeps you Available, and it turns to Away after roughly five minutes of idle or when you lock the screen. Webex behaves the same way. A refreshing tab is simply not part of that signal. If you want to stay Available while reading, set your status manually in Teams or Webex; it holds until you change it. Full detail on the blacklist.
Extensions can reload tabs you already have open, which a website can't. If you only need one site kept warm, this page is enough and needs no install. If you want your existing tabs refreshed in place today, use the macOS helper or a dedicated auto-refresh extension. Our own extension — which can also keep sessions alive without reloading, for pages where a reload would destroy work — is in development and not yet in the Chrome Web Store.
The tool itself works in any modern browser on any operating system — it's just a web page. The optional real-tab helper is macOS-only, because it relies on macOS automation to talk to browsers.
A web page cannot see other browser tabs. The browser's same-origin policy isolates every site from every other, so no website — this one included — can read, list, or reload a tab it didn't open itself. This is a platform security boundary, not a missing feature. Reaching the tabs you already have open requires software on your own computer — see clairvoyant mode.