Estimate device battery life from battery capacity and current draw

This device battery life estimator turns two common electrical specifications into a practical runtime figure. Enter the battery capacity in milliamp-hours and the device’s average current draw in milliamps, and the calculator returns an estimated operating time in hours. It is useful for quick planning when comparing batteries, checking a prototype’s power budget, or communicating expected runtime. The calculation is deterministic and uses the ideal capacity-over-current relationship. It does not attempt to model battery chemistry, temperature, aging, regulator losses, or changing loads, so its result should be treated as a clear first estimate rather than a guaranteed field measurement.

Understand the battery life formula

The estimate uses a direct relationship: runtime in hours equals battery capacity in milliamp-hours divided by average current draw in milliamps. The matching milliamp units cancel, leaving hours. For example, a 2400 mAh battery supporting a device that averages 120 mA produces an ideal estimate of 20 hours.

Average current is important because many devices switch between active, idle, radio-transmit, display, and sleep states. If you enter only the peak current, the estimated runtime may be much shorter than normal use; if you enter only deep-sleep current, it may be unrealistically long. Measure or calculate a time-weighted average across the expected duty cycle whenever possible.

The formula also assumes that the full rated battery capacity is usable at the device’s required voltage. Actual equipment often stops operating before a cell is completely discharged because of a cutoff voltage, converter behavior, or protection circuitry. Temperature, battery age, discharge rate, manufacturing variation, and self-discharge can reduce usable capacity as well.

This calculator intentionally leaves those factors outside the algorithm so the result remains transparent, repeatable, and easy to audit. Apply an appropriate safety margin after receiving the ideal estimate when planning a real product, maintenance interval, or customer-facing promise.

Choose and enter reliable input values

A label showing 2.4 Ah corresponds to 2400 mAh, because one amp-hour equals one thousand milliamp-hours. Both fields accept finite numeric values, but current must be greater than zero. Capacity may be zero, which produces zero hours, but it cannot be negative.

For a device with several modes, calculate average current by multiplying each mode’s current by the fraction of time spent in that mode and adding the results. For instance, a sensor drawing 80 mA for ten percent of the time and 2 mA for ninety percent averages 9.8 mA before other losses are included. Use measurements taken at the battery side of the power system if converters or regulators materially affect the load.

Avoid mixing units: values in microamps must be divided by one thousand to obtain milliamps, while values in amps must be multiplied by one thousand. Careful unit conversion and a representative average usually improve the estimate more than adding false decimal precision to the final answer.

Interpret the result and plan with margin

A result of 20 means twenty ideal hours under the supplied average load; it does not mean the device is guaranteed to run for exactly twenty hours in every environment. Compare the estimate with bench measurements and field trials before committing to service intervals or product claims. Many teams derate nominal capacity to reflect cold weather, aging, high discharge rates, voltage conversion losses, and the reserve needed for reliable shutdown.

One simple workflow is to multiply rated capacity by a conservative usable-capacity factor, then send that reduced mAh value to this estimator. Another is to calculate the ideal result first and apply a documented runtime margin afterward. Use the same policy consistently when comparing design alternatives.

Because the algorithm has no network access, randomness, stored state, or clock dependency, identical inputs always return identical results. Recalculate whenever firmware, radio schedules, display brightness, sensor sampling, or power hardware changes, since even modest changes in average current directly change expected runtime.