Chrome tackles notification overload with automatic revocation
Google Chrome is rolling out a feature that quietly trims notification permissions from websites users haven’t visited in a while. The update, now available on Android and desktop, aims to reduce the flood of interruptive alerts while keeping control firmly in the hands of the user.
According to a company blog post, Chrome will automatically revoke notification permissions for sites that haven’t been interacted with recently. The change is designed to minimize disruption without fully disabling a user’s browsing experience. Notably, the feature does not affect notifications from installed web apps, which will continue to send alerts as before.
How the feature works
When Chrome determines that a site hasn’t seen recent activity, it will revoke its permission to show desktop and mobile notifications. If a user wants to restore access, they can do so easily through the Safety Check tool or by revisiting the site’s settings. Users also retain the option to disable the auto-revocation feature entirely if they prefer to keep all notifications active regardless of past visits.
Why Chrome is making this change
Chrome’s developers highlight a common pain point: notification overload. They note that fewer than 1% of all notifications see user interaction, underscoring how many alerts go ignored and contribute to a sense of disruption. The auto-revocation mechanism is therefore a precautionary step toward a calmer, more manageable notification ecosystem within Chrome.
Safety Check and user autonomy
As part of its broader safety and privacy initiatives, Chrome already uses Safety Check to manage several permissions, including camera and location access. The new approach to notification permissions complements these existing safeguards by providing a simple, opt-in/opt-out path for users to recalibrate their alert experience without compromising the functionality of sites they rely on or trust.
Preliminary results and user impact
In Chrome’s experiments, the auto-revocation feature led to a noticeable decrease in notification volume with only a minor impact on total notification interactions. Interestingly, the company observed that sites delivering fewer notifications tended to retain or even increase engagement, suggesting a more relevant set of alerts reaches users when the noise is reduced.
What this means for everyday browsing
For most users, the change translates into a cleaner notification surface and fewer interruptions during work, study, or leisure. It also reinforces the idea that Chrome is prioritizing user control and privacy, rather than allowing a constant stream of permission prompts to interrupt the browsing experience.
What to expect next
The auto-revocation feature is live on Android and desktop and will continue to evolve as Chrome gathers real-world feedback. Users who depend on certain sites for timely alerts can simply re-enable permissions through the Settings menu or Safety Check if needed. As Chrome’s safety and privacy features mature, more developers will be encouraged to design respectful notification strategies that align with user preferences.
