The quit receipt
Updated 6 November 2026 · Who measures this.
The quit receipt is how WattMate checks its own promise. Before you quit an app, it names what the app is worth: a change in how long the charge lasts. A couple of minutes after you quit it, the Mac is measured again and WattMate prints what really happened, or that nothing can be claimed. The receipt right after a quit is free: what the power actually did. The minutes, before and after the quit, and the history of receipts need a key after the 10-day trial.
What does the quit receipt look like?
The projection is a pair of times rather than a percentage: 2h 21m now, 2h 36m without it. Minutes are the thing you were actually asking about, and unlike a score they can be checked afterwards.
Then the check: a couple of minutes after the app is gone, the machine is measured again and the result goes next to the promise. If the load moved for other reasons in that time, the app says so in as many words: "Over those 2 minutes the load changed for other reasons too, so the gain couldn't be measured honestly. It isn't counted toward your savings."
Why does WattMate sometimes refuse to give a number?
A tool that reports a win every time is not measuring anything. The app has a different sentence for each reason to say nothing.
| Situation | What the app says |
|---|---|
| Not enough samples yet | "The app list is ready. Naming the minutes needs a few more samples." |
| Most recent windows lack per-process readings | "Until we've measured this Mac, we can't say how much longer the charge would last." |
| Apps are not the problem | "Nothing worth quitting" |
| The app went idle | "The app has used nothing for the last few minutes, so there is nothing to quit." |
| Plugged in, on the charging card | "On the cable the charge is not being spent, so there are no minutes to count. They return when you unplug." |
| No machine to measure | "Every number here would be a zero, and a zero we cannot stand behind is worse than no number at all." |
Plugged in, the app list stays, with each app's watts and no minutes: the battery is not paying for anything, so quitting has no charge to give back.
That last one is what a virtual machine usually gets: the kernel there has no per-process energy counter, so the app declines the whole screen rather than showing a column of noughts.
Why does WattMate promise only the low end?
Under the information circle: "We show the low end of the gain: an app's power use swings from minute to minute." A promise you act on has to hold in the app's quieter minutes too, not only its busy ones, so the app shows the bottom of the range rather than the middle. If the number turns out generous, you notice. If it turns out shy, you got more than promised.
2 more rules come from the same reasoning. A projection appears only when quitting would stretch the remaining charge by a real margin rather than a rounding error. And the minutes on different rows cannot be added: "An app's minutes answer one question: what if I quit this one, now." Quitting 2 apps does not give you the sum, because the second one inherits a machine the first one already changed.
Can a single quit be verified?
Not as proof about one app. The re-measurement watches the whole machine, not the one app, because nothing in macOS reports the machine's power per process after the process is gone. Across 273 events where nothing was quit at all, the managed pool still drifted by about 3 watts either way, while a typical row promises between 0.5 and 1.5 W. Any single promise would "confirm itself" 20% of the time by chance.
So there is no verified badge on one quit, and there will not be. The app requires a much larger movement before it will show a measured result at all, and stays quiet otherwise.
Questions people ask
Why a couple of minutes and not immediately?
Because the machine takes a moment to settle after an app disappears, and because the measurement is built from windows rather than instants. Reading it too early would measure the closing, not the absence.
What if I quit the app myself, outside WattMate?
The energy already measured stays on the row, the row dims and gets a quiet "has quit" mark, and the result is recorded. The "couldn't isolate" wording belongs to the path that starts with our own button, because only there does the app know exactly when the quit happened. The App Store version has no Quit button: its sandbox does not let one app close another, so there you quit apps yourself.
Does it work while charging?
No, and that is not a limitation to work around: on mains the battery is not paying for anything, so there are no minutes to give back. The numbers return when you unplug.
Can I trust a number that low?
The low end is the point. What makes it checkable is the second half: the app comes back a couple of minutes later and tells you whether the machine agreed, including when it has to say the effect could not be separated from everything else.
How it was checked
| The 273 events | Events where nothing was quit at all, on a MacBook Pro 14″ with M3 Max, macOS 26.5.2. |
| The app list | Checked on 6 Macs under rules, thresholds and scripts published before the first counted run. On all 6, WattMate listed our test programs first (the results). |
| The wording | Every message quoted here is the app's own, compared with its source. |
What this doesn't show
- A success rate. A percentage of promises kept would need a corpus we do not yet have, and inventing one would be the failure this feature exists to avoid.
- An app's watts as such, and the battery minutes. The checks cover Apple's own power sensor, whether an app's row finds a test program and how much of the Mac's rise it carries. They do not confirm either of these.
Related: whether quitting apps saves battery at all, measured · what each app actually costs · how we count · how this compares with other apps
Get a receipt for your next quit
10 days free, no card · Requires macOS 14 or later · Apple silicon