The era of browsers changing once every six weeks is over. Google announced a two-week cycle for Chrome back in March 2026, and Chrome 153 from September 8 is the first release on that rhythm. Microsoft Edge adopted the same pace with version 152 on August 27, and Mozilla with Firefox 155 on September 1. Firefox 156 followed on September 15 and Edge 153 three days later. In September, all three major browsers aligned on the same cadence.
Why this is happening
The reason is simple: smaller batches of changes are easier to test and easier to roll back. Security fixes also reach users faster, which is timely this year. Chrome alone has patched seven actively exploited zero-days. A faster cycle also means new web standards, such as new CSS features or APIs, arrive in production gradually rather than in big jumps.
What it means for developers
A shorter cycle is not only about new features. It also means more moments when behavior your site relies on can change. Worth putting in place:
- Testing in beta and dev channels. If you run a site with critical flows (checkout, booking, forms), watch upcoming versions before they reach all your customers.
- Automated browser tests. Tests that walk the main paths of your site on every change are moving from a luxury to a necessity.
- Feature detection instead of version sniffing. Code that asks whether a browser supports a feature survives any release pace. Code that checks version numbers does not.
- Watching deprecation notices. Treat deprecation warnings in the developer console as signals, not noise.
What it means for site owners
For an ordinary business site the good news is that modern browsers preserve backward compatibility and most changes pass unnoticed. The risky sites are those built on outdated plugins, custom scripts written years ago, or libraries nobody updates. They break first, and often quietly: one button, an order form or a payment stops working, and you hear about it from a customer.
There is an upside too. New capabilities for performance and user experience reach real-world use sooner, so you can improve speed, accessibility and looks without waiting for slow cycles. Those who maintain their site regularly benefit. Those who leave it standing face more risk.
A practical checklist
Once a month, open your site in the current Chrome, Firefox and Edge and walk through the key paths: contact form, cart, login, search. Check the console for errors. Update the core, theme and plugins. And if your site is one nobody maintains, it is time to change that before the browser changes it for you.
Conclusion
The two-week browser cycle is the new normal. Maintained and tested sites will barely notice it. The others will be surprised more and more often. If you want to be sure your site works in every browser after every update, contact the Full-Net team. We will review your site and set up regular maintenance.
