Battery Test

Time how long the device lasts under a load you choose. Every reading is written down as it arrives, so the result survives the device switching itself off.

About the battery test

This page times what the battery does and records every reading. It cannot tell you the health of the cell — nothing in a browser can.

Runtime, measured rather than estimated

Pick a load, start the run, and the page keeps the clock and the charge level side by side. What comes out is how long this device lasted under that load — the one battery figure a repair bench can act on.

Runs that end with the device

Every reading is stored the moment it arrives, so a run that ends in shutdown is waiting when the device comes back, finishing at the last reading before the lights went out. That is also the honest way to measure a fresh battery, whose reported percentage is worth less than the elapsed time.

What the browser cannot see

No capacity in mAh, no cycle count, no voltage, no temperature, no health percentage — none of it is exposed to a web page on any platform. Chrome and Edge report the percentage and whether the cable is in, and nothing else.

Why the load matters

"How long does it last" needs "doing what". Idle, light and heavy give three different answers, and heavy is the same load the CPU test runs. Two devices only compare under the same load, the same brightness and the same starting level.

iPhones and Firefox

Safari and Firefox removed the Battery Status API over fingerprinting, so on an iPhone the page cannot read the level — but it still holds the clock. Six readings typed in across an evening draw the same curve as six hundred.

How precise the figures are

The level arrives in whole percentage points, so at a light load one reading can be half an hour from the next. The projection follows the last fifteen minutes for that reason.

Testing the cooling too?
Load every thread from the browser and watch whether the machine holds the pace it started at.
Open the CPU test
Stress the graphics as well?
Load the GPU and watch for artifacts, driver resets and frame rates falling away.
Open the GPU test

When a battery test is worth running

Frequently asked questions

Pick the load and start the run. Chrome and Edge read the percentage themselves; other browsers ask you to enter it. Keep the tab in front with the screen on — everything is saved as it goes.
No, and neither can any other web page: health, capacity, cycle count and voltage are not exposed to a browser on any platform. What this page measures is elapsed time against charge level, which is what actually compares two devices.
Safari and Firefox removed the Battery Status API over fingerprinting. The page switches to timing the run while you enter readings by hand; the chart, the projection and the exports are unchanged.
That is the case this page is built for. Every reading is saved as it arrives, so the run is offered back when the device returns, ending at the last reading before it died.
Yes, and in front. Background tabs are throttled and a locked phone freezes the page, which stops the load as well as the recording. The page keeps the screen awake while a run is going.
It is whatever the operating system reports, in whole percentage points, and that is itself an estimate — a poor one on a new battery. The timing is exact either way, which is why running to shutdown is the reliable method.
Heavy for runtime under stress, idle to catch a device that leaks charge doing nothing, light for something in between. What matters most is using the same one every time.
Yes, on a page of its own — one tab across. The same starting level with the same charger and cable is the only way to compare two devices.
In this browser, on this device, and nowhere else. Runs live in the browser's own storage so they survive a shutdown; nothing is uploaded.