Google announced that Chrome 154, set for release in October 2026, will make “Always Use Secure Connections” the default for all users. This change means Chrome will automatically try to connect over HTTPS, and if a site doesn’t support it, the browser will display a warning before users can proceed.
This move follows years of progress in web security. Back in 2015, only about 30 to 45 percent of Chrome page loads used HTTPS. By 2020, that number had climbed to between 95 and 99 percent, where it has largely plateaued. Google says the web is now mature enough for HTTPS to be the default standard rather than an optional feature.
The “Always Use Secure Connections” setting was first introduced in 2022 as an opt-in option. It protects users from attacks that exploit unsecured HTTP connections, which can let attackers intercept or alter web traffic. Even one insecure connection can expose users to malware or fake websites.
To minimize disruption, Chrome will limit how often warnings appear. Frequent visitors to certain HTTP sites, especially private local ones like routers or internal company portals, won’t see repetitive alerts. Warnings will mainly target new or public HTTP sites that pose real risks.
Developers and IT admins are encouraged to enable the feature now to identify systems still using HTTP. Enterprise and education administrators will also have policy controls to manage how the setting rolls out across their organizations.
While this is a great addition, it does feel late. Google should have made HTTPS the default years ago, especially since nearly every major website already uses encryption. Users have been conditioned to expect secure connections for almost a decade, and waiting until 2026 to enforce this setting feels more like catching up than leading. Still, the change will make Chrome safer for everyday users and help push the final few holdouts away from insecure protocols.
