How Windows Battery Reports Work—and How I Built a Private Browser Analyzer

Windows can create an in-depth battery report with a single command: powercfg /batteryreport. This file appears as battery-report.html and includes important data like design capacity, full charge capacity, cycle count, usage history, and battery life estimates. However, the report is filled with complex technical tables that are tough for users to understand. To make the report more accessible, I created a browser-based analyzer that displays the information without sending the file to a server.

The two most important factors in battery health are design capacity and full charge capacity. The simple capacity health percentage is calculated by dividing the full charge capacity by the design capacity and then multiplying by 100. For example, a battery with a design capacity of 50,000 mWh and a full charge capacity of 42,500 mWh would have an 85% capacity health. This figure provides important context, but it does not give a complete picture of battery health.

Battery health depends on more than just the numbers. Factors like workload, display brightness, background activity, temperature, power settings, and calibration also affect runtime. Physical warning signs such as swelling, leaking, odor, or unusual heat should never be reduced to a percentage.

Processing the battery report locally was crucial due to privacy concerns. The browser's FileReader API allows the report to be read as text and then parsed without any uploads. This method extracts only the necessary battery fields directly from the HTML file.

One challenge in creating the analyzer was dealing with variations in Windows battery reports. Robust parsing needs to handle multiple batteries, missing cycle-count values, different table structures, commas in capacity values, incomplete capacity history, and limited information exposed by firmware. Instead of relying on fixed table positions, the parser looks for known labels and normalizes the surrounding values.

When a value is missing, the interface should state that Windows did not report it instead of estimating a value.

Cycle count can be misleading. One cycle represents the use of 100% of the battery's capacity, but it does not necessarily mean a single charge from 0% to 100%. It's a supporting signal and not a universal pass-or-fail threshold. Two batteries with the same cycle count can still have different capacities, runtime, temperature history, and physical conditions. Capacity history is more informative than a single reading, as it reveals whether the decline is gradual or sudden.

The finished analyzer provides a more comprehensive view of battery health. It includes the latest health percentage, history, cycle count, and practical next steps. The tool is accessible without creating an account and works with both generated battery-report.html files and manual capacity entries. The project was documented on GitHub, and the main lesson learned was that extracting a number is easy, but explaining its limitations clearly is the real product work.