Browser.cache.memory.capacity
browser.cache.memory.capacity is a Mozilla-based browser (like Firefox, Thunderbird, or Pale Moon) preference that determines the maximum amount of Random Access Memory (RAM) dedicated to caching decoded images, script data, and other web content.
Unlike the disk cache, which saves data to your physical drive to persist between sessions, the memory cache is temporary and cleared when you close the browser. Key Values & Functions
-1 (Default): Tells the browser to automatically determine the capacity based on your system's total physical RAM.
0: Effectively disables the memory cache. This is generally not recommended as it forces the browser to fetch data from the slower disk cache or the internet for every request, potentially slowing down navigation.
Positive Integer: A custom limit set in Kilobytes (KB). For example, entering 524288 would cap the memory cache at 512 MB. How to Modify It Open your browser and type about:config in the address bar. Search for browser.cache.memory.capacity. Double-click the entry and enter your desired value in KB.
Ensure browser.cache.memory.enable is set to true for this to take effect. Why Adjust This Setting?
Any reason not to make more RAM available for browser cache?
The configuration setting browser.cache.memory.capacity is an advanced preference in Firefox-based browsers (accessible via about:config) that manually determines the maximum amount of system RAM used for the memory cache. Core Functionality
Purpose: It stores copies of recently visited site data (like images and scripts) directly in your RAM rather than on your disk. This allows for near-instant retrieval when you hit the "Back" button or revisit a page in the same session.
Default Behavior: By default, Firefox automatically manages this value based on your total system RAM. For instance, on a 4GB system, it may default to roughly 30 MB. Key Values & Customisation Recommendation -1 (Default)
Best for most users; allows the browser to scale based on available memory. 0
Disables memory caching entirely. Not recommended unless troubleshooting major leaks. Positive Integer Fixed Size
Set in Kilobytes (KB). For example, 51200 is 50MB, and 1048576 is 1GB. Performance Impact Review Pros (High Values): Browser.cache.memory.capacity
Speed: Significant reduction in page load times for revisited content because RAM is vastly faster than even the best SSDs.
Reduced Disk Wear: Minimizes constant read/write cycles to your SSD, which can theoretically extend its lifespan. Cons (High Values):
Memory Fragmentation: Very high values (e.g., above 1GB) can lead to memory fragmentation and higher overall browser instability.
System Slowdown: If you have limited RAM (8GB or less), assigning a massive cache can "starve" other applications and the OS, leading to stuttering. Expert Consensus
limit the memory cache to a reasonable value - Mozilla Bugzilla
The preference browser.cache.memory.capacity is a hidden setting in Firefox's about:config that controls the maximum amount of RAM allocated for the browser's memory cache.
Increasing this value can speed up page navigation (especially the Back/Forward buttons) by keeping recently visited pages in RAM instead of reloading them from the slower disk or the internet. How to Configure It
Access Settings: Type about:config in your address bar and click "Accept the Risk and Continue."
Find or Create: Search for browser.cache.memory.capacity. If it doesn't exist, right-click (or click the "+" button), choose New > Integer, and name it exactly as above.
Enter Value: Input the amount of RAM you want to use in Kilobytes (KB):
-1: The default setting. Firefox dynamically determines the size based on your total system RAM. 0: Disables the memory cache entirely.
Custom (e.g., 131072): Sets a fixed limit (e.g., 131,072 KB = 128 MB). Common Use Cases browser
In the architecture of modern web browsers, specifically within the Gecko engine (Firefox), browser.cache.memory.capacity
serves as a critical configuration parameter that defines the ceiling for RAM-based caching. By managing how much high-speed memory is dedicated to storing decoded images and "chrome" (the browser's own UI elements), this setting sits at the intersection of performance optimization and resource conservation. mozillaZine The Mechanics of Memory Caching
Unlike disk caching, which writes data to a persistent physical drive, memory caching utilizes a portion of the system's
to store frequently accessed data. The primary objective is to minimize latency. Retrieving a script or image from RAM is significantly faster—often by orders of magnitude—than pulling it from a hard drive or re-downloading it from a remote server. mozillaZine browser.cache.memory.capacity value is expressed in kilobytes (KB) mozillaZine A value of -1 (Default):
Instructs the browser to dynamically determine the optimal cache size based on the total available system RAM. Specific Integer:
Allows users to manually cap memory usage. For instance, a value of
would allocate approximately 200 MB for this specific cache.
Disables memory caching entirely, forcing the browser to rely on disk cache or constant network requests. mozillaZine Performance vs. Resource Management
The decision to modify this capacity often stems from a fundamental trade-off: High Capacity Benefits:
Increasing the capacity allows more complex assets to remain in memory, leading to near-instantaneous load times for previously visited pages and smoother navigation. Low Capacity Benefits:
Reducing the value is a common strategy for systems with limited RAM. It prevents the browser from "bloating" and ensures that other essential applications have sufficient memory to function without being forced into swap or virtual memory. mozillaZine Modern Context and Obsolescence
In recent versions of Firefox, the transparency of this setting has sparked debate. While the parameter can still be manually added or modified via the Advanced Preferences (about:config) page Myth 2: "Firefox uses all my RAM because
, some users report that it feels increasingly obsolete as browsers move toward more aggressive, automated multi-process architectures. Furthermore, tools like the Firefox Cache Monitor (accessed via about:cache?device=memory
) allow users to verify if their manual caps are actually being honored by the underlying engine.
Any reason not to make more RAM available for browser cache?
Myth 2: "Firefox uses all my RAM because of this setting"
False. By default (-1), Firefox caps memory cache aggressively. If Firefox is using 4 GB of RAM, it's due to web content (heavy JavaScript, video streams, leaked memory in tabs), not the memory cache.
Resetting to Default
To revert:
- Go to
about:config - Find
browser.cache.memory.capacity - Right-click → Reset
It will return to -1.
Part 4: How to Modify browser.cache.memory.capacity (Step-by-Step)
Warning: Editing advanced preferences can cause browser instability. Follow these steps carefully.
Deep Dive: Understanding browser.cache.memory.capacity in Firefox
In the ecosystem of web browsers, speed is the ultimate currency. While modern browsers are remarkably fast out of the box, there remains a class of power users and system administrators who refuse to accept "good enough." For these users, Mozilla Firefox offers a gateway to granular control via the about:config interface.
Among the hundreds of hidden preferences lies a particularly powerful, yet often misunderstood, integer value: browser.cache.memory.capacity .
This article explores what this preference does, how it interacts with the browser's multi-layered caching architecture, how to optimize it for different hardware configurations, and why you might (or might not) want to change it.
Step 6: Restart Firefox
Changes do not take effect until you fully close and restart the browser.