How much battery does Claude use on a Mac?
Measured 26 August 2026 · 485 completed measurement windows on one Apple silicon MacBook · 11.1 hours of running on battery between 24 and 26 August · every number below comes from that log
The question has a complication most apps don't have: on a Mac with both installed, "Claude" is two programs. There is the desktop app in /Applications, and there is Claude Code, which ships its own small application bundle inside your Library folder. macOS counts them separately, and so did we. They turned out to behave in opposite ways.
The answer: one is steady, the other spikes
Both ran in all 485 windows we measured. Chrome is in the table because it ran in the same windows on the same machine, which makes it the only fair yardstick we have:
| Claude (desktop) | Claude Code | Chrome | |
|---|---|---|---|
| Windows measured | 485 of 485 | 485 of 485 | 485 of 485 |
| Typical power while running | 2.71 W | 0.66 W | 4.21 W |
| Middle half of the time | 0.62 – 4.33 W | 0.32 – 1.45 W | 2.52 – 5.86 W |
| Busiest single window | 13.64 W | 35.04 W | 19.43 W |
| Share of everything the apps used | 17% | 4% | 32% |
| Processes held at once | median 4, peak 26 | median 3, peak 20 | median 21, peak 47 |
| Total over the period | 33.11 Wh | 20.37 Wh | 51.83 Wh |
Add the two totals and you get 53.5 Wh against Chrome's 51.8 on the same machine over the same two days. That is the number worth carrying away, and it is the only one in the table that can be added: the shares are medians and medians do not sum, so we have not summed them.
The spike is the whole story for Claude Code
Claude Code's typical reading is 0.66 W, a quarter of the desktop app's and a sixth of Chrome's. Sitting there, it costs almost nothing. Then one window averaged 35.04 W.
For scale: the median for the entire machine across those same windows was 13.93 W. So during that window one command-line tool was drawing more than two and a half typical Macs. That is what an agent working flat out looks like, and it is invisible in the median, which is exactly why a median alone is a bad way to judge an app.
We are not going to tell you what it was doing. The log records watts, paths and process counts, not tasks. "That was a long refactor" would be a story, and a plausible story is still a story.
What "Claude using significant energy" actually means
That line in the battery menu is how most people arrive here, and on this particular name it is less useful than usual. macOS lists an app while its Energy Impact stays high, and Energy Impact is a relative score with no unit — neither the threshold nor the formula is published.
Here it also cannot tell you which Claude it means. The two entries have medians four times apart and peaks that differ by a factor of two and a half in the other direction. Reading the label alone, the steady desktop app and the tool that briefly outdrew the whole machine look the same.
Why your Mac counts them as two apps
Claude Code lives at ~/Library/Application Support/Claude/claude-code/<version>/claude.app. It is a real application bundle, just not one in your Applications folder, so anything that groups processes by bundle files it separately from the desktop app — including us.
This is not a quirk of one vendor. Browsers put their renderers in helper bundles inside the app; some apps put helpers outside it entirely, and then a single product shows up under two or three names in any per-app energy list. If you are comparing tools that claim to show energy by app, this is a good thing to check: ask where the helpers live before you trust the ranking.
What this does and doesn't prove
One Mac, one run, 11.1 measured hours. The Chrome page on this site used two machines and found them disagreeing by six times about the same browser, so treat every absolute number here as this machine's, not the world's. What travels better than the numbers is the shape: a steady app, a quiet tool that spikes hard, and a name that covers both.
What we can say without hedging is that the two together were the largest single product on this machine over these two days, ahead of the browser. What we cannot say is whether that holds on yours, which is the whole reason the app exists.
Measure your own
Every number above came out of WattMate's own log on a normal working machine. Yours will differ, and the point is that you can read it rather than guess at it: the app shows what each program is drawing right now, and what quitting one would be worth in minutes.
Find the app that actually costs you
10 days free, no card · Requires macOS 14 or later · Apple silicon