Your Mac Battery Didn't Age Overnight — a Process Started Eating It

Your battery didn't suddenly age overnight, and a "cleaner" won't fix it. After a macOS update something usually starts eating your battery — a specific process you can name in about two minutes. Here's how to find yours, what's actually normal, and why deleting caches was never the answer.

By CoreGuard · Jun 27, 2026 · updated Jun 29, 2026 · 14 min read

▶

▶ Prefer to listen? Audio overview A podcast-style take on why your Mac battery isn’t actually dying — for the commute, not just the screen. Plays an audio file hosted on this site — no YouTube.

There's a particular kind of dread that shows up a day or two after a macOS update. The fans spin up while you're doing nothing. The lid is warm in your bag. The battery percentage drops like it's got somewhere to be. And the laptop that comfortably did a full day last week now begs for a charger by mid-afternoon. It happened again this cycle with Tahoe (macOS 26).

The instinct that follows is almost always one of two wrong moves. Either the battery is finally dying — time to price out a replacement — or the Mac needs cleaning — time to install something with a broom in its icon and let it "optimize" the problem away.

Both are wrong, and the reason they're wrong is the whole point of this piece: your battery didn't age five years over one weekend. Something started. Usually that something is a single process, it has a name, and you can find that name in about the time it takes to read this paragraph twice. No download, no faith required — the tool is already on your Mac.

Why everyone blames the wrong thing

Blaming the battery is the easy story because it fits a feeling we already have — batteries wear out, this one's a couple years old, of course it's the battery. But battery wear is slow. It shows up as a capacity that's drifted down a few percent over a year, not as a cliff that appears the night after you clicked "Update Now." macOS even has a "Battery Health" readout that can say "Service Recommended," so the story writes itself. But a sudden change has a sudden cause, and a hardware cell quietly losing capacity isn't sudden. If your runtime fell off a cliff overnight, the cliff is software, not chemistry.

The "install a cleaner" instinct is worse, because it actively points you away from the answer. Here's the plain version, the thing nobody markets to you: a cleaner does not diagnose battery drain. Deleting caches is not finding the culprit. Freeing up disk space is not the same as fixing battery health. A tool that sweeps out temp files has told you nothing about which process is awake at 3 a.m. burning watts — it can't, because that's not what it looks at. You can run one to a spotless finish and the drain will still be there the second you reboot, because the thing causing it was never a pile of junk files. It was a running program doing too much. Clearing 8 GB of caches while one daemon sits pinned at 12% CPU changes exactly nothing about your battery, except now you also have to rebuild those caches — more writes, more CPU.

So set both instincts down. The useful question isn't "is my battery bad" or "is my Mac dirty." It's "what is awake and working when it shouldn't be?" That question has an answer, and macOS will tell you for free.

The usual suspects after an update

Before the how-to, know who you're looking for. After a big release these are the names that reportedly show up most in the "why is my Mac hot" threads. Reported — I mean it. The impact varies a lot by machine, and whether any of these is your drain is exactly the thing you're about to check, not assume. Read this as who to check, not who's guilty.

• intelligenceplatformd — the daemon that coordinates Apple Intelligence's on-device models. The models need around 7 GB of disk space, and users have reported it sitting at roughly 5–15% CPU persistently with measurable heat and drain. How much it costs your Mac depends heavily on the chip and which features you've enabled. If Apple Intelligence became enabled during setup or after the update, this is a prime suspect — and you can turn it off in Settings if you decide the cost isn't worth it.
• WindowServer — the display compositor that draws everything you see. Reported to spike on CPU and energy after sleep/wake glitches, external-display weirdness, or a wallpaper change — the kind of thing a fresh OS install can stir up. Low at idle is normal; pinned high while you're doing nothing is not.
• Spotlight reindexing (mds, mds_stores, mdworker) — after an update, Spotlight rebuilds its search index, which means high CPU and disk for a while. This one is supposed to happen. It usually settles in a day or two on its own. More on it below, because it's the one people panic about needlessly.
• A nearly-full SSD — not a process, but it masquerades as one. When free space gets tight, macOS leans harder on swap and the flash controller does more garbage collection, and both burn extra CPU and power. If you're under about 10% free, fix that before you blame anything else — and if you're curious why a full SSD quietly costs you more than just space, that's its own story.
• A third-party app misbehaving — a sync client, an Electron app, a cloud-storage daemon stuck in a retry loop. Plenty of these have public threads on their own community forums about high CPU and battery on Mac. They don't care what version of macOS you're on; an update just shuffles the deck and one of them comes up wrong.

Notice what's not on that list: "the battery" and "junk files." The suspects are all processes (or one tired disk) — and every one of them is visible. You don't need to guess. You can watch it.

How to find yours in two minutes

Here's the payoff. You don't need to guess from the list above — you can watch your own machine rank its energy hogs in order.

1. Open Activity Monitor — it's in Applications › Utilities, or just hit ⌘-Space and type "Activity Monitor."
2. Click the Energy tab. This is the one that matters for battery; Apple built this exact view for this exact question.
3. Click the "Energy Impact" column header to sort, biggest first.

The thing at the top of that list is what's spending your battery right now — not a vibe, not a guess, but a named process with a number next to it. Look at "Energy Impact" for the live picture and "12 hr Power" — the average over the last 12 hours — for whether it's a sustained drain or just a momentary blip. Then read the name, not just the number: mdworker_shared chewing energy two hours after an update is Spotlight doing its job; a browser helper or a sync daemon parked at the top for hours is a different story.

One more cross-check. Click over to the CPU tab and sort by % CPU. Energy Impact is a blend; raw CPU tells you who's actually doing work, and it's usually the same short list of names. A process pinned at 10–15% CPU while you're doing nothing is the shape of a real problem.

That's it. In under two minutes you've gone from "my battery is dying" to "com.example.helper is sitting at 14% CPU and the top of my energy list." That sentence is worth a hundred cleaner scans.

Going deeper, if you want to

If the Energy tab leaves you unsure, macOS has a sharper instrument. From Terminal:

sudo powermetrics --samplers tasks --show-process-energy -n 1

powermetrics reads low-level power counters and ranks processes by a modeled energy score — it's the layer beneath the friendly Energy tab, about as close to a wattmeter as macOS gives you, though it's still an estimate, not a literal per-process meter. It needs sudo. You don't need it for most cases, but when two processes look similar in Activity Monitor, it breaks the tie.

Then re-check after a reboot and a day

One reading is a snapshot, not a verdict. Reboot, use the Mac normally for a day, and look again. This is the discipline that separates a real diagnosis from a panic. Right after an update, mds/mdworker will be loud, and that's fine. If your top energy offender is gone after Spotlight settles and a reboot, you never had a problem — just an OS catching its breath. If the same named process is still parked at the top a day later, now you've found something real, and you can go deal with that specific app: update it, quit it, change its settings, or remove it. The delta between "right after the update" and "two days later" is where the truth lives.

What's normal, and what isn't

This part saves you from chasing ghosts, because half the battery-drain panic is a normal process mistaken for a broken one.

• Normal: Spotlight (mds/mdworker) hammering CPU and disk for a day or two after an update, then quieting down. Photos analyzing your library. A one-time burst of activity the first few hours. Fans up briefly. All of this is post-update housekeeping, and it self-resolves — give it a day or two before you conclude anything. A lot of "the update wrecked my battery" posts are written inside that window and would've resolved themselves by the weekend. Don't kill it; let it finish.
• Normal-ish: intelligenceplatformd using steady CPU if you have Apple Intelligence on and a model is resident. Annoying, arguably, but expected — and you can turn Apple Intelligence off in Settings if you decide the cost isn't worth it.
• Not normal: any single process pinned high — say 15% CPU — for days, with no end in sight and no obvious reason. A WindowServer that never calms down long after a reboot. A third-party daemon at the top of the Energy list every single time you look. Heat and fan noise that never back off even when the machine is idle. That's not the OS settling; that's something stuck, and now you've got its name, which is most of the battle.

The honest rule of thumb: temporary and decreasing is fine; sustained and flat is a problem. Time is the diagnostic. The same snapshot means one thing on update day and something very different a week later — the only way to tell which you've got is to look more than once.

What I'm building CoreGuard to do here

I started building CoreGuard because the gap above kept bothering me: macOS has the answer, but it makes you go find it, read it right, and remember to look again tomorrow — and most people understandably don't. So here's the honest version of what it does, because after a whole article telling you to distrust hand-waving, I'd be a hypocrite to hand-wave now.

CoreGuard's "What's eating your Mac" is free, and it does exactly what this article walks you through by hand: it names the actual top app or process burning your CPU, RAM, or energy right now, in plain English, and tells you why the Mac is hot or loud — "this is Spotlight indexing, it'll settle" versus "this app is parked at the top and shouldn't be." There's a free one-tap "Open Activity Monitor" shortcut right next to it, because I'd rather point you at the real tool than hide it. The battery-health status is free too, and CoreGuard keeps a history of readings with threshold alerts — so "this started three days ago, right after the update" becomes something you can see on a chart instead of something you'd have had to be staring at the moment it began. Knowing something's wrong is never paywalled; that's the rule.

What Pro adds is the deeper accounting: per-app energy analytics — which apps had the highest energy impact over time, not just this instant — plus the longer history and exportable trends. That's the power-user layer, the portable proof, not the knowledge that something's off.

And the honest part, the part I won't blur: CoreGuard observes and explains. It does not clean, optimize, speed up, or repair anything, and it will not improve your battery life — it tells you what's spending it, by name. It doesn't fix the update or fix the battery. It's local-only — zero network connections, no account, no telemetry — and you don't have to take my word for it: with CoreGuard running, lsof -i -nP | grep CoreGuard returns nothing, because there are no open network sockets to find. It's notarized and Developer-ID signed by Apple. It's a sharper, always-watching version of the Activity Monitor walk-through above, not a magic wand, because magic wands for battery drain don't exist.

CoreGuard isn't out yet — the download and checkout go live shortly. So the honest ask: get notified and grab it free at launch, or see what Pro adds. Either way, the move tonight is free and takes two minutes: open Activity Monitor, sort the Energy tab, and read the name at the top. Then reboot, look again tomorrow, and trust the delta — not the battery, and definitely not a broom. Your battery is probably fine. Something just has a name you haven't learned yet.

Frequently asked questions