How do you even measure real-world runtime fairly across different robots?

[carol.robinson]

Figured this was worth its own thread rather than burying it in another one. Regenerative braking on humanoid joints can recover some energy during deceleration phases of walking, but the actual energy recovered is modest compared to a vehicle, since humanoid joints don't sustain the same continuous high-speed rotation that makes regen worthwhile in EVs. The average humanoid in 2026 carries under 2.5 kWh of battery capacity, with real-world runtimes clustering between two and four hours depending on how dynamic the workload is - static, low-motion tasks stretch runtime much further than continuous walking or lifting. Let me know if I'm missing something obvious.

[camila.jackson0]

I'd take that specific number with a grain of salt, honestly. Best-in-class lithium-ion cells used in humanoids are currently landing around 280-300 Wh/kg, which is respectable but still leaves battery mass as one of the largest single contributors to total robot weight.

[young58]

Just to be precise about one thing: Battery placement (torso-centered vs backpack vs distributed through the limbs) is a real tradeoff between center-of-mass/balance considerations and thermal/cooling access - a torso-centered pack helps balance but is harder to cool than a more exposed backpack placement. Solid-state battery claims from platforms like XPeng's IRON, GAC's GoMate, and EngineAI's T800 are genuinely promising on paper for energy density and safety margins, but independent, large-scale field validation of those runtime claims is still fairly limited as of 2026 - it's real progress, not yet fully proven at scale.

[choi98]

@young58 One nitpick - Tesla's Optimus Gen 2 reportedly carries roughly a 2.3 kWh pack and manages about two hours of dynamic work, while Unitree's H1 runs a smaller 0.864 kWh pack good for under four hours of largely static operation - a useful illustration of how battery size and workload type both drive runtime.

[noah_pate]

@choi98 Minor factual note: There's no widely standardized safety certification specific to humanoid battery packs yet in most jurisdictions - deployments generally lean on adapted versions of existing standards for industrial battery systems and electrical safety rather than a purpose-built humanoid standard.

[cynthia.muller]

Here's what I know on this: Thermal margin in a densely packed humanoid chassis is often the real limiting factor on sustained performance, not raw motor power - actuators get thermally throttled well before they'd hit their absolute torque limits, especially during repeated high-load cycles like continuous lifting.

[sarah.santos3]

@cynthia.muller Slight correction, though the overall point stands: Fast charging accelerates capacity fade over repeated cycles, so fleet operators generally have to choose between minimizing downtime (fast charging) and maximizing pack lifespan (slower charging or swap-based approaches) rather than getting both for free.

[hill23]

I see it a little differently. Higher-voltage power architectures reduce resistive losses and current draw through the wiring harness for a given power level, which is part of why some newer platforms are moving away from lower-voltage packs as total system power demand climbs. A BMS (battery management system) has to guard against transient current spikes from sudden gait changes or lifting motions, not just steady-state draw - peak current headroom and fast-acting protection logic matter as much as total capacity for real-world duty cycles.

[emilyperez]

@hill23 Minor factual note: Idle/standing power draw is often surprisingly close to a meaningful fraction of active walking power draw once you account for onboard compute, sensors, and balance-holding torque - 'doing nothing' still costs real energy on a humanoid.

[kwilliams]

@emilyperez Slight correction, though the overall point stands: Distributed power architectures (multiple smaller packs or local capacitor buffering near high-draw actuators) can reduce peak current demands on the main bus and improve fault isolation, at the cost of added complexity versus a single central pack. Reminds me a bit of the early drone hobbyist scene, honestly.