Energía por app
Gratis
Qué apps consumen energía, en vatios, con los números medidos separados de las estimaciones.
The problem
Your battery drains faster than it should, and Activity Monitor's Energy Impact is a relative score, not a unit. It does not tell you how many watts an app draws, or what the chip as a whole is using.
The Energy view shows watts: per app where macOS keeps a counter, and for the chip split into CPU, GPU, Neural Engine and memory where your Mac reports them. Where a number is an estimate, it says so, and an estimate never reaches a receipt.
How it works
- Read the counter. macOS keeps a running energy total for each process. Hedroom takes the difference over each scan window and adds up an app and its helpers, which gives watts.
- Mark estimates. If macOS gives no counter for an app, Hedroom shares the chip's CPU power by CPU time and shows it with "≈" and the word "estimate". An app macOS does not let Hedroom read shows no number, never 0.
- Read the chip. Chip power comes from a macOS interface Apple does not document, so Hedroom checks it works on your Mac and says so when it does not.
- Keep the battery separate. The "time left" figure uses the battery's own voltage and current, because chip power leaves out the display, the SSD and the radios.
- Use only measured values in receipts. Estimates are never stored. A receipt uses an app's own watts only when it has at least 3 measured readings before the action, and counts a change only from 0.3 W.
What you will see
On the CPU & Energy screen, the Energy tile shows battery percentage and the measured chip watts with their split. On battery it also shows what the whole Mac draws from the battery. Under "Top energy users", up to five apps are listed with watts: "1.4 W" when measured, or "≈ 1.4 W · estimate" when not. The list stays hidden until at least one app uses 0.05 W or more.
If macOS stops reporting chip power, for example after an update changes how it is reported, a card says "Energy readings paused". Memory, CPU, rules and storage keep working.
A worked example
Example, not real data
Two apps, two kinds of number
Say the top energy users list shows one app at "1.4 W" and another at "≈ 1.1 W · estimate". The first number is read from macOS's own counter for that app. The second is the chip's CPU power divided by CPU time, because macOS gave no counter for it. Idle power lands on whoever ran, so treat it as a guide.
You move the first app to the efficiency cores. Hedroom's receipt uses its measured watts and reports the change if it clears 0.3 W. For the second app, a receipt would fall back to another measure instead of building on an estimate.
Details and limits
Qué hace
- Lee los vatios por app a partir del contador de energía que macOS mantiene para cada proceso.
- Cuando macOS no da contador para una app, muestra una estimación (potencia de CPU del chip repartida por tiempo de CPU) marcada con “≈” y “estimación”.
- Muestra la potencia del chip en el mosaico de Energía, dividida en CPU, GPU, Neural Engine y memoria cuando el Mac la informa.
What it will not do
- Presentar una estimación como una medición, ni guardar una. Los comprobantes usan solo vatios medidos por app.
- Tratar los vatios del chip como consumo de batería. La cifra de “tiempo restante” usa el voltaje y la corriente de la propia batería.
Limits
- No todos los Mac informan de todos los canales de energía. Hedroom muestra lo que puede leer y deja fuera el resto.
Gratis o Pro
Ver es gratis.
Seeing where your power goes changes nothing. Moving an app to the efficiency cores is a fix, so that is Pro.
Questions people ask
Is this Activity Monitor's Energy Impact?
No. Hedroom shows watts, and never an Energy Impact score.
How much battery does reading energy use?
One read of the chip's energy counters took about 1 millisecond on the MacBook Pro it was checked on, and Hedroom reads at most once every 3.5 seconds. That is one Mac, not a promise for yours.
Why does "time left" not match the chip watts?
Chip power leaves out the display, the SSD and the radios, so pairing it with time left would overstate battery life. Time left uses the battery's own voltage and current.
Does it need a permission?
No admin password and no special permission. Per-app readings are available for processes your user account can read.