BatteryInfoView comes in two Windows builds, and picking between them takes about ten seconds once you know your Windows architecture. Both builds are the same tool — BatteryInfoView version 1.27 by Nir Sofer (NirSoft), displaying the same battery fields — so this is purely a matching exercise, not a feature choice. This guide gives you the exact file details, the simplest way to check your system, and what to do if you picked the wrong one.
The two downloads at a glance
| Build | Official ZIP | Size | Download link | SHA-256 of the ZIP |
|---|---|---|---|---|
| 64-bit | batteryinfoview-x64.zip | 132,819 bytes | /go/batteryinfoview | a01a2dfae2b136ade4efe88b36993256b6121db0f797a827c2b8eea16105246f |
| 32-bit | batteryinfoview.zip | 118,909 bytes | /go/batteryinfoview-32bit | be98ee432621656ce6041c962964c3e27e998cabd25b535f1102523110538af7 |
Each ZIP contains the same three items: BatteryInfoView.exe (80,384 bytes in the 32-bit package; 115,200 bytes in the 64-bit package), BatteryInfoView.chm and readme.txt. The hashes and sizes above are the self-verified values for version 1.27 from the official NirSoft files, also listed on the download page. If a copy you already have differs in size, re-download it rather than debating the build question over a suspect file.
A short history: the 64-bit build is newer
For most of its life BatteryInfoView was a 32-bit-only program. The separate native 64-bit version was added in version 1.26, alongside a Sort Log On Every Update option. Version 1.27 — the current release, from March 2026 — kept both builds and added a Black Background view option. That history matters for one practical reason: very old copies or old download pages may offer only a single file. If you want the native 64-bit build, make sure you are taking the current version 1.27 package, not an archived copy of an earlier release.
How to check whether your Windows is 64-bit or 32-bit
In general Windows terms: open Settings, go to System, then About, and look for System type. It will say either 64-bit operating system, x64-based processor or 32-bit operating system. That one line decides the download. On a 64-bit Windows, choose the 64-bit build (/go/batteryinfoview). On a 32-bit Windows, choose the 32-bit build (/go/batteryinfoview-32bit) — the 64-bit .exe cannot run on 32-bit Windows at all.
Almost every laptop running Windows 10 or Windows 11 today is 64-bit, so for most readers the answer is simply the 64-bit download. The 32-bit build still matters for older machines — remember the tool officially supports Windows from Windows 2000 through Windows 11 — and as a fallback diagnostic: the 32-bit build is the copy to try when a 64-bit copy behaves unexpectedly, as described in BatteryInfoView Wont Open.
Both builds read the same battery data
There is no data advantage to either build. Whichever you run, you get the same Battery Information view (F7) with the same 19 fields — Battery Name, capacities in mWh, Battery Health calculated as Full Charged Capacity divided by Designed Capacity, voltage, charge/discharge rate, chemistry and the conditional fields such as Serial Number, Manufacture Date and cycle count that appear only if the battery provides them — and the same Battery Log (F8) adding a line every 30 seconds by default. A health percentage taken with the 32-bit build and one taken with the 64-bit build on the same laptop at the same charge state should agree, because both are reading what the same battery reports through the same Windows.
That equivalence is useful when troubleshooting. If one build shows blank fields and the other shows full data on the same machine at the same time, suspect the copy, not the battery — re-download and verify the hash using certutil -hashfile. If both builds show the same blank field, the battery is not providing that field, and switching builds will never change it: see Cycle Count Is Blank and Manufacture Date Is Blank for those specific cases.
Which one should you keep?
- 64-bit Windows (the common case): keep the 64-bit build. It is the native match for your system.
- 32-bit Windows: keep the 32-bit build. It is your only option, and it is fully functional.
- Technicians carrying the tool on a USB stick to use on unknown machines: carry both ZIPs. Together they are under 260 KB, and you will always have the matching build.
- Archiving a verified copy: keep the ZIP itself plus its SHA-256 from the table above, so a future copy can be checked without guessing.
No installation is involved for either build: extract the ZIP and run BatteryInfoView.exe. Do not run it from inside the ZIP viewer. Removing the tool afterwards is just deleting its files. Whichever build you settle on, the program limits are identical too — it displays, logs and exports battery information (Ctrl+S to CSV, HTML, XML and other formats); it does not calibrate, repair or control charging on any build.
Still deciding because the program will not start at all? Go to BatteryInfoView Wont Open or Closes Immediately. For every other problem pattern, the Troubleshooting hub collects the guides, including the Windows-version notes in BatteryInfoView on Windows 10.
What happens if you keep both builds on one machine?
Nothing conflicts. Each build is a self-contained portable folder: extract the 32-bit ZIP to one folder and the 64-bit ZIP to another, and you can run either .exe without any installation, registration or shared settings file getting in the way. In practice most people delete the build they do not need once they have confirmed which architecture their Windows is, simply to avoid opening the wrong folder months later. If disk space is the concern, there is effectively no concern at all — the larger ZIP is 132,819 bytes, smaller than a single phone photograph. The only discipline worth keeping is labelling: rename the folders to include 32-bit or 64-bit in the folder name, keep the matching ZIP beside the extracted files, and you will never have to re-check a hash or an architecture just to know which copy you are holding. That small habit is what makes the fallback test in the wont-open guide instant instead of another download.
Frequently asked questions
Is the 64-bit version faster or more accurate?
No accuracy difference is documented or expected — both builds display the data the battery reports. Choose by architecture match, not by performance. For a utility of around 115 KB that refreshes every 10 seconds, speed is not a practical concern.
Can I run the 32-bit build on 64-bit Windows?
The 32-bit build is the standard fallback and is what to try if the 64-bit copy will not open. The reverse is not true: a 64-bit .exe cannot run on 32-bit Windows. When in doubt on a modern laptop, start with the 64-bit build.
Why are the file sizes so small — is something missing?
No. The verified ZIPs are 118,909 bytes (32-bit) and 132,819 bytes (64-bit) for version 1.27, each containing the .exe, the .chm help file and readme.txt. Small is normal for this tool. A copy claiming a very different size should be replaced from the download page.