A Handheld’s Peak Specs Aren’t Its Sustained Performance

A handheld is a thermal and battery problem wearing a console costume, and the peak numbers on the box describe roughly the first twenty seconds of it. Every review that measures frame rates at a fixed wattage is measuring a decision the manufacturer made about heat, and every spec sheet that quotes boost clocks is quoting a state the device leaves almost immediately. The interesting number is not the peak. It is the wattage the thing settles into after the aluminium warms up.

The Budget Chain Runs From the Wall to Your Palms

An APU's thermal design power is not its power draw, it is a target the cooling solution is supposed to meet. Package power includes the CPU cores, the integrated GPU, the memory controller and the fabric between them, and it is always higher than the number in the marketing copy. Around that sit the parts nobody advertises: the display and its backlight, the LPDDR PHYs, the SSD, Wi-Fi, speakers, and the losses in the voltage regulators between the battery and the silicon, which are not free. Add them up and a fifteen-watt APU is a device pulling somewhere in the low twenties from the cell.

That single figure decides the battery life, and the arithmetic is unforgiving. Valve publishes the Steam Deck at a 40 Wh battery, and forty watt-hours divided by twenty-two watts is about one hour forty. The OLED revision's 50 Wh buys back a little over half an hour at the same draw. There is no firmware trick that beats this; there is only spending less power, which is why every handheld eventually ships a frame cap and a resolution that looks low on a spec sheet and fine in your hands.

Charging is part of the same budget. USB Power Delivery over Type-C has grown well past the 100 W the original specification allowed, and the 3.1 revision defines up to 240 W at 48 volts, which is more than enough headroom for a handheld. What matters in practice is whether the device can run at full tilt while charging without cooking itself, because charging generates heat in the same chassis that is already struggling to reject it. A handheld that throttles on the charger is telling you the thermal design is the binding constraint, not the wall adapter.

Why the Peak Clocks Are a Number You Can Measure Leaving

Boost behaviour is a timer, not a capability. Firmware allows a package to exceed its sustained power limit for a bounded window, because the heatsink has thermal mass and the user will not notice a short burst. Then the window closes and the device settles. Reviewers who benchmark a thirty-second scene are measuring the burst; reviewers who run an hour are measuring the product. The gap between those two numbers is often larger than the gap between two generations of hardware.

Physics explains why the settle is so abrupt. Dynamic power scales with capacitance, the square of voltage, and frequency, and voltage has to rise to support higher frequency, so the last fifth of the clock range costs far more than a fifth of the power. Push a chip from a comfortable operating point up to its ceiling and you buy a modest framerate with a large thermal bill. That is the entire reason handhelds ship with configurable TDP windows rather than a single number: the manufacturer is admitting that the ceiling is a user decision.

Memory bandwidth is the constraint people forget. A 128-bit LPDDR5 interface at 6400 megatransfers per second moves about 102 GB/s, shared between the CPU and an integrated GPU that has no memory of its own. Render at 1080p and the GPU will spend a meaningful share of that bandwidth on framebuffer traffic before it has fetched a single texture; render at 800p and both the fill rate and the bandwidth demand drop roughly in proportion. This is why a lower-resolution panel is a power feature and not just a cost saving, and why a 1080p panel on a seven-inch device is often a way of spending battery on pixels you cannot resolve.

How to Read the Sheet Without Being Lied To

The useful specifications are boring and usually buried:

• Sustained package power, not a boost figure and not a configurable range quoted as if it were a single value.
• Battery capacity in watt-hours. Milliamp-hours alone tells you nothing without the cell voltage, and vendors know it.
• Panel resolution and refresh range. Variable refresh lets you cap at 40 or 48 Hz without judder, which is worth more runtime than any tuning profile.
• Weight and thickness, as a proxy for heatsink mass. A thin handheld at a high sustained wattage is a handheld that gets hot where your hands are.

Red flags are equally consistent: clocks described as "up to", a TDP quoted without saying whether it is sustained, no battery figure in watt-hours, and a cooling diagram that shows one fan and a vapour chamber the size of a business card. None of these are lies individually. Together they describe a device that reviews well for ninety seconds.

What I Think

The honest spec for a handheld is watt-hours consumed per hour of gameplay at a stated frame cap, and almost nobody publishes it because it would make the marketing numbers look silly. I would rather see that one figure than a teraflop count, a boost clock, or an AI-branded upscaler. If a manufacturer will not tell you the sustained wattage, the answer is that it is whatever the cooling can take, and the cooling is whatever fits in the case they designed for the price.

Which is also the buying advice: pick the device whose screen and frame target you actually want, then check that it can hold them on battery for the length of a flight. A 1080p panel that spends the trip at 25 frames per second is worse than an 800p panel locked at 40, and the person holding it will know that long before the benchmark does. The rest of the sheet is decoration.