How to Reduce Chrome Memory Usage on Your Computer

Published 2026-10-16 · Marion Remote Fix

Chrome is using too much RAM and your computer is slowing down because of it. You open Task Manager and see Chrome consuming 2, 4, or even 8 gigabytes of memory across dozens of processes. Every tab, every extension, and every service worker runs as a separate process in Chrome, and each one consumes memory independently. On computers with 8 GB of RAM or less, Chrome memory usage can push the system into using the page file (virtual memory on the hard drive), which dramatically slows everything down. The good news is that Chrome memory usage is highly controllable through settings changes, extension management, and browsing habits.

Why Chrome uses so much memory

  • Multi-process architecture: Chrome runs each tab, each extension, each plugin, and the GPU in separate processes. This design improves stability (one crashing tab does not take down the whole browser) and security (each process is sandboxed), but it means memory overhead multiplies with every open tab and extension. Each process has its own memory allocation including a copy of the rendering engine
  • Tab content: Modern websites are complex applications. A single Gmail tab can use 150 to 300 MB. Facebook or Twitter tabs with auto-loading feeds consume 200 to 500 MB. News sites with embedded videos and auto-playing ads use 100 to 300 MB each. Twenty open tabs can easily consume 3 to 6 GB of RAM
  • Extensions: Every installed extension runs its own process and consumes memory continuously, not just when you actively use it. Some extensions — particularly ad blockers processing large filter lists, password managers checking every form field, and productivity extensions monitoring page content — each use 50 to 200 MB. Ten extensions can add 500 MB to 1 GB of memory usage
  • Pre-rendering and caching: Chrome pre-loads pages it predicts you might visit and caches page data aggressively to make navigation feel instant. This trades memory for speed — useful on systems with plenty of RAM but problematic on memory-constrained systems

Find what is using memory in Chrome

Before making changes, identify the biggest memory consumers:

  • Press Shift+Esc while Chrome is open (or go to the three-dot menu, More Tools, Task Manager). Chrome has its own built-in Task Manager that shows memory usage for each tab, extension, service worker, and internal process
  • Sort by Memory Footprint to see which tabs and extensions use the most. Click on any entry to identify it — tabs show the page title and URL, extensions show their name
  • Look for tabs using unusually high memory (over 500 MB). These are often pages with memory leaks — web applications that allocate memory over time without releasing it. Refreshing these tabs resets their memory usage temporarily

Reduce tab memory usage

  • Enable Memory Saver (Tab Discarding): Chrome Settings, Performance, turn on Memory Saver (called Tab Freeze or Tab Discarding in older versions). This automatically suspends inactive tabs, freeing their memory. When you click back to a suspended tab, Chrome reloads it. You can add exceptions for sites you want to keep active. This single setting often reduces Chrome memory usage by 50 percent or more for users with many open tabs
  • Close tabs you are not using: This is the most effective fix. If you keep tabs open as reminders or bookmarks, use actual bookmarks instead. A bookmark uses zero memory. The OneTab extension can save all your open tabs as a list and restore them individually when needed, using a fraction of the memory
  • Use tab groups: Right-click a tab and select Add to Group. Chrome collapses grouped tabs, and collapsed groups use less memory because Chrome can prioritize discarding them. Organize tabs by topic or task and collapse groups you are not actively working with
  • Avoid heavy sites in background tabs: Social media feeds, video streaming sites, and web applications with real-time updates consume memory even when you are not looking at them. If you are not actively using a site, close the tab rather than leaving it in the background

Manage extensions

  • Audit installed extensions: Go to chrome://extensions. Review every extension. Remove any you do not actively use — each installed extension consumes memory whether or not you use it frequently. If an extension is something you use once a week, consider removing it and visiting the web version of that tool when needed
  • Disable extensions you use rarely: Toggle the switch to disable extensions instead of removing them. Disabled extensions use zero memory but can be re-enabled quickly when needed
  • Check extension memory usage: Use Chrome Task Manager (Shift+Esc) to see how much memory each extension uses. Extensions that use over 100 MB are worth evaluating — is the functionality worth that memory cost
  • Use fewer but better extensions: Some extensions overlap in functionality. A comprehensive ad blocker like uBlock Origin replaces multiple separate blocking extensions while using less total memory than the alternatives combined

Chrome settings to reduce memory

  • Preload pages: Settings, Performance (or Settings, Privacy and Security, Preload Pages). Set to No Preloading or Standard Preloading instead of Extended Preloading. Extended preloading uses extra memory to pre-render pages you might visit. Disabling it reduces memory usage at the cost of slightly slower page loads when navigating
  • Hardware acceleration: Settings, System, Use Hardware Acceleration When Available. This should generally be ON — it offloads rendering work to the GPU, reducing RAM usage. If your GPU has limited VRAM or you experience visual glitches, try disabling it, but on most systems hardware acceleration reduces overall memory pressure
  • Disable background apps: Settings, System, Continue Running Background Apps When Google Chrome Is Closed. Turn this OFF. When enabled, Chrome processes continue running after you close the browser window, consuming memory for notifications, syncing, and extension services even when you think Chrome is closed
  • Site settings and JavaScript: For sites that use excessive memory, you can restrict their capabilities. Settings, Privacy and Security, Site Settings. Disable JavaScript for specific memory-heavy sites — this prevents most dynamic content from loading but also breaks interactive features

System-level adjustments

  • Add more RAM: If your computer has 4 or 8 GB of RAM and you regularly use Chrome with multiple tabs, upgrading to 16 GB eliminates the memory pressure that causes slowdowns. Chrome is designed to use available memory for caching and performance — on a system with plenty of RAM, this is a feature, not a problem
  • Check for other memory consumers: Open Windows Task Manager (Ctrl+Shift+Esc) and sort by Memory. Other applications may be contributing to the memory pressure. Slack, Discord, Microsoft Teams, and Spotify are Electron apps that each use their own Chromium instance — running several of these alongside Chrome adds up quickly
  • Virtual memory settings: If you cannot add physical RAM immediately, ensure Windows virtual memory (page file) is set to System Managed on a fast drive (preferably an SSD). A page file on an SSD provides much better performance than on a mechanical hard drive when the system needs to swap memory contents

Alternative browsers

  • If Chrome memory usage is consistently problematic and you cannot add more RAM, consider browsers that use less memory. Firefox uses a different architecture that often uses less memory with many tabs. Microsoft Edge shares the Chromium engine but has more aggressive sleeping tabs. Brave is Chrome-based but includes built-in ad blocking that removes memory-heavy ad content before it loads

Chrome performance help in Marion

If Chrome is making your computer unbearably slow and the settings above do not help enough, Marion Remote Fix can remotely check your system memory, identify resource-hungry processes, optimize Chrome settings, evaluate whether a RAM upgrade would help, and configure your computer to handle your browsing needs without slowdowns.

← Back to Blog