How Long Should a Laptop Battery Last on a Charge?

Battery terminology causes much of the confusion.

Battery runtime is how long the laptop works between charges. Battery capacity is how much energy the battery can store. Battery health describes present condition relative to a new or design reference. Battery lifespan describes how the battery ages over months, years, and charge cycles.

Dell's current battery-performance guideDell Support makes the same distinction: runtime depends on battery capacity and operating conditions, while capacity gradually reduces as the battery chemically ages.

A laptop can therefore have:

• excellent battery health but short runtime because the hardware is power-hungry;
• reduced battery health but acceptable runtime because the workload is light;
• a large battery but disappointing runtime because the GPU is active;
• a small battery but excellent runtime because the system is extremely efficient.

For the terminology behind capacity condition, read our guide to what battery health means. If you already know your capacity percentage, use the good laptop battery health percentage guide to interpret it separately from runtime.

Laptop battery capacity is commonly described in watt-hours (Wh). A watt-hour is an amount of energy. A watt is a rate of power consumption.

That distinction lets you estimate runtime.

If a battery can deliver 60 Wh and the laptop averages 10 W, a simple energy budget suggests roughly six hours. If the same laptop averages 20 W, the estimate drops to three hours. If aggressive power saving reduces average draw to 6 W, the same 60 Wh energy budget could theoretically support around ten hours.

Windows may report battery capacity in milliwatt-hours (mWh). Microsoft's Full Charge Capacity documentationMicrosoft Learn defines Full Charge Capacity as the battery's fully charged energy capacity. Divide mWh by 1,000 to convert to Wh: 52,000 mWh equals 52 Wh.

This calculation is more useful than comparing battery percentages between different laptops. Fifty percent of a 40 Wh usable battery is about 20 Wh. Fifty percent of an 80 Wh usable battery is about 40 Wh. Both screens say 50%, but one machine may have roughly twice the stored energy before workload differences are even considered.

Manufacturer battery tests are useful when you read the methodology. They use controlled workloads, brightness, network states, software, and full discharge rather than your unpredictable daily mix.

Microsoft's current Surface testing illustrates this clearly: several 2026 Surface Laptop configurations have materially higher local-video ratings than active-web ratings under documented brightness and network conditions. Apple likewise separates video-streaming and wireless-web figures on current MacBook Air specifications.

That is the right way to read an “up to” claim: what exact task produced the number?

When comparing laptops or judging your own:

1. Match the workload as closely as possible.
2. Match display brightness.
3. Note refresh rate, resolution, and HDR settings.
4. Note whether Wi-Fi, cellular, Bluetooth, external displays, or peripherals are active.
5. Compare the battery's current usable capacity, not only the original specification.

A gaming session should not be compared with a manufacturer's local-video result.

Battery health affects runtime because capacity loss shrinks the energy budget.

Suppose a laptop originally had a 60 Wh design battery. If it now reports a 48 Wh Full Charge Capacity, it has roughly 80% of that design reference. Under the same average power draw, the available runtime would also be roughly 80% of what the new battery could provide, before accounting for estimation error and other aging effects.

For example:

• 60 Wh ÷ 10 W ≈ 6 hours;
• 48 Wh ÷ 10 W ≈ 4.8 hours.

This is why an older laptop can feel as if an identical workload suddenly uses more “percentage per hour.” Each displayed percentage point now represents less stored energy.

On Windows, Microsoft's Design Capacity documentationMicrosoft Learn explains that Full Charge Capacity relative to Design Capacity can be used to estimate battery wear when supported by the battery controller.

For a complete report walkthrough, use our Windows 11 battery health guide. You can also calculate compatible capacity values with the battery health checker.

The screen is active for much of normal laptop use, so display choices matter.

Microsoft's current Windows battery-saving guidanceMicrosoft Support recommends reducing brightness, shortening active-display time, and using efficient display settings to extend battery life. Dell's 2026 battery-performance guide similarly identifies high screen brightness as a major runtime factor.

Brightness is not the only variable. Depending on the laptop, higher refresh rates, HDR, high-resolution output, and driving additional displays can also increase total system demand.

A useful runtime test should therefore use a fixed brightness rather than “whatever looked comfortable that day.” If you test the laptop at 40% brightness today and 90% tomorrow, the two results are not directly comparable.

Processors do not consume one fixed amount of power.

During light document editing, large parts of the CPU can spend time in low-power states. During code compilation, software development builds, rendering, scientific computation, gaming, local AI inference, or heavy browser scripting, the processor can stay active for long periods. A discrete GPU can increase system power substantially when it is engaged.

That is why “I only had one program open” is not enough information. One video editor exporting a project can consume more energy than many idle browser tabs.

If a 60 Wh battery supports ten hours during a 6 W workload, the same battery would support only about two hours at a 30 W average draw in the simplified model. Nothing needs to be wrong with the battery for that difference to occur.

For Windows laptops, review Settings > System > Power & battery > Battery usage and compare per-app usage. Microsoft's guidance specifically uses that view to identify apps consuming battery in the foreground or background.

Web browsing is not one workload.

A static document page is very different from a video call, animated dashboard, browser-based game, cloud IDE, multiple live social feeds, or a site running heavy JavaScript. Background email, file synchronization, cloud photo uploads, indexing, antivirus scanning, software updates, and communication apps can add power demand even when the foreground looks quiet.

Windows Battery usage can help identify applications with high recent consumption. On a Mac, Apple's Activity Monitor Energy paneApple Support shows Energy Impact, 12 hr Power on laptops, whether an app is preventing sleep, and battery information including time remaining and recent battery level.

Instead of closing everything blindly, identify what is actually active.

Wireless radios and attached devices still belong in the runtime equation. Bluetooth accessories, weak cellular signals, USB devices, external SSDs, webcams, and bus-powered docks all need energy, while external displays can increase graphics workload.

The effect varies by device, so remove unnecessary consumers when maximum unplugged runtime matters rather than using fixed “hours lost” rules.

If the laptop behaves strangely only while connected to a dock or USB-C accessories, our USB-C laptop charging guide explains power delivery, docks, cables, and shared power budgets.

Operating systems deliberately let you trade performance for efficiency.

On Windows 11, Power mode, Energy saver, and Energy recommendations can reduce consumption. Microsoft's current Energy recommendations documentationMicrosoft Support says the page groups settings that can have an outsized impact on power consumption, with available recommendations depending on device hardware and state.

On Mac laptops, Apple's Battery settings guideApple Support includes Low Power Mode and Energy Mode options where supported.

A lower-power mode does not increase the battery's chemical capacity. It reduces the rate at which the laptop spends the energy already stored.

That distinction matters for troubleshooting. If Low Power Mode extends runtime substantially, the battery may be fine; the previous workload or performance configuration was simply expensive.

If you charge the laptop at night, close the lid, and discover 15–30% missing in the morning, that is not the same problem as getting short active runtime while working.

Sleep states, Modern Standby activity, wake events, network connectivity, peripherals, and software can consume energy while the screen is off.

Measure active runtime separately from standby loss. For Windows SleepStudy, wake sources, hibernation, and Mac sleep troubleshooting, use our laptop battery drains while sleeping guide.

Mixing the two problems can make a healthy battery look worse than it is.

A battery that lasts only four hours under a consistent heavy workload may be behaving normally. A battery that falls from 45% to 7% in seconds, shuts down at 30%, or jumps upward after reboot may have a gauge, controller, or battery-stability problem.

Do not use the Wh ÷ W runtime formula to explain discontinuous percentage behavior. That needs a different diagnostic path.

Our sudden battery percentage drop guide separates gauge calibration, capacity loss, weak cells, firmware reporting, and genuine power drain.

For a useful personal benchmark, control the variables.

Step 1: Start from a known charge level

Charge to the level you normally use. If a manufacturer charge limit intentionally stops at 80%, test from 80%; do not disable a health feature just to manufacture a bigger number.

Record the starting percentage and time.

Step 2: Fix brightness and power mode

Pick one brightness level and one Power mode. Keep them unchanged during each comparison test.

Step 3: Use a representative workload

If you are measuring “workday battery life,” do your normal work: browser, documents, messaging, coding, or meetings. If you want a repeatable test, use the same sites, video, or application sequence each time.

Step 4: Check Battery usage

Open Settings > System > Power & battery > Battery usage after the session. Note which apps consumed the largest share.

Step 5: Generate Battery Report

Run:

Open the generated HTML report and review Full Charge Capacity, recent usage, battery usage, capacity history, and available life estimates. Do not treat a single estimate as guaranteed future runtime; it is built from recorded behavior and battery data.

Step 6: Calculate observed runtime

If the laptop used 50 percentage points in four hours under a stable workload, a rough linear projection would be eight hours from 100% under similar conditions. This is only a practical estimate because workload and discharge behavior may change later in the cycle.

Repeat the same test after major setting changes. Comparing like with like is more useful than comparing your laptop with somebody else's screenshot.

Start with System Settings > Battery to review charge history and available energy settings. Use Low Power Mode if your goal is maximum runtime.

Then open Activity Monitor > Energy. Apple exposes Energy Impact for apps, 12 hr Power on Mac laptops, whether a process is preventing sleep, time on battery, estimated time remaining, and recent battery charge history.

For a repeatable test:

1. use the same brightness;
2. use the same Energy Mode;
3. disconnect unnecessary peripherals;
4. run the same workload;
5. record starting and ending percentage plus elapsed time;
6. review Activity Monitor for unusually expensive apps.

If the battery condition itself is questionable, check Battery Health separately rather than assuming an energy-hungry application proves battery degradation.

ChromeOS provides a simple built-in diagnostic path.

Google's Chromebook Diagnostics guideSource says the Battery section can display battery health, cycle count, and electrical current. Its discharge test measures the rate of charge or discharge over a fixed period.

That makes it useful for separating three ideas:

• capacity health;
• accumulated cycle history;
• current discharge behavior.

A low runtime complaint is easier to diagnose when you know whether health is poor or the current discharge rate is simply high.

A useful answer is enough runtime for your intended unplugged workload with reasonable settings and a battery in acceptable condition.

That may sound less satisfying than a universal number, but it is much more accurate.

A mobile productivity user may need an entire workday away from outlets. A gaming-laptop owner may accept much shorter battery sessions because the hardware is optimized for performance. A workstation user may care more about finishing a two-hour field job than matching a 15-hour web-browsing benchmark.

Judge the laptop against three references:

1. Its own controlled manufacturer test, understood in context.
2. Its current usable capacity, compared with design capacity.
3. Your repeatable real-world workload, measured under consistent settings.

When all three make sense together, the runtime is probably behaving normally.

New does not automatically mean efficient.

A new laptop can have a healthy battery but still use lots of power because of a high-refresh display, discrete graphics, aggressive performance settings, setup activity, cloud synchronization, indexing, or pending updates.

Before returning it for poor runtime, finish updates, restart, review per-app battery usage, choose an appropriate power mode, test at a fixed moderate brightness, and compare with a similar advertised workload. If it remains dramatically below that reference, run OEM diagnostics while return or warranty options are available.

Capacity decline is the obvious reason, but software and workloads evolve too. Applications and browser pages may use more resources, while background software accumulates.

Track Full Charge Capacity over time and compare it with actual runtime. Cycle count adds context but is not a runtime prediction; our laptop battery cycle count guide explains that distinction.

For slowing future capacity loss, see our evidence-based guide to improving laptop battery health.

Short runtime alone does not prove the battery needs replacing. First ask whether the laptop is using too much power.

Replacement becomes more reasonable when several signals agree:

• Full Charge Capacity has declined substantially;
• runtime has shortened under the same controlled workload;
• manufacturer diagnostics report degraded health or service status;
• the laptop shuts down unexpectedly on battery;
• capacity history keeps trending downward;
• the current runtime no longer meets your practical needs.

If the laptop is plugged in but cannot charge reliably, diagnose the charging path first with our laptop battery not charging guide. A healthy replacement battery will not fix an underpowered charger, failed port, damaged cable, or motherboard charging fault.

If replacement is the likely next step, the laptop battery replacement cost guide compares DIY parts, repair-shop service, OEM routes, and repair economics.

Laptop battery life is not one fixed specification. The battery supplies energy in watt-hours, while the laptop spends it at a rate measured in watts. Usable Wh divided by average W gives you the clearest mental model for runtime.

Battery health changes the usable Wh; brightness, CPU/GPU activity, apps, radios, peripherals, power mode, and sleep behavior change the watts. Measure your laptop under a repeatable workload, compare current capacity with design capacity, and inspect which applications consume energy instead of relying on a universal hour target.