Firefox updates: Mozilla is drastically shortening the release cycle
Users of the Firefox web browser will soon receive updates twice as often. Starting in September 2026, the company is switching the release cycle for desktop and Android from four weeks to two weeks. This is primarily intended to increase security.
Faster update cycle
From September 1, 2026, the frequency of updates to the Firefox web browser will change. The versions for desktop computers and Android devices will then receive an update every two weeks instead of every four as before. The starting signal for the new model falls with the release of Firefox 155. The previous version 154 on August 18th marks the end of the old monthly rhythm. With this step, the developer is reacting to changing conditions in IT security. Through the use of artificial intelligence, security researchers and attackers alike are detecting vulnerabilities in software ever more quickly. A shorter period of time between program versions allows the development team to close critical security gaps more quickly and distribute necessary bug fixes to end users much more quickly, instead of having to wait weeks for the next deadline.
Security instead of time pressure
As the company writes in a message to its own developers (via PiunikaWeb), the change is initially an experiment. The company emphasizes that the faster cycle must not come at the expense of quality. Unfinished features should not be released hastily. They receive the necessary maturation time and simply appear in one of the subsequent versions. Firefox is now catching up with its competitors Google Chrome and Microsoft Edge, which have also switched to a two-week cycle. Since Firefox is based on the independent rendering engine Gecko, the more frequent release cycle requires a standalone infrastructure. In contrast to the competition’s Chromium-based browsers, the team has to manage the entire process themselves.
Impact on users
For most private users, the transition takes place unnoticed in the background. Those who work in corporate environments or prefer a more consistent work environment have alternative options for keeping the system stable. This includes using the extended support release version for less frequent, stability-focused updates as well as manually controlling update installation via the browser’s general settings. Browser extension developers also need to adapt their testing cycles to the new rhythm. The shortened time period increases the frequency of changes to the programming interfaces, which requires faster updating of your own software extensions. The company reserves the right to cancel the experiment if the burden on the team becomes too high or the quality of the software decreases.
