Browser.cache.memory.capacity Official
On older systems or devices with limited memory (like a low-end laptop or a Raspberry Pi), Firefox can sometimes be "memory hungry". If you find that your entire system slows down or hits its swap file when Firefox is open, manually capping the memory cache can prevent the browser from crowding out other essential system processes. Related Settings for Power Users
This parameter operates using specific integer values measured in . It works alongside browser.cache.memory.enable , which must be set to true for the capacity rule to apply. The configuration accepts three main types of inputs: Firefox/Tweaks - ArchWiki Browser.cache.memory.capacity
The browser.cache.memory.capacity preference is a shining example of why many power users love Firefox: it gives you unprecedented control over how the browser utilizes your system's resources. On older systems or devices with limited memory
Conversely, power users with 32GB or 64GB of RAM may increase this value significantly. A larger memory capacity ensures that even high-resolution media and heavy scripts remain "hot" in the RAM, reducing the need to re-parse data from the disk. The Trade-off It works alongside browser
There are three distinct profiles of users who might want to deviate from the -1 default.


