Battery draining after the macOS 27 update?

Written 13 August 2026, before the public release of Golden Gate · we will update this page with measurements once it ships

Every autumn follows the same script: a new macOS ships, Macs update, and for a few days the battery seems worse. Some of that is real and temporary. Some of it is real and permanent — an app that hasn't caught up with the new system. And some of it is coincidence wearing the update as a disguise. The difference is measurable, and this page is about telling the three apart.

macOS 27, announced as Golden Gate at WWDC in June 2026, ships this September. It is the first macOS release for Apple silicon only — which happens to be the only hardware WattMate measures.

The first days are supposed to be expensive

Right after an upgrade the system rebuilds itself: Spotlight re-indexes the disk, photo analysis walks your library again, caches are rebuilt, apps recompile their shader and code caches on first launch. This is real energy used on real work — and it ends. On most Macs the rebuild is a matter of a day or two of ordinary use.

The catch: macOS doesn't show you this work in units you can check. Activity Monitor's Energy Impact is a number without a unit — Apple's own documentation calls it a relative measure. So "it's just indexing, give it a day" stays a guess, and three weeks later the same guess is covering for an app that actually broke.

WattMate measures power by app — real watts, not a score — and keeps history. A post-update spike you can watch shrink day by day is the system settling. A row that is as expensive on Thursday as it was on Monday is not.

How to tell whether the update is innocent

1. Wait out the rebuild — but watch it, don't take it on faith

If the expensive work is the system settling, it shrinks. Leave the Mac plugged in overnight once or twice, use it normally, and look at the same list each day. Shrinking rows are the rebuild doing its job. If nothing has shrunk after three days, stop waiting: the update is no longer the suspect, something specific is.

2. Find what got more expensive — by name

The comparison that matters is before versus after, and Activity Monitor doesn't remember yesterday. WattMate keeps its measurements, so "this app got hungrier after the update" is a check, not a feeling. Installed it only after updating? Then you won't have the before — but you will have today against tomorrow, and that answers the question that actually matters: is it settling, or is it staying?

3. Check the night

Updates change what happens while the lid is closed: indexing and analysis prefer to run when you're not looking. macOS keeps a power log of every wake-up and, most of the time, the name of the service that asked for it — almost nobody reads it. WattMate does. On the Mac we measured, across six days of that log, 204 of 206 scheduled wake-ups carried a name — and half of the total wake time belonged to Spotlight, the indexer.

4. Then decide — one quit at a time

When a specific app stays expensive, quit it while on battery and let the measurement answer. Two minutes after you quit, WattMate re-measures the Mac and prints what actually changed — or says honestly that the effect couldn't be isolated. That receipt is the difference between "I think the update ruined my battery" and "Teams got 2 W more expensive on macOS 27, quitting it gives me the minutes back, and I'm filing that bug".

When it isn't the update at all

Three look-alikes worth ruling out before blaming Golden Gate. An app shipped its own update the same week — the timing points at Apple, the watts point at the app. Battery age picked this month to show — health is a slow curve, but people check it right after updates, so updates get the blame. Or the workload changed — a new project, a new call app, an external display. In all three cases the ranked list settles the argument faster than a forum thread does.

What we haven't measured yet

Golden Gate isn't out. Everything above is the pattern every macOS release repeats; the numbers specific to macOS 27 don't exist yet — here or anywhere else. When it ships, we'll run it on battery and update this page with what we find. If a page tells you today how many watts macOS 27 costs, ask where the number came from.

And one limit we'll keep either way: macOS reports charge in whole percent, so the price of a single overnight wake-up can't be measured honestly. We say how often the Mac woke and for how long — not a made-up cost per wake.

Questions people ask

Is it normal for the battery to be worse right after updating?

For the first day or two — yes, partly. The system rebuilds indexes and caches, and that work is paid for in battery. It should visibly shrink day by day. Worse-and-staying-worse after three days is not the rebuild.

Should I quit apps to save battery after the update?

Only the ones that measurably matter. Most apps cost close to nothing in the background, and quitting them buys you nothing back. Measure first: quit the one expensive row, not everything — and check what the quit actually returned.

Does WattMate work on macOS 27?

WattMate requires macOS 15 or later on Apple silicon. We'll test on Golden Gate as it ships and post what we find here.