Windows Battery Report Explained: How to Read It

The Windows battery report is an HTML file generated by the built-in powercfg command. It collects battery and power information already recorded by Windows and supplied by the laptop's battery controller, firmware, and drivers. It does not run a new laboratory test, open the battery, or measure individual cells directly.

Microsoft describes the /batteryreport option as a report of battery usage characteristics over the lifetime of the system. The official powercfg command documentationMicrosoft Learn also supports a custom output file, XML output, and a duration argument for a chosen number of days.

The file is valuable because it brings several kinds of information together. You can identify the installed battery, compare its design and current capacity, review recent changes between battery and AC power, inspect recorded drains, follow capacity over time, and see runtime estimates based on observed use.

A battery report should be treated as a structured history, not a single pass-or-fail test. Its most important capacity numbers come from hardware reporting. Its usage sections reflect the activity Windows recorded. Its runtime estimates depend on prior drains and therefore change with workload. Each section answers a different question.

Select Start, search for Command Prompt, open it as administrator, and approve the permission request. Enter the standard command below and press Enter:

Windows displays the path where the HTML file was created. Open File Explorer, go to that location, and double-click the file to open it in your browser. Microsoft's Windows battery-care instructionsMicrosoft Support recommend beginning with Installed battery, Recent usage, and Battery usage.

A custom output path makes the file easier to find. The folder must already exist, and quotation marks are useful when a path contains spaces:

Replace YourName with the actual Windows account folder. You can also save to another existing folder. Do not type the example name literally unless that is your real path.

The duration option asks Windows to analyze a chosen number of days for relevant historical sections:

The command documentation also allows XML output, but HTML is the practical format for most laptop owners because it opens as a readable report. Generate a new file when comparing later data; the old HTML file does not update itself.

The top of the report identifies the system on which it was generated. Common fields include the computer name, system product name, BIOS information, operating-system build, platform role, whether Connected Standby or Modern Standby is supported, and the report time.

These fields help establish context. The model and BIOS details can be useful when comparing manufacturer support information or checking whether a firmware update applies. The operating-system build explains which Windows environment recorded the history. The report time confirms whether you are reading the latest file or an older copy.

Connected Standby support matters when investigating battery loss while the lid is closed. A supported laptop may remain in a low-power state that still permits selected activity. The battery report records broad states and drains, but a separate SleepStudy report provides more detailed Modern Standby analysis.

The overview is not a battery-health score. It is identification and configuration information that helps you interpret the sections below correctly.

Installed batteries is usually the first section to inspect. It can include the battery name, manufacturer, serial number, chemistry, Design Capacity, Full Charge Capacity, and Cycle Count. Some fields may be blank because the battery controller or firmware does not supply them.

Design Capacity is the battery's original or nominal energy reference. Full Charge Capacity is the amount the battery currently reports it can hold when fully charged. Microsoft's Windows hardware requirements define Design Capacity as the original capacity and Last Full Charge Capacity as the current full-charge value. The battery and charging requirementsMicrosoft Learn specify that supported firmware should provide accurate values in milliwatt-hours.

Cycle Count represents accumulated battery use, not simply the number of times the charger was connected. A complete cycle can be formed from several partial discharges. Windows can display the count only when the battery subsystem reports it, so a dash or blank field does not prove that the battery has never been used.

Battery chemistry codes may be abbreviated. They identify the reported chemistry but do not change the basic capacity calculation. Serial and manufacturer fields can help distinguish an original battery from a replacement, although reporting quality varies.

Use the two capacity values from the same battery:

If Design Capacity is 60,000 mWh and Full Charge Capacity is 51,000 mWh, the reported capacity health is 85%. The result means that the battery reports a current maximum equal to about 85% of the design reference. It does not mean the taskbar charge is 85%, and it does not predict exact remaining hours.

Microsoft's Design Capacity API documentationMicrosoft Learn explains that the capacity ratio uses Full Charge Capacity because that value normally changes with battery wear. It also warns that some controllers return no design value or return the same value for both fields.

Keep units consistent. Most modern Windows battery reports use mWh, but some devices can expose mAh. Never divide mAh by mWh. Conversion between charge and energy requires voltage, so use the matching values already paired by the report whenever possible.

One percentage is a snapshot. Compare later reports from the same laptop, record the raw values, and consider actual runtime and manufacturer diagnostics. A gradual decline is more meaningful than a small change between two closely timed reports.

Recent usage lists recorded changes in system state and power source. Rows can show when the laptop was Active, Suspended, or in Connected Standby, whether it was using battery or AC power, and the remaining capacity at that moment.

Use this section as a timeline. It can show when the laptop was unplugged, when charging began, when it entered a low-power state, and how the reported charge changed across those events. A sudden large change can help identify the period that needs further investigation.

The rows do not explain every process that ran. They show system states and capacity records, not a complete app-level audit. Also remember that capacity gauges are estimates and can update in steps. A large percentage change may reflect heavy use, delayed gauge correction, resume behavior, or a battery problem.

Compare the time, state, source, percentage, and mWh value together. A percentage alone can hide the size of the battery. A ten-percent drop from a large battery represents more energy than ten percent from a small one.

Battery usage presents recorded drain periods, commonly with a start time, state, duration, percentage used, and energy drained in mWh. It helps answer when the battery lost energy and how much was consumed during a recorded session.

A long active session with substantial energy use may be perfectly normal. A short session with a large drain is more interesting, but workload still matters. Gaming, rendering, video calls, software installation, high brightness, external displays, and background updates can consume energy rapidly.

The section is better for locating suspicious periods than identifying a specific application. Once you find a time with unusually high drain, compare it with Windows Settings under System, Power & battery, Battery usage, where app activity can be reviewed.

Connected Standby drains should be interpreted separately from active drains. If the laptop loses a large amount while the screen is off or the lid is closed, use SleepStudy on a supported system instead of assuming the battery capacity is the only problem.

Usage history summarizes how long the system spent active or in a supported standby state while using battery power and while connected to AC. It is a broad historical comparison rather than a detailed list of every session.

The table helps explain the laptop's lifestyle. A system that spends most of its time on AC may have limited battery runtime history. A laptop frequently used unplugged will provide more battery-duration data. Standby columns may be blank when the device does not support that state or when no relevant activity was recorded.

Do not treat total battery duration as a direct measure of health. The table combines different workloads. Several hours of document editing and one hour of gaming cannot be compared as if they use energy at the same rate.

Use Usage history to understand patterns, then use capacity history and controlled runtime tests for a clearer condition assessment.

Battery capacity history compares Full Charge Capacity with Design Capacity across recorded periods. This is one of the most useful sections for identifying a long-term trend because it shows whether the battery's reported maximum has gradually moved away from its design reference.

A slow downward pattern is consistent with normal chemical aging. A sudden large drop can follow calibration changes, firmware updates, battery replacement, controller corrections, or a real failure. Check the date of the change and compare it with system events and actual runtime.

Design Capacity should normally remain relatively stable for the same battery. If it changes sharply, confirm whether the battery was replaced, whether a second battery is present, or whether the firmware began reporting a different value. Full Charge Capacity is expected to move more because it represents the current estimate.

Missing rows or dashes mean Windows does not have usable values for those periods. Do not replace absent data with zero in your own calculation. Zero would imply no capacity, while a dash usually means unavailable information.

Battery life estimates use observed drain behavior to estimate how long the laptop might run at Full Charge Capacity and, separately, how long it might have run at Design Capacity. Some reports also show a current estimate based on observed drains since the operating-system installation.

These are workload-based estimates, not promises. If recent use involved gaming or rendering, the estimate can be short. If it involved light reading, it may be much longer. Screen brightness, apps, radios, external devices, temperature, and power mode all change the drain rate.

The difference between the Full Charge Capacity estimate and the Design Capacity estimate can illustrate the runtime effect of wear under similar observed drain assumptions. It still does not predict tomorrow's exact runtime because tomorrow's workload may be different.

Blank estimates can occur when Windows lacks enough suitable drain history or when capacity data is unavailable. Use a controlled battery test rather than trying to infer a precise result from missing rows.

A long HTML report can look complicated because it mixes identification, history, and estimates. You do not need to study every row on the first pass. Begin with Installed batteries and write down Design Capacity, Full Charge Capacity, Cycle Count, and the battery name. These values establish which battery you are evaluating and whether Windows has enough information for a capacity calculation.

Next, calculate the capacity ratio. If the result is close to the design reference, short runtime is more likely to involve power demand, settings, sleep behavior, or charging. If the result is substantially lower, reduced storage capacity is likely contributing to the symptom. Do not make a replacement decision yet; continue through the report.

Move to Capacity history and look for a trend. A gradual decline supports normal aging. A sudden step may point to recalibration, firmware, a replacement battery, or a reporting change. Then read Recent usage and Battery usage around the dates when the problem occurred. These sections show whether the laptop was active, suspended, on AC, or losing energy during a particular period.

Finish with Battery life estimates. Use them as context for observed workload, not as promised runtime. This order keeps the central question clear: how much energy can the battery hold, how has that changed, and when is the stored energy being used?

Generate the first report and keep it with a clear date in the filename. Generate another after several weeks or months using the same Windows installation and the same battery. Comparing reports created only hours apart usually reveals estimation noise rather than meaningful chemical wear.

Compare the battery name, serial information when available, Design Capacity, Full Charge Capacity, and Cycle Count. If the design value or battery identity changes, confirm whether the battery was replaced or whether the firmware began reporting a different controller. Do not compare percentages while ignoring changed source values.

Calculate the ratio from each report and record the raw capacities. For example, a change from 51,000 mWh to 50,500 mWh can look different after rounding even though the movement is small. Raw values make gradual changes easier to understand.

Compare Capacity history and actual runtime as well. A decline in the reported maximum that matches shorter controlled runtime is stronger evidence than a percentage change alone. If the report changes but runtime remains stable, allow more time and check firmware or charging-limit behavior before drawing a conclusion.

Some laptops, tablets, detachable systems, and older business models contain more than one battery. Installed batteries may list each pack separately. Capacity and wear can differ between them, so calculate each battery only from its own Design Capacity and Full Charge Capacity.

Windows can also expose an aggregate battery that represents all controllers together. Microsoft's battery information documentationMicrosoft Learn explains that a controller may be attached to the physical pack or to the device enclosure, and that aggregate reporting helps represent multiple batteries.

Do not combine raw values casually when one battery uses different units or when the report structure is unclear. A system may discharge packs in a particular order, making taskbar behavior look unusual even when the total energy is reasonable.

When one battery is much weaker than the other, manufacturer diagnostics are useful because service procedures and supported replacement parts are model-specific.

The report cannot inspect physical condition. It cannot see swelling, leakage, puncture damage, damaged insulation, cell imbalance, unusual odor, or localized heat. A normal-looking capacity number does not make a physically damaged battery safe.

It also cannot prove that the battery is the cause of every charging problem. A weak adapter, incompatible USB-C cable, damaged port, dock with insufficient wattage, motherboard charging circuit, firmware issue, or power setting can produce short runtime or unstable charging.

The report does not directly identify every application responsible for active drain. It records system usage and energy changes. Use Windows Battery usage for app-level comparison and an energy report for configuration and efficiency problems.

Finally, it cannot provide a universal replacement decision. Capacity, actual runtime, manufacturer diagnostics, warranty, device age, reliability, service cost, and the owner's mobility needs all matter.

Use the battery report when your main questions concern capacity, usage history, and runtime estimates. Use a different tool when the symptom requires more detail.

For battery loss while the laptop sleeps, a supported Modern Standby system can generate SleepStudy with:

Microsoft's SleepStudy documentationMicrosoft Learn explains that the report includes session duration, energy change, active and idle time, and the most active components.

For common energy-efficiency and configuration problems, use the energy report while the system is idle and normal programs are closed:

Use Windows Settings under System, Power & battery, Battery usage when you need app-level foreground and background information. Use Windows Security's Device performance & health page for general battery, storage, software, and system recommendations. Use the laptop manufacturer's diagnostics for model-specific error codes and service decisions.

Open the HTML file and review it before sending it to another person or uploading it to a website. The report can contain the computer name, system model, BIOS details, battery name, manufacturer, serial information when reported, timestamps, and usage history.

Submit the report only to a service whose processing and privacy explanation you understand. Do not assume a selected file stays on the device unless the site clearly states that the calculation is local and the implementation actually supports that claim.

A responsible analyzer should validate file type and size, parse uploaded HTML as untrusted data, avoid executing embedded content, and state which fields it uses. The report itself should never be treated as an instruction to run code.

When seeking public support, share only the sections needed for the question or remove identifiers where appropriate. Capacity values are often sufficient for a health calculation.

Replacement becomes more reasonable when Full Charge Capacity is consistently far below Design Capacity, capacity history shows a sustained decline, actual runtime no longer meets your needs, and manufacturer diagnostics or Windows condition information also indicate deterioration.

A lower percentage alone is not an emergency. A desk-based owner may accept reduced runtime, while a student or traveler may benefit from replacement much earlier. Confirm that high app usage, power settings, sleep drain, or an inadequate charger is not the main cause.

Sudden shutdowns, inability to operate without AC power, unstable charging, or a manufacturer error code strengthen the case for service. Use a compatible battery and the manufacturer's repair procedure, especially when the pack is internal.

Stop using and charging the laptop immediately when the battery is swollen, leaking, punctured, unusually hot, or producing an unusual odor. Microsoft advises stopping use when a battery expands beyond the device enclosure. Physical safety takes priority over report values and further testing.