The quickest honest answer comes from your phone or laptop's own settings, which read the battery's real capacity. A browser can't. What a browser can do is show the live charge and how fast it falls, and our battery test does that in Chrome, Edge and Samsung Internet. Use both: the settings screen for health, the drain reading for behavior.
Battery health means how much charge the battery holds now compared with when it was new. Only the operating system can read that, because it talks to the battery's own fuel-gauge chip. Here's where each one keeps it.
| Device | Where the health figure lives | What it tells you |
|---|---|---|
| iPhone | Settings > Battery > Battery Health | Maximum capacity as a percentage of new |
| Pixel 8a and later | Settings > Battery > Battery health, then Battery capacity | Health status and estimated capacity |
| Pixel 6a to Pixel 8 Pro | Not shown, per Google | No health status |
| Samsung Galaxy | Samsung Members > Support > Phone diagnostics > Battery status | Normal, Weak or Bad |
| Windows laptop | Run powercfg /batteryreport in Command Prompt | Design capacity vs full charge capacity |
| Mac laptop | Hold Option, Apple menu > System Information > Power | Cycle count and condition |
A few notes on that table. Apple's support page says iPhone 14 and earlier batteries are "designed to retain 80 percent of their original capacity at 500 complete charge cycles", and iPhone 15 and later at 1,000 cycles. Google's Pixel help says health status "is only available on Pixel 8a and later" and lists the Pixel 6a through 8 Pro as models that don't show it. Samsung's diagnostic gives a grade rather than a number, and menu names vary by model and region.
On Windows, powercfg /batteryreport writes an HTML report and tells you where it saved it. Open it and compare Design Capacity with Full Charge Capacity. Divide the second by the first for a health percentage. A brand-new battery can read slightly above 100%, and that's fine.
On a Mac, Apple's instructions are to hold Option, choose System Information from the Apple menu, then pick Power. The cycle count sits under Battery Information.
The battery test uses the Battery Status API. It gives a page four things: the charge level, whether the battery is charging, and the operating system's guess at time to full or time left. That's it. No capacity, no cycle count, no temperature.
The level is also deliberately coarse. The W3C draft says browsers "SHOULD not expose high precision readouts" because an exact figure helps sites fingerprint you. Our page rounds to whole percent on top of that, so the smallest change you'll ever see is one point.
Support is patchy, too. Chrome has had the API since version 38. Firefox shipped it in version 43 and removed it in 52. Safari never shipped it. So on an iPhone, any Mac browser except Chrome or Edge, or Firefox anywhere, the page says it's not supported. That's a browser rule, not a fault on your device.
There's no single healthy number. A phone playing video at full brightness will drain several times faster than one sitting on a lock screen. What helps is turning a rate into hours, so you can compare it with what the device used to do:
| Steady drain | Runtime from 100% |
|---|---|
| 0.1% per minute | 16 h 40 min |
| 0.25% per minute | 6 h 40 min |
| 0.5% per minute | 3 h 20 min |
| 1% per minute | 1 h 40 min |
| 2% per minute | 50 min |
| 3% per minute | 33 min |
| 5% per minute | 20 min |
The drain test on our page measures for 60 seconds with the screen on and grades the drop. Zero or one point reads as normal, two or three as elevated, four or more as high. Run it a few times under the same conditions before you trust the grade.
Because of the rounding. If the readout goes from 81 to 80, the real drop could have been a sliver (the battery was at 80.51% and slipped to 80.49%) or nearly two whole points. One minute is too short to tell those apart.
| Drop you see | Over 1 minute, real rate is | Over 10 minutes, real rate is |
|---|---|---|
| 1 point | 0 to 2% per minute | 0 to 0.2% per minute |
| 3 points | 2 to 4% per minute | 0.2 to 0.4% per minute |
| 5 points | 4 to 6% per minute | 0.4 to 0.6% per minute |
Stretch the window and the uncertainty shrinks. The ring on the battery test stays live as long as the tab is open, so here's a better method:
If the result is far worse than the device managed when it was new, and nothing else has changed, the battery is the likely suspect.
Cold also cuts runtime for a while, so don't judge a battery on a winter morning walk. If the touch screen acts up at the same time, run the touch screen test, since a swollen battery can press on the display from behind. Our touch screen guide covers that too.
If you're checking a second-hand phone before you pay, the battery is only one part. Run the GPS test outside to make sure location works, then the dead pixel test for the screen. The device test hub has the rest, including the microphone and speakers.
No. A browser can read the charge level, charging state and the system's time estimates, but not capacity or cycle count. For health, use your phone or laptop settings: Settings > Battery > Battery Health on an iPhone, or powercfg /batteryreport on Windows.
Safari has never shipped the Battery Status API, and Firefox removed it in version 52. On an iPhone, open Settings > Battery > Battery Health instead. The test works in Chrome, Edge and Samsung Internet on Android, and in Chrome or Edge on laptops.
A desktop has no battery. The W3C draft tells browsers to report a full, charging battery when there's no battery attached, so that's what you see. It isn't a fault.
Around 80% is the usual line. Apple designs iPhone batteries to keep 80% of their capacity at 500 cycles for iPhone 14 and earlier, and 1,000 cycles for iPhone 15 and later. Replace sooner if the phone shuts off while still showing charge.
It depends on what it's doing. At 0.25% a minute a full charge lasts about 6 hours 40 minutes, at 1% a minute about 1 hour 40 minutes. Measure over 10 to 30 minutes rather than one, because the reading only moves in whole percent.