Battery Capacity, Usable Energy, and Runtime Claims Explained

A research-based guide to what watts, watt-hours, amp-hours, rated and usable energy, output, runtime, efficiency, and cycle-life claims establish—and what they do not prove.

Standards and Claims → Battery capacity and runtime claims

Evidence summary: This research-based guide uses current public measurement, transportation, battery-performance, and manufacturer sources checked through July 23, 2026. No portable power station was purchased, tested, measured, or ranked. Manufacturer specifications appear only as exact examples of how claims are formatted; they are not independent proof of delivered energy, runtime, compatibility, or superiority.

Evidence checked: July 23, 2026
Manufacturer examples checked: July 23, 2026
Prices and affiliate programs: Not applicable
Hands-on testing or runtime modeling: Not performed

Quick answer

Watts and watt-hours answer different questions. A watt (W) is power—the rate at which energy is being used or delivered. A watt-hour (Wh) is an amount of energy. Amp-hours (Ah) describe charge and need a voltage before they can be converted into a nominal Wh figure.

A portable power station’s nameplate or rated Wh value is not automatically the amount of AC energy that will reach an appliance. System cutoffs, output path, conversion losses, standby consumption, load behavior, temperature, battery condition, and the manufacturer’s test boundary can all affect usable energy and runtime.

Continuous or rated output is also different from surge, peak, or a proprietary high-load mode. A cycle-life claim is incomplete unless it states the remaining-capacity endpoint and the test conditions. Treat runtime numbers as scenario estimates unless the exact product, load, output path, conditions, and measurement method are disclosed.

Claim decoder

Claim or unit What it can establish What it does not establish by itself Primary source example
W (watts) A power rate or output/load limit How long the battery will run NIST watt definition
Wh (watt-hours) A declared amount of battery energy Guaranteed AC energy at the outlet PHMSA nominal-energy boundary
Ah or mAh Charge capacity at a stated or implied voltage Comparable energy across packs with different voltages FAA Wh calculation guidance
Continuous or rated AC output The declared sustained AC power limit under the stated conditions Starting-load compatibility, runtime, or every port’s limit Jackery exact-model fields
Surge or peak output A declared short-duration or transient power capability Continuous operation or compatibility without duration/load details EcoFlow exact-model fields
Proprietary high-load mode A manufacturer-defined operating mode The same behavior as normal continuous or surge output EcoFlow X-Boost field
Cycle life A declared number of cycles to a stated remaining-capacity threshold Full original capacity for that many cycles, calendar life, or warranty coverage Jackery endpoint example
Runtime estimate A result for a stated model and assumptions Guaranteed duration for a different load, temperature, battery age, or output path BLUETTI UK formula example

Watts are power; watt-hours are energy

NIST defines a watt as a unit of power equal to one joule per second. Power describes a rate. Energy describes an accumulated amount.

That distinction is why these statements are not equivalent:

  • a 1,000 W output rating describes a power limit;
  • a 1,000 Wh energy rating describes a nominal amount of stored energy;
  • neither number alone establishes runtime.

The ideal unit arithmetic for a constant load is:

ideal hours = energy in Wh ÷ load in W

So 1,000 Wh divided by a perfectly constant 100 W load equals 10 ideal hours as a unit calculation. It is not a real-product runtime claim. Using the nameplate Wh value as delivered energy silently assumes away system cutoffs, conversion losses, standby consumption, changing loads, temperature, and battery condition.

Amp-hours need voltage before comparison

The FAA explains that watt-hours are calculated by multiplying volts by amp-hours. For milliamp-hours, convert to amp-hours first.

Wh = V × Ah

This means an Ah or mAh number cannot be compared fairly across batteries unless the relevant nominal voltage is also known. A larger Ah number at a lower voltage may represent less energy than a smaller Ah number at a higher voltage.

A current manufacturer example makes the relationship visible: Jackery lists the Explorer 1000 v2 as 30.4 Ah at 35.2 V DC and 1,070 Wh. Multiplying the declared nominal values gives approximately 1,070 Wh. That arithmetic checks the relationship among the listed fields; it does not measure the AC energy delivered by a unit.

Rated or nameplate energy is not the same as usable AC energy

PHMSA’s current interpretation of the lithium-battery transport rules describes nominal energy or the Wh rating as an energy value determined under specified conditions and declared by the manufacturer. That is a useful boundary: the declared rating is a nameplate quantity, not a universal promise about every output path and use condition. See PHMSA interpretation 25-0021.

For a consumer decision, separate at least three layers:

  1. Declared or rated battery energy — the manufacturer’s Wh value under its specified basis.
  2. Usable battery energy — energy available between the system’s allowed upper and lower limits under a defined test.
  3. Delivered energy at an output — energy that actually reaches an AC, USB, or DC load after the relevant conversion and system overhead.

DOE/FEMP’s Battery Energy Storage System Evaluation Method bases performance evaluation on actual metered charge and discharge data. A separate performance and health test procedure treats usable energy, state of charge, standby losses, and charge/discharge rate as measured performance variables over time.

Those grid-storage methods are not portable-power-station product tests. They support a narrower conclusion: usable energy is a test result with boundaries, not a universal percentage that can be inferred from the nameplate alone.

Continuous output, surge, and proprietary modes are separate claims

Energy capacity and output power are independent specifications. Two current official product pages illustrate the difference without establishing which product is better:

These are manufacturer-declared fields for exact products. They show why a buyer should not collapse capacity, continuous output, surge, and proprietary modes into one "power" number.

Before relying on a surge or peak claim, check:

  • the duration of the peak;
  • the exact load type the manufacturer says it supports;
  • whether voltage, waveform, or another output characteristic changes in a proprietary mode;
  • per-outlet and total-output limits;
  • combined AC/DC/USB limits;
  • temperature or state-of-charge derating;
  • the manual’s prohibited loads and operating conditions.

A peak number without those details does not prove that a compressor, motor, heater, medical device, or other appliance will start and continue safely.

Runtime arithmetic is not a runtime measurement

A runtime claim needs more than Wh divided by W.

A current BLUETTI UK AC180 manufacturer FAQ publishes a model-specific reference formula that includes depth of discharge, inverter efficiency, load power, and the station’s own consumption. This is a United Kingdom regional source used only to demonstrate disclosed assumptions; it is not a specification or compatibility source for a U.S. model. The page also warns that the result is for reference and is not suitable for some compressor loads.

That example supports two important rules:

  • do not apply one product’s assumed depth-of-discharge, efficiency, or self-consumption value to another product;
  • do not treat a calculation as a measurement.

For an evidence-safe runtime estimate, disclose at least:

exact product and battery condition
declared or measured usable-energy basis
AC, DC, or USB output path
average load and startup behavior
conversion-efficiency assumption
station self-consumption or standby draw
temperature and state of charge
cutoff behavior
calculation or measurement method

Low-power loads can be especially sensitive to the station’s own overhead. A 10 W internal draw is minor beside a 1,000 W appliance but material beside a 5 W router. A variable appliance may also cycle between off, running, and startup states instead of drawing one constant wattage.

Round-trip efficiency is not the same as usable discharge energy

The NREL residential battery-storage methodology defines round-trip efficiency as the ratio of useful energy output to useful energy input.

That metric includes both charging and discharging across the stated system boundary. It is not automatically:

  • the one-way AC inverter efficiency;
  • the fraction of nameplate Wh available during one discharge;
  • the efficiency of a USB or DC output;
  • a valid multiplier for every load level.

When a listing says "90% efficiency," ask what was measured:

charge-to-discharge round trip
battery-only DC efficiency
AC-to-AC system efficiency
one-way inverter efficiency
solar-controller efficiency
a peak efficiency point

Different boundaries can produce different percentages without contradiction.

Cycle-life claims need an endpoint and test conditions

Cycle-life numbers are not meaningful without the remaining-capacity threshold.

The current manufacturer examples use different endpoints:

  • Jackery states 4,000 cycles to 70%+ capacity for the Explorer 1000 v2.
  • EcoFlow states 3,000 cycles to 80+% capacity for the DELTA 2 Max.

The larger number is not automatically the better claim because the endpoints differ. A comparison also needs the charge/discharge rate, depth of discharge, temperature, rest periods, cutoff rules, and how partial cycling is counted.

NLR’s Battery Lifetime Analysis and Simulation Tool documentation notes that battery degradation is sensitive to temperature, state-of-charge history, current level, cycle depth, and cycle frequency. That supports a general caution: a laboratory cycle claim does not predict every household’s calendar life.

A cycle-life endpoint such as 70% or 80% means the battery is expected to retain that share of the stated capacity under the claim’s test basis. It does not mean the battery keeps 100% capacity until the final cycle and suddenly fails.

How to compare capacity and runtime claims fairly

Copy the exact fields into one comparison record instead of comparing headline numbers.

Field What to record
Product identity Exact model, region, revision, and checked date
Energy rating Wh, plus V and Ah when stated
Energy basis Nominal/nameplate, usable, measured, or unknown
Output path AC, regulated DC, car outlet, USB-C, or other
Continuous output Total and per-port limits
Surge/peak Magnitude, duration, load restrictions, and source
Proprietary mode Name, stated behavior, limits, and manual reference
Runtime basis Calculation or measurement; load profile and conditions
Loss assumptions DoD, efficiency, self-consumption, cutoff, temperature
Cycle life Cycle count, remaining-capacity endpoint, test conditions
Expansion Exact compatible batteries and resulting system limit
Source class Regulator, standard, manufacturer, independent test, or first-party measurement
Freshness Publication/update date and date checked

If a material field is absent, record it as unknown. Do not replace it with a category average or a different model’s value.

Red-flag claim patterns

The following phrases are not automatically false, but they need more context before they can support a buying decision:

  • "up to" runtime without a load profile and output path;
  • "surge" or "peak" without a duration;
  • "usable capacity" without a test boundary;
  • "powers almost everything" without continuous, port, and load limits;
  • "10 years" without the usage assumption and remaining-capacity endpoint;
  • "thousands of cycles" without depth, temperature, rate, and endpoint;
  • "90% efficiency" without defining the system boundary;
  • a large mAh number with no nominal voltage;
  • an expansion total without exact compatible battery models;
  • a runtime table with no statement that the values are calculated or measured.

Before trusting a runtime claim

Confirm all applicable items:

  • The exact product model and regional version are identified.
  • The capacity is stated in Wh, or V and Ah are both available.
  • The claim says whether the energy is nominal, usable, or measured at an output.
  • The output path matches the intended appliance.
  • The appliance’s normal and startup behavior are known.
  • Continuous, surge, per-port, and total-output limits are separate.
  • Any proprietary high-load mode is explained by the exact manual.
  • The runtime method identifies DoD, efficiency, self-consumption, and cutoff assumptions.
  • Temperature and battery condition are stated or treated as unknown.
  • A cycle-life claim includes its remaining-capacity endpoint.
  • A calculated value is labeled as an estimate rather than a test result.
  • The source and checked date are visible.

If the claim cannot pass this checklist, treat it as incomplete rather than rounding it into a precise runtime.

What remains unknown

This guide does not establish:

  • the usable AC energy of any individual unit;
  • the duration or compatibility of an unstated surge mode;
  • the runtime of a refrigerator, medical device, motor, heater, or other specific load;
  • the accuracy of a product display’s time-remaining estimate;
  • the current condition or state of health of a used battery;
  • whether a manufacturer cycle claim will match a particular household’s calendar life;
  • whether an expansion battery, charger, or accessory is compatible without exact documentation;
  • whether planned sizing or runtime tools are validated or public;
  • which product or capacity a reader should buy.

These are deliberate boundaries. Product choice belongs in a later category guide, sizing belongs in a separate workflow, and runtime calculation belongs in a validated method or tool.

Bottom line

Use capacity, output, runtime, efficiency, and cycle-life numbers only within their stated boundary. Preserve the exact model, region, source, checked date, output path, assumptions, and remaining unknowns. If a material field is missing, keep it unknown rather than converting a headline specification into a compatibility or runtime promise.

Related decision handoffs

Two supporting guides are already public in the current noindex pilot:

The following handoffs remain planned and intentionally unlinked:

  • Category and feature fit: choose a product class only after readiness and claim interpretation are clear.
  • Sizing: translate declared essential loads and desired duration into a defensible requirement.
  • Runtime method: use a separately validated method rather than a headline Wh/W division.
  • Alternatives: compare materially different backup approaches under one declared scenario.

Do not add a placeholder link until the target is approved, public, canonical, useful, and verified.

Method and sources

The research separated unit definitions, manufacturer-declared nominal energy, measured usable-energy concepts, output ratings, runtime assumptions, efficiency boundaries, and cycle-life wording. Material claims were normalized through a Source Registry, Claim Ledger, and Claim Sources junction.

No portable power station was purchased, borrowed, supplied, tested, or measured. Manufacturer examples are exact current claims, not independent verification or recommendations.

Key sources checked July 23, 2026:

Recheck every material source immediately before publication and before changing this public-noindex revision into an indexable release.

Next solar decision: Portable Solar Panel Buying Guide for Power-Station Charging.

EcoFlow product-line analysis