Chrome Lagging? 12 Fixes for a Slow, Sluggish Browser

Chrome lagging usually isn’t random. Something specific is eating memory or CPU — a tab, an extension, a stale cache, or a graphics driver that hasn’t been updated in a while — and once you find it, the fix is usually quick. This guide works through the checks in the order that actually saves you time: Task Manager before extensions, extensions before a full reset.

It covers Windows, Mac, and Linux, with a pointer to Chromebook-specific fixes where they diverge. You’ll also find a quick-answer table below if you just want the fastest fix for your situation, whether that’s chrome slow after a long session, YouTube lagging on Chrome specifically, or chrome sluggish behavior on an older machine. One thing worth deciding upfront: if your fix involves closing tabs or restarting Chrome, save your open windows first so you don’t trade one problem for another.

Why Is Chrome Lagging or Running Slow?

Chrome lags when something on your computer can’t keep up with what the browser is asking of it — usually a tab, an extension, low RAM, or an outdated graphics driver. The table below matches common situations to the fix most likely to work first.

Beyond those individual triggers, a few things tend to compound. Dozens of open tabs each hold some memory, even idle ones, unless Memory Saver has deactivated them. Extensions that inject scripts into every page (ad blockers, price trackers, VPN tools) add a small tax to every single page load, and that tax adds up fast if you’ve got several running at once. A browser cache that’s grown huge over months can slow down page rendering on sites you visit often, and an outdated GPU driver can turn Chrome’s hardware acceleration, meant to speed things up, into the thing dragging it down.

None of this is Chrome-specific in the sense of being unfixable; it’s mostly resource math. The rest of this guide walks through each cause with the check to run and the setting to change, starting with the fastest options. If you’re troubleshooting a Chromebook rather than a desktop, the causes overlap but aren’t identical enough to cover fully here — see Why Is My Chromebook So Slow? for the ChromeOS-specific version of this list.

What’s the Quickest Fix for Chrome Sluggish Performance?

The fastest fix for a chrome sluggish moment is closing the tab causing it and restarting Chrome, which clears most lag in under a minute. It won’t fix a chronic problem, but it’s worth trying before anything more involved, since it costs you almost nothing.

A full quit-and-reopen matters more than it sounds like it should. Closing just the window can leave background processes running, especially the GPU process, and those are often what’s stuck. Quitting Chrome entirely kills all of it and starts fresh, which clears small memory leaks that build up over a long session without you doing anything wrong.

If a tab is frozen rather than just slow (not responding to clicks, spinning tab icon that never resolves) that’s a slightly different problem with its own fixes; see Chrome Freeze or Not Responding: 9 Fixes That Work for that specific case. And if it’s really one page misbehaving rather than the whole browser, a hard refresh on just that page (Ctrl + Shift + R, or Cmd + Shift + R on Mac) is faster than restarting anything.

Accidentally closed the wrong tab in the process? Press Ctrl + Shift + T (Cmd + Shift + T on Mac) to reopen it — Chrome keeps a short list of recently closed tabs and windows for exactly this.

How Do I Check What’s Slowing Chrome Down?

Open Chrome’s Task Manager to see exactly which tab or extension is using the most CPU and memory, instead of guessing which one to close. It’s a separate window from your regular browser tabs and lists every process Chrome is running.

Task Manager lists more than just your tabs. It also shows separate rows for extensions, the GPU process, and utility processes Chrome runs in the background. A single tab using an unusually large amount of memory is often a page with autoplay video, a lot of embedded ads, or a script stuck in a loop. An extension near the top of the CPU column, especially one you rarely open, is worth disabling as a test.

For a deeper look at reading these numbers and what counts as “too much,” see Chrome Task Manager: How to Find the Tab Eating Your Memory. This step alone resolves a lot of chrome is lagging complaints, since it turns a vague slowdown into one specific thing you can close or disable.

How Do I Turn On Chrome Memory Saver to Stop Lagging?

Turn on Memory Saver under Settings > Performance, then choose how aggressively it deactivates tabs you aren’t using. Chrome deactivates inactive tabs to free memory and automatically reloads them the moment you click back in. You don’t lose anything, you just wait a beat for the page to come back.

Test it without waiting. Visit chrome://discards and click Urgent Discard next to any tab to see how Memory Saver’s deactivation behaves, without waiting for the timer.

Memory Saver is Chrome’s own answer to the “too many tabs” problem, and it’s worth trusting over a third-party extension that claims to do the same thing. Google’s own engineering blog notes a discarded tab can use up to 80% less memory than an active one, which is a meaningful difference if you routinely keep twenty or more tabs open across a workday.

It’s not a cure-all, though. Memory Saver only helps with tabs you’re not currently looking at. It won’t touch the tab you’re actively working in, so if that specific tab is heavy, you’re back to Task Manager. Worth pairing it with Energy Saver too, a separate toggle in the same Performance settings that reduces CPU use from eligible background tabs, though it exempts anything playing audio or on a video call. Full details on both settings and how Chrome decides what to deactivate are in Chrome Memory Saver: How It Works and Its Limits.

Why Is YouTube Lagging on Chrome Specifically?

YouTube lagging on Chrome usually comes from hardware acceleration or an outdated graphics driver, not from Chrome being generally slow — if other sites feel fine, the cause is narrower than a full browser problem. Video decoding leans on your GPU more than almost anything else you do in a browser, so it’s the first place a graphics conflict shows up.

Start by testing in Incognito, since extensions are disabled there by default unless you’ve explicitly allowed them. If the video plays cleanly, work back through your extensions the same way described earlier: disable all, re-enable one at a time. Ad blockers and privacy extensions that inspect network requests are common culprits with video-heavy sites, since they’re doing extra work on every request YouTube’s player makes.

If Incognito doesn’t fix it, check hardware acceleration under Settings > System — toggling it off, then relaunching Chrome, tells you whether your GPU driver is the bottleneck. An outdated driver is a frequent, boring cause here: if turning hardware acceleration off makes the lag disappear, updating your graphics driver through Windows Update or your GPU manufacturer’s own updater is usually the better long-term fix than leaving acceleration off permanently, since it’s meant to make video and animation smoother, not slower. Lowering the video’s playback quality is a quick workaround while you sort out the underlying cause, and closing any other tab actively playing audio or video frees up the same GPU resources YouTube is competing for.

Does Clearing Cache and Cookies Fix Chrome Going Slow?

Sometimes — clearing cache helps when chrome slow behavior is tied to one specific, bloated site, but it won’t fix a system-wide slowdown caused by too many tabs or a heavy extension. Cache exists to make sites you visit often load faster the second time, so clearing it is closer to a targeted fix than a general performance boost.

If it’s really one page misbehaving, a hard refresh is faster and less disruptive than wiping your whole cache and cookies. It forces that single page to reload everything from the server without touching your saved logins elsewhere. Our hard refresh guide covers the shortcut and when a hard refresh beats a full cache clear.

Clearing cookies specifically comes with a trade-off worth knowing before you do it: you’ll get logged out of most sites, since cookies are what keep you signed in. If your goal is speed rather than a fresh start, clearing cache alone (without cookies) in Chrome’s “Clear browsing data” dialog gets you most of the benefit without the inconvenience of re-logging into everything. Worth doing this on the specific slow site rather than reaching for a full browser reset, which clears far more than you likely need and won’t touch the tab or extension causing a broader chrome sluggish problem anyway.

Could Extensions Be Making Chrome Sluggish?

Yes — extensions that run on every page load are one of the most common hidden causes of chrome lagging, especially ones doing constant background work like blocking ads, checking prices, or routing traffic through a VPN. A single extension rarely causes trouble on its own, but a handful running together adds up fast.

• Ad blockers. Useful, but they inspect every request on every page, which adds a small delay that compounds on ad-heavy sites.
• VPN or proxy extensions. Routing all your traffic through another server slows every page load by design, not by accident.
• Coupon and shopping helpers. Many scan every page you visit for deals, whether you’re shopping or not.
• Grammar and writing assistants. These typically scan text fields on every page, which can lag typing on text-heavy sites.

The reliable way to find the culprit is the same process-of-elimination approach as troubleshooting anything else: disable everything at chrome://extensions, confirm the lag is gone, then turn extensions back on one at a time until it returns. Whichever one brings the slowdown back with it is your answer.

It’s worth doing this occasionally even without an active problem. Extensions you installed for a one-time task and forgot about are still running on every page, and Chrome’s Task Manager (covered above) will show you exactly which ones are consuming CPU or memory right now if you’d rather skip the trial-and-error version. Removing anything you don’t recognize or no longer use is a low-risk way to keep chrome browser running slow from creeping back in later.

Should I Update Chrome or My Graphics Drivers?

Yes to both — an outdated Chrome build or an outdated GPU driver is a common, unglamorous cause of chrome browser running slow, especially once hardware acceleration is involved. Neither takes long to check, and both are worth ruling out before you spend time on anything more involved.

Chrome updates itself automatically in the background in most cases, but it only applies fully after a relaunch. Check your current version at chrome://settings/help — if an update is ready, you’ll see a “Relaunch” button right there, and clicking it applies the update immediately instead of waiting for Chrome’s next natural restart. Performance fixes ship in these updates regularly, so a build that’s several versions behind can be carrying bugs that were already patched.

Your graphics driver is a separate piece of software from Chrome, managed by your operating system or your GPU manufacturer, and it’s easy to forget it needs updating too. On Windows, Windows Update handles many driver updates automatically, though checking directly with your GPU manufacturer (NVIDIA, AMD, or Intel) sometimes turns up a newer version faster. On Mac, GPU drivers are bundled into macOS updates rather than managed separately, so checking for a pending macOS Software Update covers the same ground. If Chrome’s hardware acceleration is fighting an old driver, that mismatch shows up as exactly the kind of stutter and lag people describe as chrome is lagging, and it’s often mistaken for a Chrome problem when it’s really a driver one.

How Do I Fix Chrome Running Slow Because of Too Many Tabs?

Too many tabs slow Chrome down through memory, not just visual clutter — every open tab holds some RAM even when you’re not looking at it, though Memory Saver reduces how much. The fix isn’t necessarily closing everything; it’s giving Chrome a way to manage what’s open without you losing track of it.

Chrome’s own tools help here beyond Memory Saver. Tab groups (right-click a tab > Add tab to group) let you collapse related tabs down to a single labeled pill instead of a wall of favicons, which cuts down visual overload even if it doesn’t directly free memory. Tab Search, the small dropdown arrow in your tab strip, plus the shortcut Ctrl + Shift + A, lets you jump straight to any open tab by name instead of hunting through dozens of them. And Ctrl + Shift + D bookmarks every open tab in one action, which works as a manual escape valve when a window has gotten out of hand and you’d rather archive it than lose it.

Our full breakdown of when to close, group, or suspend tabs (and how to decide which) is in Too Many Tabs? How to Fix Tab Overload Without Losing Anything.

None of this replaces Memory Saver or Task Manager. It’s a layer on top, aimed at the part of the problem that’s really about you losing track of what’s open, not just Chrome running low on RAM. If you’re consistently maxing out available memory regardless of how well you organize tabs, that’s a sign your machine’s RAM, not your habits, is the limit; see Is 8GB of RAM Enough for Chrome? for how many tabs is realistic at that size.

How Do I Stop Losing Tabs When Chrome Crashes or Freezes While Fixing It?

Restarting Chrome to fix lag carries its own risk: if it crashes instead of closing cleanly, “Continue where you left off” doesn’t always catch everything, and you can lose the exact tabs you were trying to save time on. Saving your session before you start troubleshooting removes that risk entirely.

Skip old tab suspenders. The original Great Suspender extension was removed from the Chrome Web Store and force-disabled by Google in February 2021, after an ownership change added code flagged as malware. Use Chrome’s built-in Memory Saver instead of a third-party suspender.

If you’re still trying to recover tabs a suspender like that closed years ago, our Great Suspender recovery guide walks through the unofficial workaround people use, since there’s no official Google tool for it. For a crash that just happened, Chrome Crashed? How to Restart It and Get Your Tabs Back covers what Chrome’s own “Continue where you left off” can and can’t restore, and Chrome Freeze or Not Responding: 9 Fixes That Work covers a frozen-but-not-crashed browser specifically.

Manual saving works fine if you remember to do it before every risky change. An automatic layer underneath it means you’re covered on the days you forget, which, if you’re already dealing with chrome browser running slow, is probably not the day you want to also lose your tabs. It’s free to set up either way; see the download page if you want it running before your next troubleshooting session rather than after.