TDP and Battery-Life Math: Turning Watts into Real Playtime

Specs are marketing. Verdicts are math — and battery life is the most math-shaped spec on any handheld. "Up to 12 hours" is a real number for the lightest possible workload and a fantasy for the one you bought the device to run. This guide gives you the formula to turn watts and watt-hours into a realistic playtime band before you spend a dollar.

The one formula

Runtime, in hours, is battery capacity divided by how fast you are draining it:

runtime (h) = battery (Wh) / total system draw (W)

Two honest complications separate this from the marketing number:

1. Battery is in watt-hours (Wh), not mAh. If a spec sheet lists mAh, convert: Wh = (mAh x nominal voltage) / 1000. A "5,000 mAh" cell at 7.6 V is about 38 Wh, not "5,000" of anything useful. Compare devices in Wh or you are comparing nothing.
2. Total system draw is not the same as TDP. TDP is the processor's power budget. The screen, Wi-Fi, speakers, fans, and voltage regulators draw on top of it — call it platform overhead. On a PC handheld that overhead is roughly 4-8 W, driven mostly by screen brightness. So a "15 W TDP" session is really a ~20-23 W system draw.

Get those two right and the formula stops lying.

Worked example: an 80 Wh PC handheld

Take a large-battery Windows handheld with an 80 Wh pack (the ROG Ally X ships an 80 Wh battery, per Asus's spec sheet). Three realistic settings:

• Light 2D / emulation, ~7 W TDP: total draw ~11-13 W. 80 / 12 = ~6.5 hours.
• Balanced AAA, ~15 W TDP: total draw ~20-23 W. 80 / 22 = ~3.6 hours.
• Max performance, ~25-30 W TDP: total draw ~35-40 W. 80 / 38 = ~2.1 hours.

That is the band: not "up to 6.5 hours" as a headline, but roughly 2 to 6.5 hours depending entirely on the wattage you run. Outlets that actually meter the wall and the battery — The Phawx and Notebookcheck are the two I trust most for this — consistently land in these ranges. That is the point: the formula predicts what the reviewers measure.

Worked example: a 50 Wh OLED handheld

The Steam Deck OLED carries a 50 Wh battery (Valve's spec, up from 40 Wh on the LCD model). Same method:

• Light indie / 2D, ~6 W: total ~10-11 W. 50 / 10.5 = ~4.7 hours.
• Mid load, ~12 W: total ~17 W. 50 / 17 = ~2.9 hours.
• Near the APU cap, ~15 W: total ~22-24 W. 50 / 23 = ~2.2 hours.

Notice the OLED model's real-world win is not just capacity; the OLED panel's efficiency at moderate brightness trims that platform overhead versus the old LCD, which is why the honest battery discussion always includes the screen. Panel technology is a power spec, covered in Screen Specs Beyond Resolution.

Why the marketing number is not exactly a lie

"Up to 12 hours" usually describes a capped-framerate, low-brightness, low-TDP scenario — often a lightweight emulated system or a 2D indie with a frame cap. It is achievable. It is also not the workload most buyers have in mind, and the spec sheet never says which end of the band you will live in. The fix is to read every battery claim as "X Wh at Y watts," and to demand the TDP context. A battery figure without a TDP is not information; it is decoration — a rule we hold every review to.

Turning it into a buying decision

Two devices with the same claimed "hours" can behave completely differently:

• The bigger battery wins raw runtime at equal draw, but usually weighs more — a real ergonomics cost on long sessions.
• The more efficient chipset (a newer node, or a right-sized Android SoC instead of an x86 part) can match runtime with a smaller pack.
• A frame cap is the cheapest battery upgrade you will ever apply: capping to 40 or 30 fps lowers TDP and can push you a full band up the runtime table.

If you want to compare specific devices on efficiency rather than headline hours, the Price-per-Performance League and the best PC handheld roundup both frame performance against power. And if your goal is long battery on light systems, a lower chipset tier is not just cheaper — it sips power. Match the tier to the job with the Emulation Ceiling Finder, then run the watt-hours math above. The number you compute will sit far closer to your real playtime than any figure on the box.

The two-minute method, recapped

Before you trust any battery claim: find the pack size in Wh (convert from mAh if you must), decide the TDP you will actually run, add 4-8 W of platform overhead, and divide. You will get a band, not a single hero number — and a band is the truth. Do it for both devices you are choosing between and the winner is usually obvious. That is the whole discipline: watts in, hours out, no marketing in between.

Worked example: a retro Android handheld

Android retro handhelds change one variable and it trips people up: they use a single-cell battery at roughly 3.85 V nominal, not the ~7.6 V two-cell packs in PC handhelds. So a "5,000 mAh" retro handheld is about 5,000 x 3.85 / 1000 = ~19 Wh — half the watt-hours the raw mAh implies. This is exactly why comparing mAh across form factors is meaningless.

Run the formula on that ~19 Wh device, where the workload is emulation rather than a fixed TDP slider:

• 8/16-bit and light PS1, ~2-3 W total: 19 / 2.5 = ~7.6 hours.
• PSP/DS-class, ~4-5 W: 19 / 4.5 = ~4.2 hours.
• PS2 / GameCube-class load, ~6-8 W: 19 / 7 = ~2.7 hours.

The pattern holds: the harder the system you emulate, the harder the SoC works, the shorter the band. That is why our Anbernic RG557 review reports battery as multi-hour for 8/16-bit but notably shorter under PS2-class load, rather than a single hero figure — the workload sets the wattage, and the wattage sets the hours.