Skip to main content
Web Development 2 min read

Chrome now updates every two weeks: what it means for your site

Since Chrome 153, Google ships a new version of its browser every two weeks instead of every four. What that means for your website's security and upkeep.

Since September 8, with the arrival of Chrome 153, Google ships a stable version of its browser every two weeks instead of every four. Google announced the change in March and it's now in effect: Chrome 154 followed two weeks later, and the pace will continue.

What happened

The change covers Chrome on every platform: Windows, macOS, Linux, Android and iOS. According to Google, each release will be smaller, which lowers the risk of bugs and makes it easier to trace a problem back to its source when one appears.

  • Stable: a new version every two weeks, with security fixes and new features.
  • Beta: also every two weeks, arriving about three weeks before stable. This is the one to test with.
  • Extended Stable: the option for businesses that need more breathing room stays on its eight-week cycle.

Chrome is the world's most used browser, so its calendar largely sets the pace for the whole web.

What it means for your business

For most users this is good news: security patches arrive sooner, and browser vulnerabilities stay exposed for less time.

For anyone with a website or web app, the message is different: the environment your customers view your site in changes twice as fast. Each Chrome release can bring new features, but also changes to how certain elements render, to cookies or to privacy. Most of them don't affect anything, but now and then an update breaks a form, a checkout or an integration, and at this pace there are more chances for that to happen.

The real problem is not noticing. Many small business sites only get checked when a customer reports that something isn't working.

What we recommend

  1. Regularly check the critical parts of your site in the latest Chrome: contact forms, cart and checkout, bookings, login.
  2. If you have a custom web app, test it in Chrome Beta. That way you catch problems about three weeks before they reach your customers.
  3. Set up some form of error alerts, such as a monitoring tool or notifications on your forms, so you know when something breaks without waiting to be told.
  4. For companies with many computers, consider whether the eight-week Extended Stable channel suits you, at the cost of getting new features later.
  5. Keep your own browser up to date. It's the simplest way to get security patches as soon as they ship.

In short

Chrome now updates twice as fast. That's better for security, but it means checking more often that your site still works as it should. If you'd like maintenance that reviews your site on a regular schedule, let's talk.

Source: Chrome for Developers (developer.chrome.com)

Share

Keep reading