Chrome Battery Drain on Mac: Why It Happens and How to Get Hours Back

Chrome battery drain on a Mac is easy to spot: you unplug at 100%, open your usual tabs, and two hours later the MacBook asks for a charger. Click the battery icon in the menu bar and Google Chrome sits under Apps Using Significant Energy.

Chrome does not have to drain your battery that fast. Most of the energy goes to a few tabs and extensions doing work in the background, and macOS and Chrome both show you exactly which. This guide shows how to read those numbers, then the settings and habits that win back real hours.

The short answer#

• Find the energy hog in Activity Monitor's Energy tab, then in Chrome's task manager.
• Turn on Energy Saver in Chrome's Performance settings.
• Let idle tabs sleep with Memory Saver. Sleeping tabs use no energy.
• Pause video and quit Chrome fully when you are done.

What we measured on a Mac#

Tested on a MacBook Pro (M1 Pro) with 16 GB of RAM, macOS 26.3, running on battery, Chrome 155, October 21, 2026. We used a fresh Chrome profile and read CPU and the POWER column of macOS's top (the same score Activity Monitor shows as Energy Impact) for all of Chrome's processes.

One video tab multiplied Chrome's energy use about six times. That is why a single forgotten video or busy page in a background tab can drain a battery faster than twenty quiet tabs. Find that one tab first; it is usually worth more than any setting.

Why does Chrome drain a Mac battery?#

Battery use follows work. Every open tab can keep running scripts, refreshing content, animating ads and playing video, and every extension can run code on every page. Each of those wakes the processor, and a processor that keeps waking up drains the battery even when you are only reading.

Three things cost the most:

• Video, especially in formats your Mac decodes in software, and video you are not even watching in a background tab.
• Busy background tabs: live dashboards, chat apps, social feeds, pages full of animated ads.
• Extensions that inspect every page you open.

How do you see what is draining the battery?#

1. Open Activity Monitor (Applications, then Utilities) and click the Energy tab.
2. Sort by Energy Impact. Chrome often appears as Google Chrome plus several Google Chrome Helper entries.
3. Look at the 12 hr Power column too. It shows which apps cost the most over the day, not just right now.
4. Now open Chrome's task manager from the Window menu, then Task Manager, and sort by CPU. The tab or extension at the top is doing the work.

CPU is a good stand-in for energy: a row that stays busy while you are not using it is draining your battery. Our guide to Chrome high CPU usage on Mac walks through the task manager row by row.

1. Turn on Energy Saver#

Chrome's built-in Energy Saver is made for exactly this.

1. Open the three-dot menu, then Settings, then Performance.
2. Turn on Energy Saver and choose when it applies.

Google says Energy Saver works when your device is unplugged or the battery is low, and does not turn on while plugged in. It reduces background tasks and stops eligible CPU-intensive background tabs. Tabs with video calls or audio keep running. To pause it for one session, click the Energy Saver icon next to the address bar and choose Turn off now. For the video case, see Chrome high CPU usage on YouTube.

2. Let idle tabs sleep#

A tab that is asleep does no work at all. Turn on Memory Saver in the same Performance page. Chrome then deactivates tabs you have not used for a while; they stay in the tab strip and reload when clicked. See what Chrome Memory Saver does.

Memory Saver decides on its own when a tab counts as idle. If you want a fixed rule, Cleaner Pro sleeps tabs after 30 minutes without use and closes duplicate tabs in one click. It never touches the tab you are on, pinned tabs or tabs playing sound. Pro is a one-time $19.99.

3. Trim your extensions#

Go to chrome://extensions and remove anything you have not used in a month. Keep an eye on extensions that act on every page, like shopping helpers and page scanners. Chrome's task manager shows each extension's CPU; any that stays busy is costing battery. Our guide to Chrome extensions slowing down your computer has a quick way to test them.

4. Stop hidden video and animation#

• Pause or close video in background tabs. A muted video still decodes every frame.
• On news and sports sites, autoplay players and animated ads keep running. Close those tabs when you are done reading.
• For YouTube, a lower quality setting cuts decoding work a lot. See Chrome high CPU usage on YouTube.

5. Keep graphics acceleration on#

In Settings, then System, keep Use graphics acceleration when available on. With it off, drawing pages and decoding video fall on the main processor, which costs more battery. Turn it off only to troubleshoot crashes or display glitches.

6. Quit Chrome when you are done#

Closing the last window does not quit Chrome on a Mac. It keeps running, and if Continue running background apps when Google Chrome is closed is on in Settings, then System, extensions and web apps can stay active too. Press Command+Q to quit fully.

7. Use Low Power Mode on long days#

macOS has its own Low Power Mode in System Settings, then Battery. It reduces energy use across the whole Mac, Chrome included. It pairs well with Chrome's Energy Saver on flights and long days away from a charger.

8. Consider Safari for battery-critical days#

Safari is made by Apple for macOS, and Apple's MacBook battery claims are measured with Safari. If you need every last hour on a trip, doing your light browsing in Safari and keeping Chrome for the work that needs it is a reasonable split. For most days, the fixes above close much of the gap.

The bottom line#

Chrome drains a MacBook battery when tabs and extensions keep working in the background. Find the culprit in Activity Monitor and Chrome's task manager, turn on Energy Saver and Memory Saver, trim extensions, stop hidden video, and quit Chrome fully when you are done. If your Mac also feels slow, our guide to Chrome using too much memory covers the memory side of the same problem.