Chrome keeps refreshing pages on Android – fix it

Why your Chrome tabs keep reloading

Open Chrome on Android, switch to another app for 30 seconds, come back — and the page refreshes. You lose your scroll position, your form input, your place in a long article. It's maddening.

What's actually happening here is Android's memory management. When RAM gets tight, the OS kills background processes. Chrome is a big target because it's a hungry app. On devices with 4GB RAM or less (think budget Samsung A series, older Pixels, or any phone running Android 13+ with aggressive memory optimization), this happens constantly.

The fix isn't complicated, but you need to understand what you're disabling — because the trade-off is faster battery drain or slightly slower page loads.

The main fix: disable Chrome's memory-saver feature

Chrome for Android added a "Memory Saver" in 2023 that deliberately discards background tabs. It's on by default. Turn it off.

Open Chrome on your phone.
Tap the three-dot menu (top right) → Settings.
Go to Memory Saver (under the "Performance" section on Chrome 120+).
Toggle it off.

This stops Chrome itself from killing tabs. It's the first thing to try because it's a setting Chrome controls directly, not the OS.

Why this works: Memory Saver is a Chrome feature that unloads tabs from RAM after they've been inactive for a while. When you switch back, Chrome has to reload the page from scratch — causing that refresh. Disabling it tells Chrome: "keep every tab alive." The cost is higher RAM usage, meaning Chrome might slow down if you have 20+ tabs open. On 6GB+ devices, that's rarely an issue.

If it's still happening: stop Android from killing Chrome

Disabling Memory Saver doesn't stop Android itself from killing Chrome when the phone needs RAM. For that, you need to change how Android treats the app.

Option A: Disable battery optimization for Chrome

Android's battery optimization aggressively freezes background apps. Turning it off for Chrome tells the OS: "leave this one alone."

Go to Settings → Apps → Chrome.
Tap Battery (or App battery usage on Samsung).
Select Unrestricted (instead of "Optimized" or "Restricted").

On One UI 6 (Samsung phones): it's under Settings → Device care → Battery → Background usage limits → Never sleeping apps. Add Chrome to that list.

Option B: Lock Chrome in recent apps

On Android 12+, you can "lock" an app in the recent apps switcher so the system can't kill it.

Open the recent apps overview (swipe up and hold).
Find the Chrome card.
Tap the icon above the card (or long-press the card on some skins).
Select Lock.

This prevents the OS from closing Chrome when memory pressure hits. It's a per-session lock — after a reboot, you need to re-lock it.

Less common variations of the same problem

Variation 1: Only happens on certain Wi-Fi networks

If tabs refresh when you switch networks (e.g., leaving home Wi-Fi), the issue is Chrome's network prediction. It reloads pages thinking the network changed. Fix: go to Chrome Settings → Privacy and security → Use secure DNS and set it to Cloudflare (1.1.1.1). This stabilizes DNS queries across network changes.

Variation 2: YouTube or video-heavy tabs refresh

Media-heavy tabs consume more RAM. Android kills them first. The fix is the same as above, but also consider: in Chrome Settings → Lite mode, turn it on. Lite mode compresses pages and reduces RAM usage, meaning Chrome is less likely to hit the memory limit that triggers the kill.

Variation 3: Chrome beta or Dev channel crashing then refreshing

If you're on Chrome Beta or Canary, the browser itself crashes more often. That causes a clean refresh, not just a reload. Solution: switch back to stable Chrome. Beta features aren't worth the stability hit on mobile.

Prevention: avoid the conditions that trigger refreshes

Keep Chrome updated. Updates after Chrome 119 fixed some memory leaks that made the problem worse. Check Play Store weekly.
Close unused tabs. Having 30+ tabs open guarantees memory pressure. Use Chrome's tab grouping or just close them. I keep under 10.
Use a lighter browser if you have 4GB RAM or less. Bromite (if you can sideload it) or Firefox Focus won't refresh as much because they use less memory. Chrome is a hog on low-end hardware.
Restart your phone every few days. Android memory leaks accumulate. A reboot clears caches and resets memory maps. On Samsung devices especially, this cuts refresh frequency in half.
Don't use Chrome's "Continue where you left off" tab restore. That feature reloads all previous tabs on startup, which triggers the refresh cycle. Switch to "New tab page" in Chrome Settings → On startup.

Bottom line: Disable Chrome's Memory Saver first. If that's not enough, stop Android from killing Chrome via battery settings. On low-RAM phones, accept that no fix is perfect — but these steps reduce refreshes from "every 30 seconds" to "maybe once an hour."