Chrome team is experimenting with an option to permanently mute sound on specific websites
Ryan Whitwam / Android Police :
Context & Ripple Effects
This experiment extends a line Chrome has been walking since muting audio in background tabs back in 2015: give users granular control over which sites are allowed to make noise. A per-site permanent mute goes further — the decision sticks across visits rather than applying only to tabs you've left.
The timing matters because it landed just weeks before Google confirmed the bigger hammer: blocking autoplay videos with sound entirely starting January 2018. The per-site flag reads as the fine-grained complement to that blanket policy — and the same playbook later reappeared when Google began auto-disabling stale website notifications on Android and desktop.
First-order effects
- Users get a persistent kill switch for noisy individual sites, while sites that rely on autoplaying or ambient audio lose that channel for anyone who flips the flag.
Second-order effects
- Publishers and ad networks face pressure to design video and audio experiences that earn sound explicitly — a shift compounded by Chrome's January 2018 autoplay block removing the default-on case altogether.
Third-order effects
- If the pattern holds — background tabs, then per-site mutes, then autoplay defaults, then auto-suppressed notifications — browser vendors become the de facto regulators of web UX, with Google deciding by default what sites may do to users' senses and attention.
The trend: Chrome is steadily converting user-hostile web defaults (autoplay audio, intrusive notifications) into opt-in permissions, shifting power over site behavior from publishers to the browser maker.