The engineers at Mozilla have spent years tuning the automatic memory cache algorithm to balance speed, memory pressure, and disk usage. For the vast majority of users, the default setting provides 95% of the performance possible with zero risk.
Decrease or zero out the memory cache to force Firefox to use the disk cache or network exclusively, freeing precious RAM for the operating system. Profile 3: The Developer or Tester Scenario: You are testing a progressive web app (PWA) or a single-page application (SPA). You need to ensure that a specific JavaScript file is always re-fetched from the network, not from a stale memory cache. Browser.cache.memory.capacity
Now go forth, open about:config , and tweak with confidence. The engineers at Mozilla have spent years tuning
Increase the capacity to store more assets in RAM, reducing reliance on the slower disk cache. Profile 2: The User on Constrained Hardware Scenario: You use an older laptop with only 2 GB of RAM. Firefox’s automatic mode attempts a 16 MB cache, but every tab you open pushes your system into swap memory (using the hard drive as fake RAM), causing the entire OS to freeze. Profile 3: The Developer or Tester Scenario: You
In recent Firefox versions (100+), the memory cache is now partially shared with the , blurring the lines between this preference and internal memory management. There is a non-zero chance that Mozilla will lock this value permanently to -1 in future releases, removing manual control.