Most websites log you out after a period of inactivity. The OWASP session management guidelines say common idle timeouts are 2–5 minutes for high-value applications and 15–30 minutes for low-risk ones. Step away for a coffee and you come back to a sign-in page and lost work.
To keep a session alive in Chrome, reload the page a little before the timeout runs out. Each reload sends a fresh request to the site, which resets its inactivity timer. Auto Refresh Page can do this for you. Set an interval shorter than the site's timeout and choose Restart, so the page reloads only after you have actually been idle.
Refresh only on current tab
Show visual timer on the webpage
Refresh Behavior on User Interaction
Hard Refresh
There are five common reasons. Only the first one can be fixed by refreshing the page.
When you sign in, the site stores a session cookie in your browser and notes when you were last active. Every page load sends that cookie back, and the site resets your inactivity clock. Some sites also count idle time inside the page and show a countdown pop-up. A reload loads the page fresh, so that countdown starts over too.
As long as a reload arrives before the timeout, the session stays open. You do not need a special trick, just a reliable timer that is a bit shorter than the site's limit.
Will a hard refresh log me out? No. In Auto Refresh Page, Hard Refresh only skips the browser cache. It keeps your cookies, so your session survives. A normal refresh is enough to keep a session alive, though, and it is lighter on the site.
Refresh at about two-thirds of the site's idle timeout. That leaves a safe margin if a reload is slow or your connection drops for a moment.
| Site's idle timeout | Suggested refresh interval |
|---|---|
| 5 minutes | 3 minutes |
| 10 minutes | 7 minutes |
| 15 minutes | 10 minutes |
| 20 minutes | 15 minutes |
| 30 minutes | 20 minutes |
| 60 minutes | 45 minutes |
| Unknown | 10 minutes, then adjust |
Do not go much shorter than you need. Refreshing every few seconds does not keep you signed in any better. It only adds load, and some sites respond to rapid reloads with a CAPTCHA.
Every page you save goes into the Refresh List with its own interval. A CRM with a 30-minute timeout can refresh every 20 minutes while a support portal with a 10-minute timeout refreshes every 7. The Running switch at the top of the popup pauses or resumes all of them at once. See how to manage multiple URLs.
To bring your rules back after a restart, tick Start auto refresh on browser start. If Chrome deletes cookies when it closes, you will still need to sign in again first.
Some extensions keep sessions alive by sending small background requests without reloading the page. That is convenient when it works. Whether a site counts those requests as activity depends on how the site was built, though. A page reload is an ordinary visit, so it resets idle timers on almost any site. The usual downside of reloading, interrupting you while you work, is what Restart mode prevents: the page reloads only after you have been idle for the whole interval.
Idle timeouts exist to protect your account. Keep them working in these situations:
Even on your own device, lock your screen when you step away: Windows key+L on Windows, Ctrl+Cmd+Q on Mac.
Getting logged out mid-task is almost always an idle timeout. A refresh timed just under that limit keeps you signed in, and Restart mode makes sure it never gets in your way. Set it up once in Auto Refresh Page and stop typing your password ten times a day. Prefer not to install anything? See how to auto refresh Chrome without an extension.
Usually, yes. Most logouts come from an idle timeout, and every page reload counts as activity, so the site resets your inactivity timer. Refreshing cannot extend an absolute timeout, which signs you out after a fixed number of hours however active you are.
Refresh at about two-thirds of the site's idle timeout. For example, refresh every 10 minutes for a 15-minute timeout or every 20 minutes for a 30-minute timeout. If you don't know the timeout, start with 10 minutes and adjust.
No. In Auto Refresh Page, Hard Refresh only skips the browser cache and keeps your cookies, so your session stays open. A normal refresh is enough to keep a session alive, though.
Not in Restart mode. Turn on Refresh Behavior on User Interaction and choose Restart. Every click or keystroke restarts the countdown, so the page reloads only after you have been idle for the full interval.
No. Nothing runs while the computer sleeps, so the session can expire. A locked screen is fine as long as the computer stays awake and online.
On your own private device and for low-risk sites, yes. Don't do it on shared or public computers or on banking and payment sites, and check your company's IT policy before doing it on work systems.