Battery Charging Status

Back to Main

Battery Charging Detection

Checking...

Note: Battery Status API is deprecated. This feature has been removed from modern browsers.

1. Technical Classification

Battery Status APIDeprecatedPrivacy ConcernRemoved

The charging status was part of the Battery Status API, indicating whether a device was plugged into power or running on battery. Like battery level, this was removed due to privacy concerns.

2. Background & Purpose

Charging status was intended to help websites adapt behavior based on power availability. The idea was that websites could be more aggressive with features when plugged in, and conservative when on battery.

Original Use Cases

3. Possible Values & Detection

Original Values (When Supported)

true

Device is plugged in and charging

false

Device is running on battery power

Current Status

API completely removed from modern browsers. No longer accessible.

4. Common Legitimate Uses (Historical)

Power-Aware Applications

5. Browser & Platform Differences

BrowserStatusWhen Removed
ChromeRemovedVersion 103 (2022)
FirefoxRemovedVersion 72 (2020)
SafariNever supportedN/A
EdgeRemovedFollowing Chromium

6. Privacy Implications & Tracking Risks

Privacy Risk: MEDIUM (when it existed)

Charging status contributed to device fingerprinting, especially when combined with battery level and other system information.

Fingerprinting Via Charging Status

While a simple binary value (charging/not charging) seems innocuous, it enhanced fingerprinting when combined with:

Behavioral Tracking

Advertisers could infer daily routines. For example, if someone charges from 10pm-7am daily, that reveals sleep schedule. Charging at the same location (work) from 9am-5pm reveals work schedule.

7. Current State & User Protection

No Action Needed

The Battery Status API, including charging detection, has been completely removed from all modern browsers. You're automatically protected.

What This Taught Us

The removal of battery APIs demonstrates browser vendors taking privacy seriously by removing features that, while useful, posed unreasonable privacy risks.

8. Learn More