Chrome team is experimenting with an option to permanently mute sound on specific websites
A lot of awful things can happen on the internet, but few are as terrible as landing on a website that automatically plays videos with sound. Thankfully, this is something Google is addressing in a future update to Chrome.
Context & Ripple Effects
This experiment extends a line Google has been walking since it enabled muting of audio in background tabs back in 2015. The difference here is granularity: instead of silencing tabs after the fact, users would be able to permanently blacklist specific sites' sound.
Weeks later, the team went further still, announcing that Chrome will stop autoplaying videos with sound entirely starting January 2018 — turning what began as a manual per-site control into a platform-wide default. The arc matters because it shows Chrome moving from giving users tools against intrusive sites to deciding for them.
First-order effects
- Users gain a persistent per-site mute switch, so a single visit to an autoplaying news or video site no longer means repeated manual silencing.
- Publishers whose traffic model depends on autoplaying sound in Chrome see those impressions lose their audio — and, once the January 2018 policy lands, the autoplay itself.
Second-order effects
- Ad and video publishers are pushed toward click-to-play and muted-by-default formats as Chrome's defaults harden, since the browser now sets the terms of how media can start.
- Rival browsers face pressure to match Chrome's stance, because a browser perceived as noisier than Chrome loses users who treat autoplay audio as a dealbreaker.
Third-order effects
- If the pattern holds through the autoplay block and later into features like automatically disabling stale website notifications, the structural shift is clear: browsers increasingly act as arbiters of which site behaviors are allowed by default, with publishers designing around whatever Chrome permits rather than what the open web allows.
The trend: Chrome is steadily converting user-side controls over intrusive site behavior — background-tab audio, autoplay sound, stale notifications — into platform-enforced defaults that reshape how publishers build for the web.