The Windows battery report is a snapshot and history of information supplied by the computer, firmware and battery-management system. It can help explain reduced runtime, but it is not a physical inspection or a guarantee that every value is perfectly calibrated.
How the report is generated
Open an elevated Command Prompt, run powercfg /batteryreport, and open the HTML file at the path Windows displays. The report can be viewed in any modern browser. For step-by-step instructions, see how to check battery health in Windows 11.
Computer and report information
The first section identifies the computer, operating-system build, platform role and report time. This context matters when you compare reports. A firmware or Windows update, battery replacement or reset can change what is reported.
Installed batteries
This is the most important section for a quick health check.
- Name and manufacturer identify the battery information exposed by the system. The name may be a technical part code.
- Chemistry describes the reported battery chemistry, commonly a lithium-based abbreviation.
- Design Capacity is the original reference capacity.
- Full Charge Capacity is the maximum capacity the system currently estimates.
- Cycle Count may be present when the laptop firmware exposes it.
Recent usage and battery usage
Recent usage shows power-state changes, such as active, suspended, connected standby, battery and AC operation. It is useful for reconstructing when the device was unplugged or slept. Battery usage focuses on discharge sessions and the percentage or energy consumed during those periods.
These tables are not controlled laboratory tests. A heavy video call, game or software update will consume power differently from reading a document. Compare similar workloads if you are investigating a runtime change.
Usage history and capacity history
Usage history summarizes time spent on battery and AC power over longer periods. Battery capacity history tracks reported Full Charge Capacity alongside Design Capacity. The latter is especially useful because a series of readings gives more context than one current value.
A gradual decrease is consistent with ordinary chemical aging. A sudden jump or drop can result from battery replacement, calibration changes, firmware behavior, a reporting error or a long gap in data. Generate another report before acting on a surprising single entry.
Battery-life estimates
The estimates section projects runtime based on observed battery drain, sometimes comparing current full-charge capacity with design capacity. It is an estimate, not a promise. Recent workloads can push it sharply up or down, and future use may differ.
If you want a practical runtime test, start from a known charge level and perform the same normal workload with similar brightness and connectivity. Record the time and remaining charge. Do not deliberately stress or deeply discharge a battery that shows physical warning signs.
Why fields may be blank or look wrong
- The firmware may not expose cycle count or other telemetry.
- A battery replacement can make historic and current entries look inconsistent.
- Capacity estimation can shift after different charging patterns or firmware updates.
- Locale formatting may change commas, periods and date formats.
- A desktop computer or device without a recognized battery may not produce useful battery data.
A Full Charge Capacity above Design Capacity is not automatically proof of a better-than-new battery. It may reflect replacement hardware, conservative design values or imperfect reporting. If the ratio is far above 100%, confirm it in another report and the manufacturer's diagnostic utility.
Turn the report into an action
| Observation | Reasonable next step |
|---|---|
| Stable capacity and acceptable runtime | Keep using the battery and avoid excessive heat. |
| Gradual capacity decline | Monitor occasionally and adjust expectations for unplugged runtime. |
| Sudden unexplained capacity change | Generate a fresh report; check firmware and manufacturer diagnostics. |
| Low capacity plus disruptive runtime | Compare replacement cost and obtain the correct part or service. |
| Swelling, leakage, odor, smoke or unusual heat | Stop using and charging the device; seek qualified help. |
What the report cannot prove
The report cannot visually inspect cells, rule out an internal defect, certify safety, guarantee remaining life or decide a warranty claim. Use reported capacity as one input alongside real runtime, reliability, temperature, physical condition and manufacturer guidance.
Official documentation
See Microsoft's documentation for the batteryreport command and caring for your battery in Windows.