Chrome reloading tabs constantly — tabs refreshing when you switch back to them, losing your place on a page, or the tab indicator showing a reload that you didn’t initiate — is almost always a memory management issue. Chrome aggressively frees RAM by discarding inactive tabs; when you return to a tab, it reloads from scratch. For a broader walkthrough, our Google Chrome Errors is a good next read.
This is Chrome working as designed on machines with limited RAM. The question is how to stop it from happening, or at least reduce how aggressively it occurs.
The main cause: tab discarding for memory
Chrome’s “Tab Discard” feature removes inactive tabs from memory when RAM is low, keeping the tab visible in the tab strip but requiring a reload when accessed. If you have 20+ tabs open on an 8 GB machine while running other applications: Chrome will discard tabs you haven’t visited recently to keep the active tab and overall system responsive.
Navigate to chrome://discards to see which tabs are discarded, which are active, and why. This page is the most useful diagnostic for tab reload behaviour — it shows Chrome’s internal state for every open tab.
Fix 1: Disable automatic tab discarding
Chrome flags provide a way to reduce tab discarding. Navigate to chrome://flags/#automatic-tab-discarding → set to Disabled → Relaunch Chrome. This prevents Chrome from automatically discarding tabs. The trade-off: Chrome uses more RAM and the system may become slower when many tabs are open.
If the flag isn’t available in your Chrome version: Chrome Settings → Performance → “Memory saver” (labeled differently depending on Chrome version) → toggle Off. Memory Saver is Chrome’s official version of tab discarding with a user-accessible toggle.
Fix 2: Manage Memory Saver mode
Chrome Settings → Performance → Memory Saver → when enabled, you can add exceptions for specific sites that should never be discarded. This lets you keep critical work tabs active while still discarding less important tabs from memory.
Click “Customise” or “Add a site” to the Memory Saver exclusion list → add sites like Google Docs, your email client, project management tools — whatever you can’t afford to have refresh. Less important tabs (news, reference pages, shopping) can be discarded without issue.
Fix 3: Extensions causing tab reloads
Some extensions trigger page reloads intentionally or as a side effect. Tab managers, productivity extensions, and ad blockers occasionally reload pages during their update cycle or when their rules change.
Test: disable all extensions → test tab switching. If tabs stop reloading: re-enable extensions one at a time to identify the cause. Tab manager extensions that “restore sessions” are particularly likely to trigger reloads — they may be refreshing tabs to verify their state is current.
Fix 4: Add more RAM (hardware solution)
The permanent solution to tab discarding on machines with 8 GB or less RAM: upgrade to 16 GB. Chrome with 10 open tabs, a video editor, and a couple other applications comfortably stays within 16 GB. Below 8 GB, with many tabs open, tab discarding is almost unavoidable regardless of Chrome settings.
If hardware upgrade isn’t immediately possible: close tabs you’re not actively using. Tab groups (right-click a tab → Add to new group) help organise tabs so you can close groups you don’t need without losing track of the URLs.
Tab reloading on specific sites
Some websites intentionally force a page refresh when you navigate away and return, using JavaScript session timeout detection or authentication token refresh. This isn’t Chrome reloading the tab — it’s the site responding to your return. Signs: the tab indicator briefly shows activity when you switch to it, and the page position resets (you’re back at the top). There’s no Chrome fix for this; it’s server-side behaviour by the specific website.
Chrome profile and background processes
Chrome Settings → System → “Continue running background apps when Google Chrome is closed” — if enabled: Chrome maintains background activity even when the window is closed. This background activity sometimes triggers apparent tab reloads when the window is reopened. Disabling this reduces Chrome’s background resource usage and prevents some unexpected tab refresh behaviour.
Our guide on Chrome performance optimisation covers memory management and background process settings more broadly. For RAM-related slowness that affects tab performance system-wide, our system performance guide covers memory pressure monitoring and management. Chrome’s Memory Saver documentation covers the exclusion list, the aggressiveness settings (standard vs extreme), and how tab activity tracking works — including why some sites you visit frequently are protected from discarding automatically.
Tab groups as a memory management strategy
Chrome’s Tab Groups feature (right-click any tab → “Add tab to new group”) lets you colour-code and label groups of related tabs. Collapsing a group (click the group label) hides its tabs visually while keeping them in memory — but also makes them less likely to be discarded since they’re part of an active group. For power users with many open tabs: organising into groups of 5-8 related tabs, with less-needed groups collapsed, provides a practical balance between access and memory usage.
chrome://discards explained
The discards page shows several key columns for each open tab:
- State: Active (currently visible), Hidden (open but not visible), Discarded (out of memory, will reload on access)
- Site engagement score: Chrome’s measure of how often you interact with this site — higher-scoring sites are less likely to be discarded
- Reactivation score: Chrome’s prediction of whether you’ll return to this tab — low-scored tabs get discarded first
- Last active time: when the tab was last focused — the most recently used tabs survive longest
The “Urgently Discard” button on specific tabs lets you manually discard a tab to free memory — useful for large pages you’re done reading but want to keep the URL accessible.
Memory Saver aggressiveness settings
In Chrome 108+: Settings → Performance → Memory Saver → “Mode” → choose between Standard (waits longer before discarding) and Extreme (discards more aggressively). For machines with adequate RAM where occasional discarding is acceptable: Standard is the right choice. For machines under constant memory pressure: Extreme is counterproductive if tabs you need frequently keep reloading. The per-site exclusion list is more useful than the aggressiveness setting in most cases.
Hardware acceleration and tab rendering
Tabs that use WebGL, video players, or complex animations consume significantly more GPU memory than static pages. Chrome’s GPU process shares memory with the rest of the system. When GPU memory is exhausted (on systems with shared GPU memory like Intel integrated graphics): Chrome may discard tabs to reduce GPU load. Settings → System → “Use hardware acceleration when available” → disabling this can reduce GPU memory pressure and reduce tab discards on systems with limited GPU memory, at the cost of slower visual rendering.
Chrome Task Manager for per-tab memory
Chrome’s built-in Task Manager (Shift+Esc while Chrome is open) shows memory usage per tab, extension, and Chrome process. This is the fastest way to identify which tabs are consuming the most memory. Sort by “Memory footprint” descending → the largest tabs are the first candidates for manual closing or discarding. A single tab with a complex web app can use 500 MB-1 GB; finding and managing these high-memory tabs makes a bigger impact than global Chrome settings changes.
Reading List as a tab alternative
The Chrome Reading List (bookmark icon → Reading List, or three dots → Bookmarks → Reading List) saves pages for later reading without keeping them open as tabs. For tabs you’ve opened to “read later”: adding them to the Reading List and closing the tab eliminates the memory pressure while preserving easy access. The Reading List syncs across devices via Chrome account, making it more useful than just bookmarks for current-session “read later” content.
Is it the page reloading, or Chrome?
Not every reload comes from Chrome. JavaScript refresh timers, news sites that periodically pull fresh content, single-page apps that reset on session timeout, and pages that redirect after detecting inactivity all produce reloads that look like Chrome but originate in the page’s own code. To tell them apart, open Developer Tools (F12) → Network tab → tick Preserve log, then wait for a reload. If it shows up as a full page-load request and the Initiator points at the page, the site is doing it — and none of the Memory Saver fixes above will change that.
Back/forward navigation and the bfcache
Chrome’s Back/Forward Cache (bfcache) keeps full page snapshots in memory so pressing back or forward is instant instead of a reload. When that cache is disabled or evicted, hitting back triggers a full reload — which often gets read as “Chrome keeps reloading my tabs” when it is really the navigation cache being cleared. You can see a tab’s lifecycle state at chrome://discards/: anything marked Discarded will reload when you return to it, while Active or Frozen tabs will not.
Telling a crash apart from a Memory Saver suspension
A renderer crash — the GPU or content process going down because of a driver or extension fault — looks identical to a Memory Saver suspension from your seat: the tab blanks and shows a loading indicator when you switch back. The causes are entirely different, though. Right after a reload, open chrome://crashes/; if a crash entry is timestamped within seconds of what you just saw, it was a crash and the Memory Saver fixes will not help. A clean crashes list points back to ordinary tab suspension instead.
Preventing specific tabs from reloading
For truly critical tabs that absolutely must not reload: using a pinned tab (right-click tab → Pin) provides slight memory priority. For complete reload protection: Tab Wrangler or Session Buddy Chrome extensions provide “lock” features that mark specific tabs as always-active, preventing Chrome from discarding them regardless of memory pressure. These extensions come with their own RAM cost but ensure protected tabs never reload unexpectedly.
| Situation | Cause | Fix |
| Tabs reload after switching away | Memory Saver discarding inactive tabs | Add to Memory Saver exclusion list; disable Memory Saver |
| Specific tabs reload at intervals | Extension or site-side refresh | Disable extensions; check if site forces refresh |
| All tabs reload when switching back to Chrome | Chrome was suspended while backgrounded | Disable “Continue running background apps”; update Chrome |
| Reloads correlate with other app use | System RAM pressure | Close unused tabs; upgrade RAM; use Reading List |
Chrome tab reloading is fundamentally a memory management trade-off. Chrome is choosing between system stability and tab continuity — it prefers a responsive system over preserving tabs you might not return to. Understanding this makes the fix obvious: give Chrome more memory to work with (by closing other tabs or upgrading RAM), or tell Chrome specifically which tabs matter (via Memory Saver exclusions). The chrome://discards page remains the single most useful diagnostic for anyone who wants to understand exactly what Chrome is doing with their tabs.
For developers and power users who want the most aggressive approach to preventing tab discards: Chrome can be launched with command line flags that modify its memory management. Creating a Chrome shortcut with --disable-tab-discarding in the target field completely disables tab discarding regardless of Memory Saver settings. The trade-off: Chrome will use as much RAM as all open tabs require — potentially causing system slowdowns on low-RAM machines. This is appropriate for developer machines with 32 GB+ RAM where tab continuity is important for testing workflows.
Chrome’s proactive tab freeze
Separate from tab discarding: Chrome also “freezes” inactive background tabs, reducing their CPU usage without removing them from memory. Frozen tabs don’t reload when you switch to them — they simply resume execution. Freezing is generally invisible and helpful. Discarding is what causes visible reloads. The chrome://discards page distinguishes between frozen and discarded tabs, which is useful when trying to determine whether a tab will reload on access (discarded) or simply resume (frozen).
One thing that genuinely helps with tab management at scale: using Chrome’s profile system. Creating separate Chrome profiles for work and personal use keeps tab counts manageable per profile, with the system only allocating memory for active profiles’ tabs. Work tabs on the work profile stay separate from personal browsing, and each profile’s inactive tabs compete for memory only within their profile rather than all mixing together. This organisation approach produces a better experience than trying to keep 50+ mixed tabs in a single profile.
Chrome’s memory usage over time
Chrome’s memory usage tends to grow during a browsing session as cached page data, scripts, and media accumulate. After hours of browsing, the same 20 tabs that started at 2 GB may be using 4 GB — not because of leaks but because Chrome caches more aggressively to anticipate your navigation. Periodically restarting Chrome (or using the “Relaunch” button that appears in the menu when an update is pending) clears this accumulated memory and returns Chrome to its baseline usage. For users who leave Chrome running continuously for days: a daily or session-end restart is a practical habit that keeps memory usage predictable.
For workplaces where specific web apps must remain active throughout the day (project management tools, CRM systems, communication platforms), making those sites Chrome Progressive Web Apps (PWAs) — installed via Chrome three-dot menu → “Save and share” → “Install as app” → install — creates dedicated app windows separate from the browser’s tab management. PWA windows aren’t subject to tab discarding in the same way browser tabs are, since they’re treated as separate applications. This is a practical architectural solution for the specific tabs that absolutely cannot reload during a workday.
Tab reloading is one of those Chrome behaviours that generates significant user frustration but has a logical explanation and practical solutions. The Memory Saver exclusion list for critical sites, tab groups for organisation, and chrome://discards for diagnosis together provide the complete toolkit for managing it. For the subset of users who genuinely need all tabs to always be live: the RAM upgrade is the only truly satisfying fix — everything else is working around the fundamental constraint that modern web applications are memory-intensive and modern systems have finite RAM.
Finally: if tab reloading started suddenly after Chrome auto-updated and was fine before: a Chrome update changed Memory Saver’s aggressiveness or moved the control location. Check Settings → Performance for new options that appeared after the update and configure them to match your preferred behaviour. Chrome updates frequently change where these controls live and how they’re labelled, which is why step-by-step instructions sometimes don’t match the current interface. Our guide on Stop Chrome Tabs From Reloading covers an adjacent issue.
