Linux battery health comes down to two numbers: what the pack can hold today and what it held when it was new. The kernel exposes both. Tools like UPower, acpi and inxi simply read them. This guide shows how to check them from the terminal.
Divide today’s figure by the design figure and you get remaining capacity as a percentage. Above 80% is healthy and below 60% usually means a replacement. Every method below works in a terminal. Most need nothing installed.
Checking your Laptop’s battery health
As mentioned above, we will discuss various CLI tools that will help us determine our device’s battery health, you can choose the method you find easiest to use:
The upower command
Perhaps the simplest method using which you can determine the Battery health and status would be the upower command. It can easily list down all the power sources which your system is using and also can manage power on your system.
In order to display the power sources, you can type the following command in your Terminal:
upower -e

The first output shows that my device is plugged in and charging, and the third entry is DisplayDevice, a composite device UPower provides for desktop battery icons. However, we are only interested in the second output which contains the information regarding our battery.
You can display the Battery related information using upower command by typing the following commands in your Terminal:
upower -i /org/freedesktop/UPower/devices/battery_BAT0

As you can see, the information such as Battery percentage, it’s vendor, state, charge cycles are displayed in a nice table. Battery Health is listed in the table as ‘Battery Capacity’ and it is currently 100% on my system.
Battery health is the capacity line. It compares energy-full (what the pack holds today) against energy-full-design (the factory figure). Percentage is a different field and only shows how charged the battery is right now.
Your battery may be BAT1 instead of BAT0, so copy the path from upower -e instead of typing it from memory. Newer UPower builds also add a -b option that prints only battery data. The openSUSE changelog lists it under release 1.90.10.
Using the ACPI command
The acpi command can also display information related to your laptop’s battery. It stands for Advanced Configuration and Power Interface. Most Linux distributions don’t ship with this command pre-installed, so you will usually need to install it using your default package manager like this:
# On Debian and Ubuntu based distributions:
sudo apt update && sudo apt install acpi
# On Arch Linux based distributions:
sudo pacman -S acpi
# On Fedora:
sudo dnf install acpi

After installation, you can check your device’s Battery health by typing the following command:
acpi -V

As you can see in the second line of the output, it says design capacity is 3580 mAh and last full capacity is 3680 mAh, which works out to about 103%. Readings a little above 100% show up on healthy packs because the firmware reports an estimate, so your battery health is currently good.
Plain acpi -b shows only charge state and time left. Add -i (acpi -bi) to get the design capacity and last full capacity line. Some firmware also makes acpi warn that the battery will never fully charge while it charges fine, so trust the capacity figures instead.
By listing individual files
As we all know that Linux is designed in such a way that it stores everything in the form of ‘files’. Every hardware that is attached to your system is assigned a specific file. SO, technically, you can check your device’s battery health simply by listing or reading a file without installing any command.
The file/directory associated with your attached batteries is located in /sys/class/power_supply/BAT0 directory. You can list everything stored in that directory by typing:
ls /sys/class/power_supply/BAT0

As you can see, in this directory there are two files named energy_full and energy_full_design. We can just see the contents of these files in order to display the maximum charge your battery holds today and its factory design capacity, which together give your battery health.
cat /sys/class/power_supply/BAT0/energy_full
cat /sys/class/power_supply/BAT0/energy_full_design

If you want to check the health, you can just compare the both numbers. If the difference is small, then your battery is in good shape and there is too much difference, then you might want to change your device’s battery.
Some batteries expose charge_full and charge_full_design instead. Those values are in microamp-hours rather than microwatt-hours, but the ratio works the same way. Run ls /sys/class/power_supply/ first, since the battery directory can be BAT1 or even CMB0 on some laptops.
Divide energy_full by energy_full_design and multiply by 100 to get the health percentage. This one-liner does it in one step:
paste /sys/class/power_supply/BAT0/energy_full /sys/class/power_supply/BAT0/energy_full_design | awk '{ printf "%.1f%%\n", $1 / $2 * 100 }'
The paste command joins the two values onto one line and awk divides them. You get a single number such as 87.7%, which is your remaining capacity. Swap in the charge_full files if your battery uses them.
Using inxi
The inxi system information tool has a battery switch. Install it from your package manager, for example sudo apt install inxi on Debian and Ubuntu, then run the command below. The -B flag prints battery charge in Wh and a condition line that compares today’s capacity to the design figure.
inxi -B
Sample output (the values are illustrative):
Battery:
ID-1: BAT0 charge: 31.2 Wh condition: 44.1/50.0 Wh (88%)
In that sample the pack holds 44.1 Wh today against 50.0 Wh when new, so it sits near 88% health.
Using tlp-stat
TLP has a reporting command too. Run the command below to list every battery with its charge thresholds, cycle count and capacity figures, as far as the driver exposes them.
sudo tlp-stat -b
Adding -v on laptops that report mAh converts the ratings to mWh. TLP 1.10.2, released in July 2026, bases that conversion on voltage_min_design, which stands for the pack’s nominal voltage.
How to read Linux battery health numbers
Every tool above reports the same pair of values: the full charge capacity today and the design capacity. Divide the first by the second to get the health percentage. The wear level is 100 minus that number, so 82% health means 18% wear.
Do not confuse this with percentage. In upower output, percentage is the current charge while capacity is the health value. The kernel’s plain capacity file also shows charge level, so it tells you nothing about wear.
Guides draw the replacement line anywhere between 50% and 70%, so use this as a rule of thumb and judge by how long the laptop lasts on a charge:
- 80% and above: healthy, no action needed
- 60% to 80%: normal aging, plan ahead if you rely on battery power
- Below 60%: a replacement is worth considering
Cycle count adds context. UPower prints it as charge-cycles and sysfs exposes cycle_count when the driver supports it. Age matters too, since one OMG! Ubuntu writer reported 71.9% health after only 194 cycles on a six-year-old laptop.
Software cannot detect a swollen battery. If the case bulges or the trackpad lifts, stop using the laptop right away and replace the pack before you charge it again.
Why battery health readings jump around
Health percentages are estimates from battery firmware. Firmware is not always consistent. A Manjaro forum user saw 90% after a full discharge and 102% after a full recharge on the same laptop. A reply explained that the battery reports its own condition.
So compare readings taken at the same charge level and repeat them across a few weeks. In that thread upower and inxi showed the same value, while acpi phrased things differently. One odd number is rarely a reason to replace the pack.
Check battery health from a GUI
A graphical option exists if you prefer clicking. Ubuntu ships a Power Statistics app that shows the same design and full-charge values along with charge history. Search for Power Statistics in the application menu or start it from a terminal:
gnome-power-statistics
Look for Energy (design) and Energy when full, then divide as before. Flavors that leave the app out can still use the terminal methods above to get the same numbers.
Track Linux battery health over time
One reading tells you little because batteries lose capacity slowly. A weekly log shows the trend and costs almost nothing. The script below appends the date, both capacity values, the health percentage and the cycle count to a CSV file. Save it as ~/battery-log.sh:
#!/bin/bash
BAT=/sys/class/power_supply/BAT0
LOG="$HOME/battery-health.csv"
FULL=$(cat "$BAT/energy_full")
DESIGN=$(cat "$BAT/energy_full_design")
CYCLES=$(cat "$BAT/cycle_count" 2>/dev/null || echo NA)
HEALTH=$(awk -v f="$FULL" -v d="$DESIGN" 'BEGIN { printf "%.1f", f / d * 100 }')
[ -f "$LOG" ] || echo "date,energy_full,energy_full_design,health_percent,cycles" > "$LOG"
echo "$(date +%F),$FULL,$DESIGN,$HEALTH,$CYCLES" >> "$LOG"
Make the script executable and open your crontab, then add the schedule line from the second block. It runs the script every Monday at 9 AM, so replace youruser with your own username.
chmod +x ~/battery-log.sh
crontab -e
0 9 * * 1 /home/youruser/battery-log.sh
Cron only runs while the machine is awake, so a laptop that sleeps on Monday morning skips that week. That is fine for a trend line. Open the CSV in LibreOffice Calc or plot it with gnuplot.
Slow battery wear with charge limits
Charge limits help once you know your health number. OMG! Ubuntu notes that Google and Apple advise keeping batteries between roughly 10% and 90%, though the advice is debated. Many laptops now let you set a stop threshold through firmware or the kernel.
Newer UPower builds print charge-threshold-supported and the current start and end thresholds, so check there before touching sysfs:
upower -i /org/freedesktop/UPower/devices/battery_BAT0 | grep -i threshold
If charge-threshold-supported says yes, you can cap charging at 80% through sysfs. The value resets at reboot. The kernel docs also warn that a driver may accept only some values, so read the file back after writing:
echo 80 | sudo tee /sys/class/power_supply/BAT0/charge_control_end_threshold
cat /sys/class/power_supply/BAT0/charge_control_end_threshold
For a permanent limit, set the thresholds in /etc/tlp.conf and restart TLP. The TLP manual adds that availability depends on laptop vendor, kernel and TLP version.
START_CHARGE_THRESH_BAT0=70
STOP_CHARGE_THRESH_BAT0=80
Radios you never use drain power too, so disable Bluetooth on Ubuntu startup if it stays idle on your laptop.
What to do when no battery shows up
If upower -e lists only DisplayDevice and acpi says it has no support for the power supply, the kernel is not exposing a battery. That is normal in virtual machines and containers and on desktops with no internal battery. Rarely it points to a firmware fault.
Confirm with the two commands below. Only AC, USB-C or wireless peripheral entries mean no internal battery is visible. On a laptop, try a newer kernel and read the log for battery errors.
ls /sys/class/power_supply/
sudo dmesg | grep -i battery
Key Takeaways
- Battery health is full charge capacity divided by design capacity
- upower -i shows it as the capacity line
- acpi -bi and inxi -B print the same comparison
- sysfs gives energy_full and energy_full_design with no install
- Some batteries use charge_full files instead
- Percentage is charge level and not health
- Above 80% is healthy and below 60% is worth replacing
- Firmware estimates can push readings above 100%
- Log the numbers weekly to see the trend
- Charge limits slow wear where supported
Frequently asked questions
How do I check laptop battery health in Linux from the terminal?
Run upower -i on your battery path and read the capacity line. It shows full charge capacity as a percentage of design capacity. Most distributions include upower already.
What is a good battery health percentage in Linux?
Above 80% is healthy and 60% to 80% is normal ageing. Below 60% is worth replacing if you depend on battery power, though guides draw the line differently.
Why does my battery health show over 100%?
Firmware reports estimates, so a healthy battery can read slightly above its design capacity. Readings also shift with charge level, so compare values taken at the same charge.
What is the difference between percentage and capacity in upower?
Percentage is the current charge level of the battery. Capacity is battery health, calculated as energy-full divided by energy-full-design, so only capacity tells you about wear.
Does energy_full_design exist on every laptop?
No. Some batteries expose charge_full and charge_full_design in microamp-hours instead. Run ls /sys/class/power_supply/BAT0 to see which files your battery provides.
How do I check battery cycle count in Linux?
Run upower -i and read charge-cycles, or cat /sys/class/power_supply/BAT0/cycle_count. Some drivers do not expose the value, so the line can be missing.
Why does upower show no battery?
The kernel is not exposing one. That is normal in virtual machines and containers and on desktops without an internal battery, but check dmesg for firmware errors on laptops.
Conclusion
As we have already discussed above, you might want to install tools like TLPUI or Auto-CPUfreq (pick one, since Auto-CPUfreq’s own guidance is to remove TLP first) if you want to save your battery for a larger duration. Choice of distribution and desktop environment also affects the battery usage, so if you have time you can try out various Linux distributions such as Ubuntu, Fedora, Arch Linux or any of their derivative operating systems.
Auto-CPUfreq is easier to install now. Debian accepted version 3.2.0-1 into unstable on October 5, 2026, as upstream released 3.2.0.
