Battery Life Calculator

Introduction to battery runtime estimates

A battery is really just a fuel tank measured in charge rather than litres, and runtime is the same tank-divided-by-flow problem you would use to work out how far a car can drive. Pour milliamp-hours of stored charge into the tank, drain it at a certain number of milliamps, and the arithmetic tells you roughly how many hours you get before the tank runs dry. That single idea drives everything below, whether you are sizing a power bank for a weekend trip, checking whether a laptop survives a long meeting, or budgeting current for a battery-powered sensor left in a field for a season.

The honest caveat is that a battery never drains at one steady rate. A phone sips a few hundred milliamps while the screen is off and then gulps over a thousand the moment you open a game. This tool collapses that jagged real-world curve into a single average draw, so the number it returns is a well-reasoned planning estimate, not a stopwatch-accurate guarantee. Treat it the way you treat a fuel-economy sticker: useful for comparison and rough planning, a little optimistic under hard use.

How to use the battery life calculator

Fill in the five fields and press Estimate Runtime. Only capacity and average consumption are strictly required to get a number; voltage, reserve, and health refine it.

1. Battery capacity — read the milliamp-hour rating printed on the pack, in your device's spec sheet, or in a teardown. If you only have a watt-hour figure (common on laptops), convert it first with the formula in the next section.
2. Average consumption — the trickiest input. Pull it from a battery-monitor app, a datasheet, or a USB power meter, and match it to the activity you actually care about rather than an all-day blended average.
3. Battery voltage — leave this near your pack's nominal value (3.7 V is a good default for a single lithium cell). It only feeds the watt-hour readout, not the runtime itself.
4. Reserve — the slice you refuse to touch, such as the 15% at which you normally reach for a charger. Set it to 0 for the theoretical full-tank runtime.
5. Battery health — enter the "maximum capacity" percentage your phone or laptop reports in its settings so an aging pack is not treated as brand new.

The result panel then shows usable capacity, energy in watt-hours, and runtime broken into days, hours, and minutes, plus a one-line summary you can copy.

What each input actually means

Battery capacity (mAh) is how much charge the cell can hold. Bigger tank, longer run — everything else being equal. As a sanity check on your entry, a small IoT sensor lives around 200–1,000 mAh, most smartphones sit at 3,000–5,500 mAh, large phones and small tablets reach 5,000–8,000 mAh, and power banks run from 5,000 to 30,000 mAh and beyond. If your pack is instead labelled in watt-hours, convert with the battery voltage:

Formula: mAh = (Wh × 1000) / V

$\mathrm{mAh}=\frac{\mathrm{Wh}\times 1000}{V}$

Average consumption (mA) is the flow out of the tank, and it swings enormously with what the device is doing. Screen brightness, CPU load, and the radios — Wi‑Fi, 5G, Bluetooth — all push it up, while an idle or sleeping device draws a tiny fraction of its gaming or streaming figure. To pin down a realistic number, read it from a battery-stats app or datasheet, or convert a wattage reading with mA = watts ÷ voltage × 1000. When in doubt, pick something between your light and heavy figures rather than either extreme.

Battery voltage (V) is the pack's nominal voltage — roughly 3.6–3.8 V for a single lithium‑ion cell, or 7.2 V, 11.1 V and up for multi-cell laptop packs. Here it only converts capacity into the watt-hour energy figure and lets you compare packs on equal footing; the runtime itself comes purely from mAh divided by mA.

Reserve capacity (%) is the portion you deliberately keep untouched — an emergency buffer, or simply the level at which you always recharge. Ten to twenty percent is a common safety margin; zero gives you the full theoretical run from 100% to flat.

Battery health (%) is how much of the original capacity survives. A new cell is 100%; at 90% you effectively have 90% of the rated mAh, and at 70% your runtime is roughly a third shorter than when new. Most phones and laptops expose this figure in settings, and entering it keeps the estimate honest for an older device.

The battery life formula, step by step

The whole calculation is three short moves: shrink the tank for age, carve off the reserve you will not use, then divide by the flow rate.

First, scale the rated capacity by health so a worn pack contributes only what it can still hold:

Formula: C_health = C_rated × health / 100

$C_{\mathrm{health}}=C_{\mathrm{rated}}\times \frac{\mathrm{health}}{100}$

Next, keep only the fraction you actually plan to drain by removing the reserve percentage:

Formula: C_usable = C_health × (1 - reserve / 100)

$C_{\mathrm{usable}}=C_{\mathrm{health}}\times (1-\frac{\mathrm{reserve}}{100})$

The two percentages stack multiplicatively, which trips people up: 80% health with a 20% reserve leaves 0.8 × 0.8 = 0.64, so only 64% of the rated capacity is on the table. Finally, divide usable charge by the average current to land on hours:

Formula: Runtime_hours = C_usable / I_avg

${\mathrm{Runtime}}_{\mathrm{hours}}=\frac{C_{\mathrm{usable}}}{I_{\mathrm{avg}}}$

Because milliamp-hours divided by milliamps cancels down to hours, the units take care of themselves; multiply by 60 for minutes. The calculator also reports watt-hours as usable mAh × voltage ÷ 1000, which is handy when a device or airline quotes energy rather than charge.

Worked example: streaming video on a phone

Say you want to know how long a year-old phone lasts streaming HD video on a long flight. The phone has a 4,500 mAh battery, streaming pulls a steady 600 mA, the pack is at 90% health, and you refuse to drop below a 15% reserve. Work the three steps in order:

1. Adjust for health: 4,500 mAh × 0.90 = 4,050 mAh of real capacity.
2. Apply the reserve: 4,050 mAh × (1 − 0.15) = 4,050 × 0.85 ≈ 3,442.5 mAh you will actually spend.
3. Divide by draw: 3,442.5 mAh ÷ 600 mA ≈ 5.74 hours.

So the calculator reports roughly 5 hours 45 minutes of continuous streaming before the phone hits your 15% floor — comfortably enough for most flights, but you can see how a heavier 900 mA game would cut that to under four hours.

Reading your result — and making it more realistic

The runtime is a planning figure, so read it with a little skepticism. If it looks implausibly high, your consumption value is probably too low, or generous health and reserve settings are handing you more usable capacity than the device delivers in practice. If it looks stingy, you may have entered a worst-case draw — a gaming or video-export number — while your real day is lighter. A few habits close the gap between estimate and reality:

• Match the draw to the scenario. If gaming battery life is what you care about, measure current while gaming, not across a mixed day.
• Be honest about health. A phone several years old is rarely still at 100%; entering its real figure usually pulls the estimate toward what you observe.
• Set a reserve you actually respect. If you always plug in around 15%, model that 15% instead of assuming you drain to zero.
• Measure, then tune. Run the device under similar conditions, compare with the estimate, and nudge the consumption value until the two line up.
• Derate for anything critical. For medical, network, or remote-monitoring gear, add a safety margin on top and confirm with a real discharge test.

Typical capacities and current draw by device

The table below summarizes rough ranges for battery capacities and average current draws for common categories of devices. These are only typical values; individual models can be lower or higher.

*Runtime examples assume 100% health, 0% reserve, and a constant current draw at the heavy‑use figure.

Assumptions and limitations behind the estimate

Battery life calculations are inherently approximate. This calculator makes several simplifying assumptions that you should be aware of when interpreting the results:

• Constant average current: The calculator assumes your device draws the same average current throughout the entire discharge. Real‑world devices often fluctuate widely between idle, bursts of activity, and sleep states.
• Stable temperature: Battery capacity and efficiency decrease in extreme cold and, to a lesser extent, extreme heat. The estimate assumes normal room‑temperature conditions.
• Healthy internal resistance: As batteries age, internal resistance increases, reducing usable capacity under high load. Battery health percentage only approximates this behavior.
• Linear discharge behavior: The model effectively treats the relationship between state of charge and voltage as linear, while real batteries have a more complex discharge curve.
• No conversion losses: Many devices use voltage regulators, DC‑DC converters, or inverters which introduce efficiency losses. Those losses reduce actual runtime but are not explicitly modeled here.
• No safety margins for critical systems: For mission‑critical or safety‑critical equipment, you should apply additional safety factors and perform real‑world tests instead of relying on a simple online estimate.

Because of these limitations, the result should be viewed as a best‑effort estimate under average conditions. For planning travel, gaming sessions, or daily use, that is usually plenty. The gap tends to widen most in a handful of situations worth flagging: when load currents are very high relative to battery size, so voltage sag and internal resistance quietly eat into usable capacity; in the cold, where lithium‑ion chemistries lose a chunk of their effective capacity; on devices with aggressive power management that swing between high peaks and near-zero idle; and in multi-stage systems such as a power bank driving a laptop, where each voltage conversion stacks another efficiency loss. In those cases, lean on more conservative inputs and add an extra safety margin — or, for engineering and professional work, fall back on detailed testing and manufacturer data.