MacBook Battery Usage by App: See What Is Actually Draining Your Battery

Quick answer

macOS does not show per-app battery usage the way an iPhone does. There is no “Chrome used 22% of your battery today” screen. On a MacBook, your built-in options are the battery iconin the menu bar (which only flags apps “using significant energy”) and Activity Monitor's Energy tab, which ranks apps by an opaque score called Energy Impact.

Energy Impact is genuinely useful for sorting apps from worst to least bad. What it is notis a measurement of battery. It has no unit. It is not watts, not milliamps, not percent per hour. So when you want to answer “how much battery is this one app actually costing me,” the built-in tools run out of resolution, and you need live power draw in watts.

The two built-in ways to check battery usage by app

macOS ships two views that touch per-app battery draw. Neither is a true per-app battery accounting like the iPhone Battery screen, but together they cover most day-to-day diagnosis.

1. The battery icon in the menu bar

Click the battery percentage in your menu bar. If any app is pulling a lot of power, you will see a line that reads “Apps Using Significant Energy” with the offender listed by name. This is the fastest check, and it is the one Apple nudges you toward in its Activity Monitor energy docs.

The catch: it only fires for gross offenders. An app quietly burning three or four watts in the background will never earn a mention here, even though four watts sustained is enough to shave hours off your runtime.

2. Activity Monitor, Energy tab

Open Activity Monitor (in Applications → Utilities, or hit ⌘ + Space and type its name) and click the Energy tab. Sort by Energy Impact descending. The top of that list is your worst offender.

This is the real built-in answer to “what is draining my MacBook battery?”. It works. It is also where the built-in approach runs into its ceiling, because of what Energy Impact actually is.

What Energy Impact actually measures (and what it does not)

Energy Impact is a unitless score. macOS computes it from CPU time, GPU work, and network activity, weighted in ways Apple does not document. A score of 12 is worse than a score of 4, and that ranking is reliable. But the number itself does not mean anything you can act on.

Concretely, Energy Impact cannot tell you any of the following:

• How many watts the app is pulling right now.
• How much percentage per hour the app is costing you.
• How much battery time you would regain by quitting it.
• Whether the app is responsible for the drop you just saw, or just a slow accumulator.

This matters because the practical question is rarely “which app is worst?” — Activity Monitor answers that. The practical question is “is this app worth quitting?”, and that requires a unit. Five watts is a problem on top of an already-bright screen. One watt is not. Energy Impact gives you no way to tell which case you are in.

Watts, Energy Impact, and battery percentage, compared

There are three signals you can use to judge per-app battery usage. They answer different questions, and most people only have easy access to two of them.

The point of the table is not that Energy Impact is bad — it is the right tool for “which app should I look at first.” The point is that it stops short of “how much is this actually costing me,” and that is the question that gets asked once you have already found the suspect.

Reading the numbers while you work

The reason a unit matters is that drain is contextual. The same Chrome window pulling six watts is meaningful on top of a bright screen at a cafe and negligible on top of an external monitor at a desk with the lid closed. You cannot make that call from a score.

Once you can see live power draw, the mental model is simple. A MacBook Air battery holds roughly 50–55 watt-hours. If your whole Mac is drawing ten watts, you get about five hours. If one app is responsible for four of those watts, quitting it roughly buys back the difference. That math only works in watts.

Those ranges are why “close everything” is bad advice. The goal is not to remove every watt; it is to find the one app that is pulling the total out of the range you need. That is also where a tool like BetterBatteryMonitor earns its keep — it shows live watts and a per-app breakdown in the menu bar, so you can watch the total move as you quit things.

The apps that usually top the list

If you sort Activity Monitor by Energy Impact right now, the usual suspects are predictable. Knowing them in advance speeds up diagnosis, because you can check them first instead of scanning the whole list.

• Browsers, especially Chrome. Each tab is its own process. A page with video, ads, or heavy JavaScript can hold a core busy in the background. Safari is generally lighter, but not always.
• Electron apps— Slack, Teams, Discord, Spotify, Notion. They each bundle a copy of Chromium and keep network connections alive. Quitting them during deep work is one of the highest-leverage moves there is.
• Video calls. Zoom, Meet, and FaceTime drive the camera, microphone, encoder, and often screen sharing at once. Keep the camera off when you do not need it.
• Cloud sync. Photos, iCloud Drive, Dropbox, and Google Drive spike after large changes (a big photo import, a repo clone). They settle once the sync finishes.
• Build tools and compilers. Xcode, Docker, and anything running tests can pin the CPU for minutes at a time. Expected, but worth knowing if you are on battery.

If something you do not recognise is at the top of the list, that is worth a closer look — occasionally it is malware or a misbehaving helper process. For more on the runtime side of this, see our guide on why your MacBook's battery only lasts 2 hours, and for the health side, how to check MacBook battery health.

FAQ