Why Is Chrome Using So Much CPU?

High CPU in Chrome is a more tractable problem than high memory, because memory can be held passively by many tabs at once while CPU is only consumed by something actively executing right now. There is almost always exactly one owner, and Chrome will tell you its name.

The fan noise, the hot laptop and the battery draining in two hours are all the same symptom. Start by identifying the process rather than applying general fixes.

Find the process in fifteen seconds

Press Shift+Esc on Windows and Linux, or open the ⋮ menu → More tools → Task manager on any platform.

Click the CPU column header to sort. Watch it for ten seconds rather than reading one snapshot — CPU fluctuates, and the entry that stays high is the one that matters.

What you are likely to see:

Select any row and click End process. If the CPU drops immediately, you have your answer. The tab shows a crash page and reloads with one click.

That last row is worth knowing about: entries labelled Subframe are iframes, usually advertising. A single badly written ad script can hold a core at full speed indefinitely on a page that looks completely static.

Check hardware acceleration

This is the most common systemic cause and the easiest to miss, because nothing appears broken — everything is just several times more expensive than it should be.

With acceleration working, video decoding and page compositing happen on the GPU. Without it, all of that lands on the CPU. The difference on a 1080p video is roughly 5% CPU versus 25%.

Go to Settings → System and confirm Use graphics acceleration when available is on.

Then verify it is actually working. Open chrome://gpu and look at the list at the top. You want Hardware accelerated next to Video Decode and Canvas. If you see Software only on entries that should be accelerated, the feature is enabled but not functioning — almost always a graphics driver problem.

Updating the graphics driver from the GPU vendor’s site, rather than through Windows Update, fixes the majority of these.

Audit extensions properly

An extension with permission to run on all sites executes its code on every page you open. Its cost therefore scales with your browsing, and a poorly written one is a permanent CPU tax.

Open chrome://extensions and:

1. Remove anything you do not use. Most people carry two or three they installed once.
2. Restrict site access. Click an extension’s Details, and change Site access from On all sites to On click wherever the extension still works that way.
3. Test the suspects. Disable the largest CPU consumers from the task manager list, restart Chrome, and watch whether the problem follows.

The definitive test is a clean profile. Click your profile icon → Add → set up a new profile with no extensions, and use it for an hour. If CPU is normal there, an extension is responsible and you can bisect the list by re-enabling in halves.

Deal with the tabs that legitimately work

Some CPU use is correct. A video call encodes and decodes continuously. A spreadsheet recalculates. A live dashboard polls. Chrome cannot make these free.

What it can do is stop everything else running:

• Memory Saver, under Settings → Performance, discards inactive tabs. A discarded tab uses no CPU at all. It is named for memory but the CPU effect is just as real.
• Pin the tabs that must stay live and let the rest be discarded.
• Use tab groups and collapse them — collapsed groups are stronger candidates for discarding.

If an idle background tab is using CPU and should not be, the page is running a timer it does not need. Close it rather than trying to fix it.

The cases that look like Chrome but are not

The whole machine is busy. Chrome is often blamed for CPU that belongs to Windows Defender, a search indexer or a stuck update. Check the system-level picture first — how to find what’s using 100% CPU or disk on Windows covers reading Task Manager and Resource Monitor properly.

Thermal throttling. A laptop that is hot runs its CPU slower, so the same work shows a higher percentage. If Chrome feels fine for ten minutes and then degrades, the problem is heat rather than the browser.

Too little RAM. Under memory pressure the system pages to disk constantly, and the resulting stall looks like a busy processor. That is a different problem with a different fix — see Chrome using too much RAM.

Suspect mining if the pattern fits

One tab pinned at high CPU, no visible activity, and the load disappearing the moment you close the tab is the signature of an in-page cryptominer. It also happens through compromised extensions, which is harder to spot because the load follows you across every site.

Close the tab, remove the extension, and run a scan. Chrome’s own chrome://settings/safetyCheck is a reasonable first pass.

What does not help

• “Optimiser” and cleaner utilities. They do not affect what code a page runs.
• Disabling all extensions permanently. Useful as a diagnostic, excessive as a fix. Find the one responsible.
• Turning off hardware acceleration because an article said so. It usually makes CPU use worse. Only a specific driver bug justifies it.
• Limiting Chrome’s process count via flags. Reduces isolation, does not reduce the work being done.

Realistic expectations

In most cases this ends with one specific culprit — a tab, an ad frame, or an extension — and killing it returns CPU to near zero in seconds. Fixing hardware acceleration is the other common win, and on a laptop it is worth an hour or more of battery life during video playback.

If nothing in Chrome’s task manager stands out and the machine is still busy, Chrome is not your problem. Look at the system.