A capacity number that looks impossible — higher than the battery was ever rated for, far lower than yesterday, or jumping around — naturally makes you distrust the tool. In most cases BatteryInfoView (NirSoft, version 1.27) is simply displaying the values the battery itself reports to Windows. The tool does not measure capacity with its own hardware test. This guide shows how to sanity-check what you see, how to separate a units mix-up from a real change, and how to cross-check with a second source before drawing any conclusion.
Start with the two numbers that matter
Two fields anchor almost every capacity judgement. Designed Capacity is the full capacity when the battery was completely new. Full Charged Capacity is the capacity when fully charged now. Battery Health is calculated from exactly those two values: Full Charged Capacity divided by Designed Capacity, multiplied by 100. A new battery should be around 100%, and the figure gradually decreases over time. BatteryInfoView does not invent either input — if one of those two reported values is odd, the health percentage will look odd as a direct result.
Write both numbers down exactly as shown, including the unit. By default the absolute values — Current Capacity Value, Full Charged Capacity and Designed Capacity — are usually shown in mWh (milliwatt-hours). Since version 1.22 there is also an option to display capacity in mAh, but that display works only if battery voltage is available. Mixing mWh and mAh readings between two tools is one of the most common reasons numbers appear not to match, when in fact they are describing the same battery in different units.
| Field | What it means | Common mix-up |
|---|---|---|
| Designed Capacity | Capacity when new, as reported by the battery | Comparing it to a shop listing for a different battery model |
| Full Charged Capacity | Capacity at full charge now, as reported | Reading it mid-charge and treating it as the full value |
| Current Capacity Value | Charge held right now, usually in mWh | Confusing it with Full Charged Capacity |
| Battery Health % | Full Charged / Designed x 100 | Treating an estimate or a unit error as real wear |
Cross-check with the Windows battery report
The strongest sanity check is a second reader of the same source. Windows has a built-in report: open a command prompt and run powercfg /batteryreport. The report shows Installed batteries with Design Capacity, Full Charge Capacity and Cycle Count, plus capacity history and life estimates. Compare its Design Capacity and Full Charge Capacity with the Designed Capacity and Full Charged Capacity in BatteryInfoView. A detailed side-by-side is in BatteryInfoView vs powercfg /batteryreport.
If both tools show the same unusual number, the battery or its controller is reporting that number — BatteryInfoView is not creating it. If they differ, note the time of each reading: a battery that was charging or discharging between the two checks will legitimately show a different Current Capacity, and even Full Charged Capacity can be re-estimated by the battery over time. Always compare like with like, at full charge where possible, and in the same units.
Let a full charge cycle and the log speak
A single glance is a weak test. A better observation is to let the battery complete a normal charge to full, then use it on battery power, and watch the trend. BatteryInfoView Battery Log (press F8) adds a line every 30 seconds by default with Power State, percentage capacity and related values, and it also logs on suspend and resume, so standby drain is visible too. A log line can also be saved automatically to a comma- or tab-delimited file via Advanced Options (F9). Over an hour or an afternoon, the log shows whether Current Capacity falls smoothly, whether Charge/Discharge Rate (usually in milliwatts) looks plausible for what the laptop is doing, and whether the percentage Windows shows matches the Current Capacity percentage in the tool — the official description notes that percentage is the same value Windows displays.
Do not treat that observation as a calibration procedure. Watching a charge cycle helps you judge whether readings are consistent; it does not recalibrate anything, and BatteryInfoView itself has no calibration function. If readings swing wildly within minutes while the laptop is idle on a desk, note the pattern in the log and export it (Ctrl+S saves to CSV, HTML, XML and other formats) so you have a record to show a repair shop.
Estimates are not raw readings
Four fields are explicitly estimates: Remaining battery time for the current activity, Full battery time for the current activity, Remaining time for charging, and Total time for charging (the last one only while charging). Officially, these calculated fields are based on the change in Current Capacity Value over the last 30 seconds. That is why an estimated time can change sharply when you start or stop a heavy task — the last 30 seconds suddenly look very different. A jumping estimate is not evidence that the capacity fields are wrong. Judge capacity by Designed and Full Charged Capacity; judge estimates as short-term projections that will move with your workload.
Voltage deserves the same care. Voltage is a single pack-level value in millivolts across the battery terminals. There is no per-cell voltage field and no temperature field in BatteryInfoView, so do not look for them or compare against a tool that shows them as if the fields were equivalent.
What to do when the numbers still look wrong
- Charge to full, leave the laptop plugged in briefly, then record Designed Capacity, Full Charged Capacity and Battery Health together.
- Run
powercfg /batteryreportat the same time and compare the same two capacity values in the same units. - Check whether one tool is showing mAh and the other mWh — enable or disable the mAh display consistently before comparing.
- Use the Battery Log (F8) over a real work session and look at the trend, not a single line.
- Try a fresh official copy from the download page and the other build if you suspect a damaged copy — see 32-bit vs 64-bit.
If both readers agree that Full Charged Capacity has fallen a long way from Designed Capacity, that is genuine wear information, however unwelcome. BatteryInfoView cannot fix, restore or improve a capacity reading, and no setting inside it will make a worn battery report as new. Anyone who needs a second live view can also read BatteryInfoView Shows No Data for the related case where nothing appears at all, and Cycle Count Is Blank for another field that depends entirely on what the battery provides. More checks are collected on the Troubleshooting hub.
Frequently asked questions
Full Charged Capacity is higher than Designed Capacity. Is that possible?
It can appear in reported data, which pushes Battery Health above 100%. Treat it as a reported value to cross-check with powercfg /batteryreport at full charge, not as proof the battery grew. Batteries sometimes report conservatively when new, and controllers re-estimate over time.
Why do BatteryInfoView and batteryreport show different numbers?
Check the time and the units first. Current Capacity changes minute by minute, and mAh versus mWh displays will not match numerically. Compare Design and Full Charge Capacity at the same moment, ideally at full charge.
Can BatteryInfoView correct a wrong reading?
No. It displays, logs and exports what the battery reports. It has no function to fix, calibrate or rewrite capacity values. If two independent readers agree, the reported value is the battery own figure.