When you load a webpage, Firefox doesn't just render it and forget it. It intelligently predicts which resources you might need next—preloading linked scripts, next-page images, or CSS for hover states. These predicted resources live in the memory cache.
The memory cache is volatile. Close Firefox, and everything inside browser.cache.memory.capacity vanishes. This is by design. RAM is meant for short-term, high-speed access, not long-term storage.
Use
about:cacheto monitor real-world usage before and after changing the value.
In the world of Firefox's about:config, browser.cache.memory.capacity is the master dial for how much RAM your browser uses to keep the internet "warm." Browser.cache.memory.capacity
Think of your browser like a chef. The Hard Drive (Disk Cache) is the deep freezer in the basement—it holds everything, but it takes forever to go down and get it. The RAM (Memory Cache) is the cutting board right in front of the chef. The Backstory: Speed vs. Space
In the early days of the web, dial-up speeds were the bottleneck. Today, the bottleneck is often how fast your computer can move data from storage to the screen.
The Default (-1): Most users leave this at -1, which tells Firefox to use a dynamic heuristic. It looks at how much total RAM you have and grabs a slice (usually between 4MB and 32MB for older systems, but much more on modern rigs) to keep images and scripts ready for an instant "Back" button click. When you load a webpage, Firefox doesn't just
The Power User's Move: Users with 32GB+ of RAM often manually crank this up (e.g., to 524288 for 512MB) to ensure that even complex, media-heavy tabs never have to "re-fetch" data from the slower SSD. Why People Change It The "story" usually follows one of two paths:
The Minimalist: A user with an old laptop or a tiny 4GB RAM stick wants to stop Firefox from "eating" memory. They set this to a low value or even 0 to force the browser to be lean, accepting that pages might take an extra half-second to reload.
The SSD Saver: Some users worry about the constant "wear and tear" of a browser writing small temporary files to an SSD. By disabling the Disk Cache (browser.cache.disk.enable = false) and increasing the Memory Capacity, they force the browser to live entirely in the "volatile" RAM, which clears every time the computer restarts—keeping the SSD pristine and the browsing lightning-fast. Key Settings to Know Preference Recommended Action -1 Let the browser decide based on your system RAM. 0 Use about:cache to monitor real-world usage before and
No memory caching. Every "Back" click reloads from disk/web. Integer (KB) Set your own limit (e.g., 131072 for 128MB).
Pro-Tip: You can see exactly what's sitting on your "cutting board" right now by typing about:cache into your address bar and looking for the memory section.
Any reason not to make more RAM available for browser cache?
True for most. Unless you have a specific bottleneck or benchmark data, -1 is the safest, most intelligent setting.
"browser.cache.memory.capacity" is a configuration preference historically used in some web browsers (notably Mozilla-based browsers) to control the size of the in-memory HTTP cache. It determines the maximum amount of RAM the browser will dedicate to storing cached resources—HTML, CSS, JavaScript, images, and other fetched assets—so they can be served quickly without re-fetching from disk or network.