







Firefox has long had a reputation for using too much memory. The accuracy of that reputation has varied over the years but it has stuck with the browser. Every Firefox release in the past several years has been met by skeptical users with the question "Did they fix the memory leak yet?" We shipped Firefox 4 in March 2011 after a lengthy beta cycle and several missed ship dates–and it was met by the same questions. While Firefox 4 was a significant step forward for the web in areas such as open video, JavaScript performance, and accelerated graphics, it was unfortunately a significant step backwards in memory usage.
Clarifying the Future of Firefox Screenshots – Future Releases
Screenshots has been a popular part of Firefox since its launch in Firefox 56 in September 2017. Last year alone it was used by more than 20 million people to ...

Firefox Maker Mozilla Is Flailing When the Web Needs It the Most
The organization is losing relevance in a world where the desktop browser is less important.

Mozilla downsizes as it refocuses on Firefox and AI: Read the memo | TechCrunch
After installing a new interim CEO earlier this month, Mozilla, the organization behind the Firefox browser, is making some major changes to its product

Exciting Improvements Delivered Today in Firefox for Desktop and Android | The Mozilla Blog
Today we’re proud to announce the initial rollout of multi-process Firefox for Desktop to our general audience. With this, we’re taking a major step fo

The Legacy of Firefox OS
In the two years or so since Mozilla announced the end of Firefox OS as a Mozilla-run project, the B2G source code has found its way into a

Is Firefox OK?
Mozilla’s privacy-heavy browser is flatlining. What it does next is crucial for the future of the web.

Multi-process Firefox brings 400-700% improvement in responsiveness | TechCrunch
Earlier this summer I wrote about Mozilla's efforts to rollout a multi-process architecture, codename Electrolysis, for Firefox. In the months since,

Suhail on Twitter / X
He who owns the browser, shall own the memory. https://t.co/ENA04zwo82— Suhail (@Suhail) June 24, 2025
Reducing Adobe Flash Usage in Firefox – Future Releases
Browser plugins, especially Flash, have enabled some of our favorite experiences on the Web, including videos and interactive content. But plugins often introduce stability, performance, and security issues for browsers. ...

The whole web at maximum FPS: How WebRender gets rid of jank – Mozilla Hacks - the Web developer blog
The Firefox Quantum release is getting close. It brings many performance improvements, including the super fast CSS engine that we brought over from Servo. But there’s another big piece of ...

Exploring the Firefox community on r/firefox | The Mozilla Blog
Open source thrives because of its people. Firefox, like so many successful open-source projects, is powered by passionate contributors and dedicated suppo

The Story of Firefox OS
I remember at a team dinner once Mitchell Baker, Mozilla’s Chairwoman and “Chief Lizard Wrangler”, talked about the importance of…

The Story of Firefox OS
I remember at a team dinner once Mitchell Baker, Mozilla’s Chairwoman and “Chief Lizard Wrangler”, talked about the importance of…

Sebastian Aaltonen on Twitter / X
No wonder iTerm2 is so bloated. They just added a web browser inside the terminal. Who asked for this?Empty iTerm2 window now uses 400MB of RAM :( pic.twitter.com/JhkHp4WUjM— Sebastian Aaltonen (@SebAaltonen) September 22, 2025

What to Look Forward to from Firefox OS – Future Releases
Firefox OS is an important part of our mobile strategy, in addition to Firefox for Android and other initiatives. We believe that building an open, independent alternative to proprietary, single-vendor ...

Why Did Mozilla Remove XUL Add-ons?
TL;DR: Firefox used to have a great extension mechanism based on the XUL and XPCOM. This mechanism served us well for a long time. However, it came at an ever-growing cost in terms of maintenance for both Firefox developers and add-on developers. On one side, this growing cost progressively killed any effort to make Firefox secure, fast or to try new things. On the other side, this growing cost progressively killed the community of add-on developers. Eventually, after spending years trying to protect this old add-on mechanism, Mozilla made the hard choice of removing this extension mechanism and replacing this with the less powerful but much more maintainable WebExtensions API. Thanks to this choice, Firefox developers can once again make the necessary changes to improve security, stability or speed. During the past few days, I’ve been chatting with Firefox users, trying to separate fact from rumor regarding the consequences of the August 2020 Mozilla layoffs. One of the topics that came back a few times was the removal of XUL-based add-ons during the move to Firefox Quantum. I was very surprised to see that, years after it happened, some community members still felt hurt by this choice. And then, as someone pointed out on reddit, I realized that we still haven’t taken the time to explain in-depth why we had no choice but to remove XUL-based add-ons. So, if you’re ready for a dive into some of the internals of add-ons and Gecko, I’d like to take this opportunity to try and give you a bit more detail.