BatteryInfoView’s interface is in English by default, but volunteers around the world have translated it into around thirty languages — and switching is a thirty-second job involving a single small file placed next to the program. This guide explains how language packs work, where to get them, how to install one, and the one caveat that trips people up: a language pack’s version is not the program’s version.
You will need the program itself first — the official file is on the download page via /go/batteryinfoview. The rest of the series is in the Tutorials hub.
How translations work: one .ini file next to the .exe
BatteryInfoView loads its UI language from a file named batteryinfoview_lng.ini placed in the same folder as BatteryInfoView.exe. That is the whole mechanism — a fitting design for a portable program (see BatteryInfoView Portable): the translation travels with the executable, including on a USB stick, and removing the .ini file returns the interface to English. There is no language setting buried in the menus to hunt for and nothing to install.
Translators create and update these files starting from a template the program itself can generate: the /savelangfile command-line option produces the language file for translation work (documented under Translating on the official page; the full option list is in Command-Line Options). Community members translate the strings and submit the result, which is why coverage and freshness vary by language — the next sections set expectations correctly.
Which languages are available
The official product page maintains the authoritative translations table — check it for the current list, each pack’s target version, and its download link: the translations table on the official NirSoft BatteryInfoView page. As checked for this guide, the table lists around 30 community language packs, including Arabic, Bahasa Indonesia, Belarusian, Brazilian Portuguese, Bulgarian, Croatian, Czech, Dutch, French, German, Greek, Hungarian, Italian, Japanese, Korean, Persian, Polish, Romanian, Russian, Simplified Chinese, Slovak, Slovenian, Spanish, Swedish, Traditional Chinese, Thai, Turkish, Ukrainian, Valencian, and Vietnamese.
For convenience, this site also keeps a bundle mirror at /go/batteryinfoview-languages-pack — labelled honestly as what it is: a bundle mirror, not the official source. The official NirSoft table above is the primary source and the place to check which pack version you are actually getting; the mirror exists as a convenience copy and should be treated that way.
Install a language pack, step by step
- Find your language in the official translations table and note the version the pack targets (see the caveat below before choosing).
- Download the pack — from the official table link, or via the bundle mirror at /go/batteryinfoview-languages-pack if you prefer — and extract it if it arrives as an archive.
- Locate the file named
batteryinfoview_lng.iniinside the download. If the downloaded file has a different name, rename it to exactlybatteryinfoview_lng.ini. - Copy that file into the same folder as
BatteryInfoView.exe— alongside the .exe and the .chm help file. - Close BatteryInfoView if it is running, then start it again. The interface should now appear in the pack’s language.
- To revert to English at any time, delete or move the
batteryinfoview_lng.inifile and restart the program.
If the interface is still in English after these steps, check the two usual causes: the file is not in the same folder as the executable you actually launched (easy to do if you have both a 32-bit and a 64-bit copy — see where the files live), or the filename is slightly off, including a doubled extension such as .ini.txt from a text-editor save. The Troubleshooting hub covers related start-up issues in BatteryInfoView Won’t Open.
The version caveat: pack version ≠ program version
Here is the point most download pages skip. A language pack is made for a specific program version, and that version is not automatically the current one. The program is now at v1.27, but the translations table contains packs targeting versions from the earliest releases up to the present. The good news: several packs have already been updated for v1.27 — as checked for this guide, these include Bahasa Indonesia, Dutch, French, German, Hungarian, Italian, Japanese, Korean, Polish, Russian, Slovak, and Traditional Chinese. Other languages’ packs still target older versions (anywhere in the 1.00–1.26 range).
What happens if you use an older pack with v1.27? In practice, translated strings that exist in the pack are used, while anything added or changed since the pack’s version — for example the ‘Black Background’ view option label added in v1.27, or the tray and log wording changed in intervening versions — may remain in English or otherwise not match the pack. That is a cosmetic mismatch, not a functional problem: the battery data, the F7/F8 views (health check, log guide), and exports all work identically in any language. For that reason this site does not claim BatteryInfoView v1.27 is ‘available in 30 languages’ without this caveat — around thirty packs exist; only some of them target v1.27 itself. If your language’s pack lags and you can help update it, the /savelangfile route in Command-Line Options is where translators start.
Frequently asked questions
Does a language pack change the exported reports too?
Exports (Ctrl+S — see Export a Battery Report) write the field data you selected. If you are preparing a report for someone else — a support desk or a buyer — consider whether they will read it more easily with the English field names, and temporarily remove the .ini file before exporting if so.
Can I use a pack with both the 32-bit and 64-bit builds?
The mechanism is identical for both builds — the same batteryinfoview_lng.ini filename next to whichever .exe you run. If you keep both builds in different folders, each folder needs its own copy of the file.
Where do I report a translation mistake?
Translations are community work published through NirSoft’s official page, so the official translations table is the right starting point for pack details and translator credits. This site mirrors a bundle for convenience but does not maintain the packs themselves.
Next: generate a fresh language file with Command-Line Options, run the health check in your new UI language, or return to the Tutorials hub.
Checking a pack before you rely on it
Before settling on a pack, spend one minute checking it against the program you actually run. Open the official translations table and compare the pack’s stated version with your program version — v1.27 at the time of writing. If they match, you can expect the interface, including the newest v1.27 wording such as the ‘Black Background’ option, to be covered. If the pack targets an older version, expect the bulk of the interface to be translated and the newest labels to remain in English, and decide whether that mix serves your reader; for many people it is perfectly serviceable, and it never affects the battery data itself. Then, after installing, open both views — F7 Battery Information and F8 Battery Log (guide) — and confirm the field names you rely on most, such as Battery Health and the two capacity fields from the health check, read clearly in the new language before you take readings or exports for anyone else.