Chrome Is Secretly Slowing Down Your PC — Here's How to Fix It
At some point in the last year, your computer got slower. Not dramatically, not all at once — just gradually, quietly, until one day you noticed the fan spinning when you're just reading an article, or the whole machine stuttering when you switch between apps, or your battery dying two hours before it used to.
You probably blamed the computer. Maybe you blamed Windows. Maybe you started wondering if it was time for a new laptop.
It might be Chrome.
Google Chrome is the most popular browser in the world, and it is also one of the most resource-hungry pieces of software on your entire computer. Not because of a bug. Not because of a bad update. By design — intentional architectural decisions that prioritise stability and speed in ways that quietly eat your RAM, spike your CPU, and drain your battery without ever showing you a warning.
The good news is that most of this is fixable. And fixing it doesn't require installing anything, paying for anything, or spending more than about twenty minutes.
First — Why Chrome Does This
Before we fix it, it helps to understand why it happens. Because once you understand the design, every fix on this list will make immediate sense.
Chrome runs on what's called a multi-process architecture. Every tab you open is treated as a separate process — essentially a separate mini-program running on your computer. Every extension you've installed runs as its own process. Internal Chrome components run as their own processes. Open ten tabs with five extensions active and you could easily have twenty separate processes competing for your RAM and CPU simultaneously.
The reason Google built it this way is actually sensible. If one tab crashes — a rogue script, a misbehaving website — it doesn't take the entire browser down with it. The other tabs survive. It's a stability feature.
The cost is that this architecture requires significantly more memory than a browser that handles all tabs in a single shared process. Chrome doesn't have a memory problem — it has a memory philosophy. And on a computer with 8GB of RAM, that philosophy can leave you with very little room for anything else.
Add to that the fact that Chrome keeps running in the background after you close the window, pre-loads pages it thinks you might visit next, and syncs your data constantly — and you have a browser that is doing quite a lot even when you think it's doing nothing.
Fix 1: Turn On Memory Saver — Right Now, Before Anything Else
This is the single most impactful change you can make and it takes about thirty seconds.
Memory Saver is a Chrome feature that automatically puts tabs to sleep when you haven't looked at them in a while. The tab stays visible in your tab bar. It doesn't disappear. But it stops consuming RAM and CPU in the background. When you click back to it, it reloads instantly. You barely notice the difference in use — but your computer absolutely notices.
To turn it on, click the three-dot menu in the top right corner of Chrome, go to Settings → Performance → Memory Saver and switch it on. You'll see three options: Moderate, Balanced, and Maximum. Balanced is the right choice for most people. Maximum is worth trying if your machine is genuinely struggling — it puts tabs to sleep more aggressively and reclaims memory faster.
Chrome is smart enough not to sleep tabs that are playing audio, running a video call, or have an active form you're filling in. You won't lose anything mid-task.
On a heavy browsing session with fifteen or twenty tabs open, Memory Saver can reduce Chrome's memory consumption by a significant margin. For some users, the difference is immediately visible in how the rest of the computer feels.
Fix 2: Use Chrome's Hidden Task Manager to Find What's Actually Killing Your PC
Most people don't know Chrome has its own Task Manager. It's one of the most useful diagnostic tools on your computer and it's been sitting there the whole time.
Press Shift + Esc on Windows to open it. On Mac, click the Chrome menu and go to Window → Task Manager.
What opens is a list of every process Chrome is currently running — every tab, every extension, every background service — with real-time CPU usage and memory footprint numbers next to each one.
Look at the Memory Footprint column first. If a single tab is using 500MB or more, that tab is doing something heavy — a complex web app, a video stream, an ad-heavy news site. You can kill it directly from the Task Manager without closing the rest of your browser.
Now look at your extensions. This is where most people get a surprise. An extension using 150MB or 200MB of memory is not unusual — and if you have seven extensions running, the collective memory consumption can rival the tabs themselves. Make a note of the offenders.
You don't have to uninstall anything based on what you see here. But knowing which extensions are genuinely heavy gives you real information to make decisions with, rather than guessing.
Fix 3: Audit Your Extensions — and Be Ruthless
Extensions are where Chrome slowdowns quietly accumulate over months and years. You install something once to use once. You forget about it. It runs in the background forever.
Type chrome://extensions into your address bar and press Enter. This shows every extension currently installed. Go through the list honestly. For every extension you see, ask: have I used this in the last two weeks? If the answer is no, disable it. If the answer is "I don't even remember installing this," remove it.
The key insight is that disabled extensions don't run. You can keep them installed — so they're easy to turn back on if you need them — but in a disabled state they consume zero memory and zero CPU. This is the right approach for extensions you use occasionally but not daily.
For extensions you actively use, check whether they're actually necessary as a browser extension or whether they do something you could do without the extension. Many people have extensions that replicate functionality that's already built into Chrome or Windows.
Disabling unused extensions is consistently one of the fastest ways to reclaim 20 to 30 percent of Chrome's memory usage. The effect is immediate and requires no restart.
Fix 4: Stop Chrome Running After You Close It
Close all your Chrome windows. Look at your system tray in the bottom right corner of Windows — the cluster of small icons near the clock. Is the Chrome icon still there?
If it is, Chrome is still running. Fully. In the background. Consuming RAM and CPU while you're using other applications, watching videos, or trying to get anything else done.
Chrome does this to keep background apps like Google Drive sync and notifications running after you've closed the browser. Whether you need those services running continuously is a question worth asking. Most people don't.
To turn it off, go to Settings → System and toggle off "Continue running background apps when Google Chrome is closed."
Once disabled, closing Chrome means Chrome is actually closed. The memory it was consuming is immediately returned to your system. For users on 8GB of RAM who run other applications alongside Chrome, this change alone can meaningfully improve how the rest of the computer performs.
Fix 5: Adjust or Disable Hardware Acceleration
Hardware acceleration is a Chrome feature that offloads graphical rendering work from your CPU to your GPU. On modern computers with a dedicated graphics card, this is a genuine improvement — smoother video playback, more responsive scrolling, less CPU strain.
On older computers, or on laptops with integrated graphics rather than a dedicated GPU, hardware acceleration can backfire. Chrome asks the GPU to do work it isn't well-suited for, the GPU struggles, and the result is increased memory usage, occasional stuttering, or input lag — particularly noticeable when scrolling or playing video.
If your computer is on the older side and Chrome feels janky, go to Settings → System and toggle off "Use graphics acceleration when available." Restart Chrome and use it normally for a day. If the stuttering and lag improved, leave it off. If nothing changed or it felt worse, turn it back on.
This one is a test rather than a guaranteed fix — it depends entirely on your hardware — but it's worth five minutes to find out.
Fix 6: Clear Your Cache — But Know What You're Actually Clearing
Chrome's cache is a store of temporary files — images, scripts, page data — that gets saved locally so websites load faster on repeat visits. Over time this cache grows, and a large or corrupted cache can cause Chrome to consume more CPU than necessary as it manages and references outdated data.
Press Ctrl + Shift + Delete to open the Clear Browsing Data panel. Select All time from the time range dropdown. Check Cached images and files. Leave your passwords and bookmarks alone — clearing the cache doesn't touch those. Hit Clear Data.
What this doesn't do: it doesn't free up RAM. Cache lives on your storage drive, not in active memory. If Chrome's RAM usage is your main problem, clearing the cache helps with page load behaviour and CPU processing — not with memory consumption. Both Memory Saver and extension management will do more for your RAM than cache clearing.
But if Chrome has been feeling sluggish in a general way — slow page loads, occasional freezes on sites you visit frequently — a cache clear is a useful reset and worth doing every few months regardless.
Fix 7: Turn Off Preloading — Stop Chrome Working Before You Ask It To
Chrome tries to be fast by predicting where you're going to click next and silently loading those pages in the background before you've actually clicked anything. The idea is that by the time you click a link, the page is already partially loaded and appears to open instantly.
The trade-off is that Chrome is consuming data, memory, and CPU loading pages you may never actually visit. If you clicked differently than Chrome predicted — or didn't click at all — that pre-loading work was wasted resources.
To adjust it, go to Settings → Performance → Preload Pages. You'll see three options: No Preloading, Standard Preloading, and Extended Preloading. Standard is the default. Switching to No Preloading stops Chrome from working ahead of you entirely, which reduces background activity at the cost of pages feeling slightly slower to open initially.
For users on metered internet connections or machines with limited RAM, No Preloading is worth trying. For everyone else, Standard is a reasonable default. Extended Preloading is the most aggressive option and the one most likely to contribute to sluggishness on lower-spec machines — if that's selected, bring it down to Standard at minimum.
The Honest Bottom Line
Chrome is not going to become a lightweight browser. The architecture it's built on is fundamental to how it works, and Google isn't going to redesign it from scratch. The multi-process model, the background services, the preloading — these are features, not bugs, and they serve real purposes for users on powerful hardware with fast connections.
But most of the defaults were chosen for Google's ideal user, not necessarily for your machine, your habits, or your RAM situation. Every fix on this list is about adjusting those defaults to match your actual circumstances rather than an imagined one.
Start with Memory Saver and the extension audit. Those two changes alone will recover most of what Chrome has been quietly taking. Work through the rest as needed. Give it a day and notice whether the fan is quieter, the switching between apps is smoother, and the battery is lasting a little longer.
Your computer probably isn't dying. It just needed someone to tell Chrome to calm down a little.
Also read: I used Claude Opus and Codex and the results are not what I expected
