If you search for a Windows battery report, you will find two very different answers. One is built into Windows itself: powercfg /batteryreport, a command that generates an HTML report of battery usage. The other is BatteryInfoView, Nir Sofer’s small freeware utility from NirSoft that shows live battery information in a window and logs it every 30 seconds. Both use the same underlying health inputs — Designed Capacity and Full Charged Capacity — but they answer different questions, at different moments, in different ways. This comparison explains exactly what each one does, how to run both, and which to reach for by use case. For the full set of head-to-heads, see our Comparisons hub.
What powercfg /batteryreport actually is
Microsoft documents /batteryreport on Microsoft Learn as an option of the powercfg command-line tool: it “Generates a report of battery usage” as an HTML file, with documented /output and /duration options. You do not download or install anything — the command ships with Windows. The resulting HTML report includes an Installed batteries section showing Design Capacity, Full Charge Capacity and Cycle Count where the battery provides them, along with capacity history and battery life estimates drawn from what Windows has recorded.
That makes batteryreport a snapshot with history. It is excellent for answering “how has this battery behaved over recent days?” and for producing a file you can save, email to IT support, or attach to a warranty conversation. What it does not do is sit open and refresh while you watch the charge move, show you a live Charge/Discharge Rate in milliwatts, or keep adding a new line every 30 seconds while you run a test discharge.
How to generate the Windows battery report — the actual steps
- Open Terminal or Command Prompt. On Windows 11, right-click Start and choose Terminal; on Windows 10, search for cmd. You do not need to change any BatteryInfoView setting to do this — the two tools are independent.
- Type
powercfg /batteryreportand press Enter. Windows writes an HTML file, by default namedbattery-report.htmlin your user folder, and prints the exact path in the window. - To control where it goes, use the documented output option, for example:
powercfg /batteryreport /output "C:\Users\YourName\Desktop\battery-report.html" - To change how many days of history the report covers, use the documented duration option, for example adding
/duration 14for 14 days. - Open the HTML file in any browser. Scroll to Installed batteries for Design Capacity, Full Charge Capacity and Cycle Count, then read the Recent usage, Battery capacity history and Battery life estimates sections below it.
Note what just happened: you ran a command, Windows compiled records it already held, and you read a static file. Close it and nothing keeps updating. Run it again tomorrow and you get a new file. That workflow is the core difference from BatteryInfoView.
What BatteryInfoView adds: live view, rate and a timed log
BatteryInfoView is a portable utility — no installation, just run BatteryInfoView.exe. Its Battery Information view (F7) refreshes every 10 seconds by default and shows 19 documented fields, including Battery Name, Manufacture Name, Power State, Current Capacity in percent and as an absolute value (usually in mWh), Full Charged Capacity, Designed Capacity, Battery Health %, Voltage, Charge/Discharge Rate, Chemistry, cycle count where the battery provides it, and four estimated time fields calculated from the change in capacity over the last 30 seconds.
Switch to the Battery Log (F8) and a new line is added every 30 seconds by default, with an extra line on suspend and on resume — so standby drain becomes visible. Since v1.20 each new log line can also be auto-saved to a comma- or tab-delimited file from Advanced Options (F9). In both views, Save Selected Items (Ctrl+S) exports to CSV, tab-delimited text, HTML or XML, or you can copy rows and paste them into a spreadsheet. If you want the tool itself, get it from our download page — the main download is the official NirSoft file via /go/batteryinfoview, described honestly as the official file.
Side-by-side comparison
| Aspect | powercfg /batteryreport | BatteryInfoView |
|---|---|---|
| Cost / install | Built into Windows, free, nothing to install | Freeware, portable, no installation — run the exe |
| Format | Static HTML report generated on demand | Live window, refreshed every 10 seconds (F7) |
| Health inputs | Design Capacity, Full Charge Capacity, Cycle Count in Installed batteries | Designed Capacity, Full Charged Capacity, Battery Health % = Full Charged ÷ Designed |
| History | Capacity history and life estimates from Windows records | Own Battery Log (F8), new line every 30 seconds, plus suspend/resume lines |
| Live rate | No live Charge/Discharge Rate view | Charge/Discharge Rate in milliwatts, updated live |
| Export | The HTML report itself is the file | Ctrl+S to CSV, tab-delimited, HTML or XML; copy to spreadsheet |
| Best moment to use | Periodic check, support evidence, trend over days | Watching a charge, discharge or drain test as it happens |
Battery health: the same maths, presented differently
Battery Health in BatteryInfoView is calculated from Full Charged Capacity divided by Designed Capacity, multiplied by 100. A new battery sits around 100% and the figure gradually decreases. batteryreport does not present that single percentage as its headline — it gives you the two capacity numbers and lets you do the same division, alongside history that BatteryInfoView does not compile on its own. Neither tool calibrates, repairs or changes the battery; both are reporting tools. For the formula in full, see Battery Health % Explained and Wear Level vs Health.
Honest verdict by use case
- You want a one-off health check to save or send: run batteryreport first. It is already on the machine and the HTML file is self-contained evidence.
- You are testing drain right now — a new app, a background process, standby loss overnight: use BatteryInfoView’s log. See the Battery Log guide for the F8 workflow.
- You want the live discharge rate in mW while you work: BatteryInfoView. batteryreport will not show it live.
- You want long-term history without leaving a program running: batteryreport, or its NirSoft companion covered in BatteryInfoView vs BatteryHistoryView.
- You want both: that is the sensible default. Generate the report monthly, keep BatteryInfoView on hand for live checks. Our export guide covers saving BatteryInfoView data in the same spirit.
There is no loser here. batteryreport is the best built-in snapshot Windows offers; BatteryInfoView is the better live instrument. If you are deciding what to install — nothing, in BatteryInfoView’s case, since it is portable — start from the download page and run the two side by side once. You will immediately see which view answers the question you actually have. More comparisons live on the Comparisons hub, and the Alternatives overview puts both in the wider landscape.
One more practical difference: repeatability
A workflow worth adopting is to make both outputs part of the same routine. Generate a batteryreport once a month and file the HTML away with its date in the filename; you build a capacity history in files you control, independent of what Windows retains. In the same sitting, open BatteryInfoView, note the Battery Health percentage and the Full Charged Capacity, and export a CSV with Ctrl+S. The two records cross-check each other: if the HTML report and the live reading disagree materially on Full Charge Capacity, something changed between the records — a calibration shift, a replaced battery, or a reading taken mid-charge — and that discrepancy itself is diagnostic. Technicians supporting several machines benefit most: the batteryreport file travels by email, while the BatteryInfoView export drops straight into a spreadsheet where a whole fleet’s health percentages can be sorted in one column. Neither workflow costs anything, neither requires installation, and together they cover the snapshot, the history and the live moment — which is why this comparison ends in “both” rather than a winner.