Browser.cache.memory.capacity !!hot!! Review
browser.cache.memory.capacity is a configuration preference in Firefox-based browsers that determines the maximum amount of
(system memory) the browser can use to store cached web content for rapid retrieval. mozillaZine Key Functions
: It stores decoded images and UI elements ("chrome") in RAM to speed up navigation between previously visited pages. Performance Impact Higher Value
: Increases page load speeds for visited sites but consumes more of your computer's RAM. Lower Value Browser.cache.memory.capacity
: Frees up RAM for other applications but may cause the browser to re-download elements or fetch them from slower disk storage. mozillaZine Core Values and Meanings Description -1 (Default) Automatic Management.
The browser dynamically adjusts the memory cache size based on your total available system RAM. the memory cache entirely. Positive Integer fixed limit in Kilobytes (KB) . For example, would limit the cache to 32 MB. How to Modify Settings To access or change this setting in Firefox: about:config in the address bar and press Accept the Risk and Continue Search for browser.cache.memory.capacity
Double-click the value to edit it, or use the plus/pencil icon to create it if it doesn't exist. browser.cache.memory.enable for these changes to take effect. mozillaZine Related Configuration Tips Checking Current Usage browser
: You can see how much memory is currently being used by the cache by typing about:cache into the address bar. Disk vs. Memory Cache browser.cache.memory.capacity handles RAM, browser.cache.disk.capacity controls how much space is used on your hard drive/SSD. Individual Entry Limits : The preference browser.cache.memory.max_entry_size
sets a limit on the size of any single file allowed into the memory cache to prevent one large file from hogging all allocated space. Mozilla Support recommended manual values for specific RAM capacities like 8GB or 16GB?
Based on the preference name Browser.cache.memory.capacity, this appears to be a low-level browser setting (historically from Mozilla/Firefox) that controls the maximum size of the in-memory cache. Part 8: How to Verify Your Change Actually
Here is a feature concept built around exposing and enhancing this preference for a privacy-focused or developer-oriented browser:
Part 8: How to Verify Your Change Actually Worked
Changing the preference is one thing. Verifying it is another.
The Case for Decreasing Capacity
Scenario: You are running Firefox on a legacy system with 4GB of RAM. You also run a Virtual Machine, Adobe Photoshop, or a local development server (Docker, Node). Every megabyte matters.
Outcome: A large memory cache will cause the operating system to swap memory to the page file on disk. Once swapping begins, performance collapses. In this context, a restrictive memory cache forces Firefox to be "neighborly" to other processes.
Recommended value: 51200 (50 MB) or 25600 (25 MB). Alternatively, leaving it at -1 often works, but manual caps can prevent aggressive caching spikes.
User benefits
- Faster back/forward navigation without OOM crashes.
- Privacy by preventing sensitive pages lingering in RAM.
- Auto-tuning for gaming or development systems.
Method 1: The about:cache Interface
- Type
about:cacheinto the Firefox address bar. - Click on the "Memory cache device" link.
- Look for:
- Maximum storage size: This should match the value you set (in KB).
- Storage in use: How much of that capacity is currently filled.