My M1 MacBook Air used to get me through a full day of writing, browsing, and the occasional video call. Then one week it started dying by mid-afternoon. Nothing about my usage had changed. The battery health readout still said 91%.
The culprit turned out to be a single misbehaving browser tab that was pinning a CPU core at 100% in the background. Twenty minutes of investigation, one closed tab, problem solved. Here is the process, so you can do the same.
Battery health is rarely the problem
First, rule out the boring explanation. Open the battery menu (the icon in the menu bar) or go to System Settings → Battery → Battery Health. You will see a "Maximum Capacity" percentage.
Apple considers a battery healthy down to about 80% of its original capacity. Below that, you genuinely will get less runtime, and a battery replacement is worth considering. But if you are above 85% and the battery is dying fast, the battery is not your problem. Something is using power it should not.
The Energy tab in Activity Monitor
This is the tool most people never open. Activity Monitor (in /Applications/Utilities) has five tabs across the top: CPU, Memory, Energy, Disk, Network. Click Energy.
The column that matters is "Energy Impact". It is not raw CPU; it is a weighted score that accounts for how much each app is keeping the system awake and burning power. Sort by it, descending.
The usual suspects, in my experience:
- A browser tab gone rogue. An ad script in an infinite loop, a video that never stopped, a web app with a memory leak. This is the number one cause. Chrome and the browsers built on it are especially prone.
- Photos or Spotlight indexing. After importing a big batch or a system update, these run hot for a while. This is temporary - leave it overnight and it settles.
- A sync client. Dropbox, OneDrive, Google Drive, and Creative Cloud can spin for hours after you add a lot of files.
- A messaging app. Slack, Teams, and Discord are notorious for high idle energy impact. Teams in particular.
- A stuck helper process. Sometimes a background daemon from an app you are not even using crashes into a busy loop.
The "Avg Energy Impact" column tells the real story
The instantaneous Energy Impact bounces around. The column next to it, "Avg Energy Impact" (average over the last 8 hours or since the app launched), is the one to trust for finding a chronic drain. A tab that spikes for a second when you click is fine. A process averaging 40+ all day is your problem.
Right-click the offending process and you can quit it directly from Activity Monitor. If it is a browser tab, the better move is to find which tab. In Chrome and Edge, Shift-Esc opens the browser\'s own task manager, which shows per-tab CPU and memory.
Apple Silicon changes the picture slightly
On M-series Macs, work is split between performance cores (P-cores) and efficiency cores (E-cores). Light background work runs on the E-cores and barely touches the battery. This is why an M1 or M2 Mac can feel busy in Activity Monitor while sipping power.
The flip side: when something pins a P-core at 100% for hours, the battery drains noticeably. So the thing to watch is not "is the CPU busy" but "is something keeping a performance core busy when it should be idle".
A menu bar monitor that shows per-core load makes this obvious at a glance. When the P-cores are lit up and you are not doing anything demanding, that is your cue to open Activity Monitor.
The habits that actually help
Once you have killed the acute drain, a few habits keep things healthy:
- Quit apps you are not using, especially Electron apps. Slack, Discord, Teams, Notion, and friends are each a full web browser under the hood. Three of them open is three browsers running.
- Watch your browser tab count. Each tab is potential drain. Tab-suspender extensions help, or just be ruthless.
- Turn on Low Power Mode for travel days. System Settings → Battery → Low Power Mode. It caps performance slightly and noticeably extends runtime.
- Check Login Items. System Settings → General → Login Items. Apps you installed years ago may still launch helpers at startup. Prune them.
- Disconnect power-hungry peripherals. A bus-powered external SSD or a USB hub with devices attached draws from the battery. On a long flight, unplug what you do not need.
What does not help (despite the advice you will find)
- "Calibrating" the battery by fully draining and recharging. Modern lithium batteries do not need this, and deep discharges are mildly bad for them.
- Killing every background process you do not recognise. Many of them are legitimate macOS daemons. Quitting them just makes the system relaunch them, wasting energy.
- Battery "cleaner" apps that promise to extend life. The genuinely useful ones just surface the same Activity Monitor data with a nicer interface. The rest are placebo at best.
- Lowering screen brightness to 0. The display is a real power draw, but you do not need to suffer in the dark. Auto-brightness plus a comfortable level is fine.
The five-minute checkup
When my Mac battery starts misbehaving, this is the routine:
- Open Activity Monitor → Energy → sort by Avg Energy Impact.
- Anything above 30 that should not be there, investigate.
- Browser tabs: Shift-Esc to find the heavy one, close it.
- Glance at per-core load. P-cores busy while idle = something is wrong.
- If nothing obvious, reboot. A stuck daemon clears on restart more often than you would think.
Nine times out of ten the answer is a browser tab. The tenth time it is a sync client. It is almost never the battery itself, unless you are below 80% health and overdue for a replacement.