Before downloading anything, every Windows laptop already has a battery page: Settings → System → Power & battery. It shows your charge level and usage basics in a friendly, touch-ready interface. So what, honestly, does BatteryInfoView add? The short answer is depth: the two capacity values behind battery health, the health percentage itself, cycle count, live charge/discharge rate, a timed log, and exportable data. The longer answer — including where Settings is genuinely the better choice — is below. This comparison is part of our Comparisons hub.
What the Windows Settings battery page does well
The Settings battery page is designed for everyone, and it shows. You get the current charge level at a glance, battery usage presentation suited to everyday questions — is my battery draining unusually fast today, which apps have been using power — and a direct path into the power settings that actually change behaviour, such as power mode and screen/sleep timing. It needs no download, no command line and no interpretation of milliwatt-hours. For “how much charge do I have and what has been using it?”, Settings is not a cut-down tool; it is the right tool.
Its boundary is equally clear: Settings is a consumer summary. It does not present Designed Capacity and Full Charged Capacity as the headline figures, does not calculate a Battery Health percentage from them, and does not offer a live Charge/Discharge Rate in milliwatts, a 30-second logging view, or an export of raw battery fields to CSV, HTML or XML. Those are diagnostic jobs, and Microsoft leaves them to utilities and to powercfg /batteryreport — covered separately in BatteryInfoView vs powercfg /batteryreport.
What BatteryInfoView adds
BatteryInfoView (NirSoft freeware, portable, no installation) shows 19 documented battery fields in its Battery Information view (F7), refreshed every 10 seconds. The additions over Settings that matter most are: Designed Capacity (the battery’s capacity when new), Full Charged Capacity (what it holds now at full charge), Battery Health % — Full Charged divided by Designed, so wear is a single number — Current Capacity in percent and in mWh, Voltage, live Charge/Discharge Rate, Chemistry, Power State, cycle count where the battery provides it, and four estimated time fields calculated from capacity change over the last 30 seconds.
Then there is recording and output. The Battery Log (F8) adds a line every 30 seconds, and on suspend and resume, and can auto-save lines to a delimited file. Save Selected Items (Ctrl+S) exports to CSV, tab-delimited, HTML or XML, or copies rows into a spreadsheet. Settings offers no equivalent of either. Get BatteryInfoView from our download page — the main link is the official NirSoft file via /go/batteryinfoview — and follow how to check battery health with BatteryInfoView for the first reading.
Side-by-side comparison
| Aspect | Windows Settings battery page | BatteryInfoView |
|---|---|---|
| Charge level | Yes — clear, glanceable display | Yes — Current Capacity in % and mWh |
| Usage basics | Yes — usage graphs and app/power context, plus links to power settings | No app-usage view; battery hardware data only |
| Designed vs Full Charged Capacity | Not the presented focus | Yes — both values, in mWh (mAh display optional where voltage is available) |
| Battery Health % | Not calculated as a headline figure | Yes — Full Charged ÷ Designed Capacity |
| Cycle count | Not the presented focus | Yes, where the battery provides it |
| Live rate | No live mW rate view | Charge/Discharge Rate in milliwatts, live |
| Logging | No timed battery log | Battery Log (F8) every 30 seconds, suspend/resume lines, auto-save option |
| Export | No raw-data export | Ctrl+S to CSV, tab-delimited, HTML or XML |
| Install | Built in | Portable freeware, no installation |
A worked example
Suppose your three-year-old laptop feels like it lasts half as long as it used to. Settings confirms the symptom — charge falls quickly through the day — but cannot tell you whether the battery has physically worn or something is simply drawing more power. BatteryInfoView answers the wear half in one reading: if Designed Capacity is, for illustration, 56,000 mWh and Full Charged Capacity now reads 41,000 mWh, Battery Health is about 73%, meaning roughly a quarter of the original capacity is gone regardless of settings. If health instead reads near full while the rate in the log is persistently high, the problem is draw, not wear — and you are back to Settings’ usage view and power options with the right diagnosis. The formula itself is explained in Battery Health % Explained, and Designed vs Full Charged Capacity covers reading the pair. Any replace-or-not judgement remains general editorial guidance, not a feature of the tool — see When Should You Replace a Laptop Battery?
Which to use
- Everyday charge and usage questions, and changing power behaviour: Settings. It is built for this and BatteryInfoView changes no settings at all — it is read-only.
- “How worn is my battery, as a percentage?” BatteryInfoView.
- Watching drain live or logging it for evidence: BatteryInfoView’s rate and F8 log.
- Sharing battery data with support or keeping records: BatteryInfoView export, or the built-in HTML from batteryreport.
Verdict: Settings and BatteryInfoView are not rivals so much as layers. Settings is the dashboard Microsoft designed for daily use; BatteryInfoView is the instrument panel underneath it. Keep using Settings daily — and run BatteryInfoView on the days you need a number Settings does not give you. More comparisons are on the Comparisons hub and the Alternatives overview.
The settings BatteryInfoView will never change — and why that is a feature
It is worth stating plainly what sits on Settings’ side of the line, because “more data” can sound like “better tool” and mislead. Settings is where you act: power mode, sleep and screen timing, and the everyday battery controls of the machine. BatteryInfoView acts on nothing. It cannot limit a charge, switch a plan, extend runtime or fix a reading — it displays, logs and exports, and that read-only nature is precisely why it is safe to run on any machine, including one that is not yours, in a way that a settings-changing utility would not be. Diagnosis and treatment live in different places in Windows by design: BatteryInfoView (and batteryreport, and the other tools in our roundup of laptop battery health tools) handle diagnosis; Settings handles the response.
A sensible habit follows from that division. Keep Settings as your daily glance — charge level, usage, power behaviour. Once a month, or whenever runtime feels wrong, open BatteryInfoView for thirty seconds: read Battery Health, glance at Full Charged Capacity against Designed Capacity, and close it. That single percentage, trended in your head or in a saved export across a year, tells you more about your battery’s future than any amount of daily percentage-watching. And on the day the health figure and the lived runtime finally disagree with what you need from the machine, you will have the numbers to make the replacement decision calmly — which is all any of these tools, Microsoft’s included, are really for.