The Browser Extensions Quietly Draining Your Battery

An extension is not a passive add-on. Many of them inject a script into every page you open, and that script runs for as long as the page is alive. Multiply by the number of tabs you keep open and the arithmetic gets unpleasant quickly.

The ones that cost the most share a pattern: they need to watch continuously rather than act occasionally. Price trackers polling in the background. Grammar and writing assistants parsing every text field as you type. Coupon finders checking every domain you visit. Tab managers keeping timers on dozens of tabs. Anything doing continuous video or audio processing.

None of these are malicious. They are doing the job you installed them for. The question is only whether you still want that job done badly enough to pay for it in runtime.

Finding the expensive ones

You do not need a third-party tool for this, and you should be wary of any "extension analyser" extension, which is a category with an obvious conflict of interest.

Chrome, Edge, Brave, and other Chromium browsers

Press Shift + Esc, or open the menu and choose More tools → Task manager. You get a live list of every tab and every extension with its memory footprint and CPU usage.

Sort by CPU and watch for thirty seconds or so while you browse normally. Tabs will spike as they render — that is expected. What you are looking for is an extension row holding steady above roughly 1 percent CPU while you are not interacting with it. An extension that is busy when you are idle is being busy on its own schedule, which is exactly the behaviour that costs battery.

Firefox

Type about:performance into the address bar. Firefox reports an "Energy impact" figure per tab and per extension, which is more directly relevant to battery life than raw CPU percentage.

Safari

Safari has no per-extension task manager, so use macOS Activity Monitor instead. Open the Energy tab and look at Safari's web content processes. For attribution, disable extensions one at a time and watch the figure — slower, but it works.

The audit

Once a quarter, open your extensions page and go through it honestly. Three questions, in order:

• Have I used this in the last month? If not, remove it. You can reinstall in twenty seconds if you turn out to be wrong.
• Is it still maintained? Check the last-updated date on its store listing. An extension untouched for two years with broad permissions is a security question as well as a performance one.
• Does it need access to every site? Most do not. Chromium browsers let you set an extension's site access to "on click" or a specific list, under its details page. This is the single highest-value change here — it cuts both the battery cost and the amount of your browsing the extension can see.

That third setting deserves emphasis. An extension you only need on a few sites but which has permission for all of them is running everywhere, all the time, for no benefit. Restricting it is free.

The fix is rarely "use no extensions." It is granting each one only the reach it genuinely needs.

A realistic expectation

Removing two or three continuously active extensions and restricting site access on the rest typically buys somewhere between thirty and ninety minutes of runtime on a laptop that spends its day in a browser. It also tends to make heavy pages noticeably more responsive, because there are fewer injected scripts competing on every page load.

It will not double your battery life, and anything promising that is selling something. But it is fifteen minutes of work for a real, repeatable gain — and unlike most battery advice, you can measure the before and after yourself.