Chrome has a hidden settings page called chrome://flags. It contains experimental features that are not ready for the main settings menu. Some of them are useless. Some are broken. But a handful directly control how Chrome uses memory.
These 7 flags are the ones that actually reduce RAM. They are not placebo. They are not outdated. They work by making Chrome more aggressive about killing, freezing, or offloading the processes that eat your memory.
chrome://flags and set it to Default. None of these flags will delete your data, but they might make some tabs reload more often.
How to Access Chrome Flags
Type chrome://flags in your address bar and press Enter. Use the search box at the top to find each flag by name. Change the dropdown from Default to Enabled. Restart Chrome when prompted. That is it.
Flag 1: Enable Aggressive Tab Discarding
Chrome already discards inactive tabs when memory gets low. But it waits too long. By the time it acts, your system is already swapping and your browser is sluggish.
This flag makes Chrome discard tabs much earlier. A discarded tab stays in your tab bar but its process is killed. It uses zero RAM. When you click it, it reloads. You might lose scroll position or unsaved form data, but you get your memory back immediately.
This is the single most effective flag for tab hoarders. If you regularly run 20+ tabs, enabling this can cut your RAM usage by 30-40%.
Trade-off: Discarded tabs reload on click. Unsaved form data may be lost.
Flag 2: Enable Tab Freeze in Background
Even when a tab is not active, its JavaScript keeps running. Ads refresh. Trackers ping home. Animations loop. All of this consumes CPU and RAM.
This flag freezes background tabs completely. JavaScript stops. Timers pause. Network requests halt. The tab stays in memory but does nothing. When you click it, it unfreezes instantly. No reload needed.
This is different from discarding. A frozen tab is still in RAM but is not actively consuming resources. A discarded tab is removed from RAM entirely. Both are useful. Use them together.
Trade-off: Background tabs will not refresh until you click them. Notifications might be delayed.
Flag 3: Enable Memory Saver Multi-State
Chrome's Memory Saver mode (Settings → Performance) is either on or off. This flag adds multiple levels: Moderate, Balanced, and Maximum. Maximum mode discards and freezes tabs almost immediately. Moderate mode is gentler and keeps your active tabs responsive longer.
If you have a laptop with 8GB of RAM, set it to Maximum. If you have 16GB and just want to prevent runaway growth, set it to Moderate. The flag gives you control that the default settings menu does not.
Trade-off: Maximum mode can be aggressive with video and music tabs. You might need to add exceptions in Settings → Performance → Always keep these sites active.
Flag 4: Enable High Efficiency Mode
This flag enables a battery-saving mode that also reduces memory pressure. It throttles background JavaScript, reduces animation frame rates, and pauses non-essential timers. It is designed for laptops on battery, but it works on desktop too.
The memory savings come from the background throttling. Less CPU work means less cache pressure and fewer temporary allocations. It is not as dramatic as tab discarding, but it adds up if you keep Chrome open for 12 hours a day.
Trade-off: Some animations and transitions become less smooth. Background web apps might feel sluggish.
Flag 5: Enable Aggressive DOM Storage Flushing
Websites store data in localStorage and sessionStorage. Chrome keeps this data in RAM for fast access. Over time, especially with heavy web apps, this storage can grow to hundreds of megabytes.
This flag forces Chrome to flush DOM storage to disk more aggressively. It trades a tiny bit of speed for lower RAM usage. The impact is small on most sites but noticeable on heavy web apps like Figma, Google Docs, and complex dashboards.
Trade-off: Slightly more disk writes. Minimal performance hit on SSDs. Avoid on very old hard drives.
Flag 6: Enable GPU Rasterization
By default, Chrome renders pages on the CPU using system RAM. This flag offloads rasterization (turning vector graphics into pixels) to your GPU. On systems with a dedicated graphics card, this frees up 200-500MB of system RAM.
The catch is that it uses GPU memory instead. If you have a dedicated GPU with 4GB+ of VRAM, this is a great trade. If you have integrated graphics that shares system RAM, the benefit is smaller or nonexistent. Test it for a day and check your total system RAM usage.
Trade-off: Uses GPU memory instead. Can cause rendering glitches on older or integrated GPUs. Disable if you see visual artifacts.
Flag 7: Enable Memory Saver (Force-Enable)
Memory Saver is now a standard Chrome setting, but some users do not see it. Enterprise policies, older Chrome versions, or certain Linux builds hide the Performance section in Settings. This flag forces Memory Saver to appear and function regardless.
If you already see Memory Saver in Settings → Performance, this flag is redundant. But if you are on a managed machine or an older build and the setting is missing, this flag is your only way to access it.
Trade-off: None. This just exposes a feature that should already be there.
Quick Reference: All 7 Flags
| # | Flag | Impact | What It Does |
|---|---|---|---|
| 1 | Aggressive Tab Discarding | High | Kills inactive tab processes earlier. Tabs reload on click. |
| 2 | Tab Freeze Background | High | Pauses JavaScript in background tabs. No reload needed. |
| 3 | Memory Saver Multi-State | Medium-High | Adds Moderate/Balanced/Maximum levels to Memory Saver. |
| 4 | High Efficiency Mode | Low-Medium | Throttles background JS and animations. Cumulative savings. |
| 5 | Aggressive DOM Storage Flushing | Low-Medium | Flushes web app storage to disk instead of keeping it in RAM. |
| 6 | GPU Rasterization | Variable | Offloads rendering to GPU. Frees system RAM on dedicated GPUs. |
| 7 | Memory Saver (Force-Enable) | High | Exposes Memory Saver on systems where it is hidden. |
What These Flags Will Not Fix
Flags are not magic. They optimize how Chrome manages the tabs and processes you already have. They do not fix the root cause of RAM bloat, which is usually:
- Too many extensions. Every extension runs as a separate process. Flags will not fix a 200MB VPN extension. Remove it.
- Opening tabs for glances. If you open 50 tabs a day "just to check," flags will only make Chrome discard them faster. The better fix is previewing links instead of opening them. Use GoPeek for that.
- Heavy web apps. A single Google Sheets document with 10,000 rows will use 800MB no matter what flags you enable. The flag helps, but the app is the problem.
- Corrupted profile data. If Chrome has been slow for months, your profile might be corrupted. Flags will not fix cache leaks. Clear your browsing data or create a new profile.
Think of flags as tuning your engine. They make Chrome run more efficiently. But if you are carrying 500 pounds of junk in the trunk, tuning the engine is not enough. You also need to unload the trunk.
My Recommended Order
If you only enable three flags, make them these:
- Aggressive Tab Discarding — Immediate, high-impact RAM reduction.
- Tab Freeze Background — Stops background tabs from eating CPU and RAM passively.
- Memory Saver Multi-State — Gives you granular control over how aggressive Chrome should be.
The other four are nice to have. Enable them if you want the full optimization stack. Skip them if you just want the biggest wins with the least risk.
The Bottom Line
Chrome flags are free, reversible, and take 30 seconds to enable. The 7 flags above are the ones that directly target memory usage. They work by making Chrome more aggressive about killing, freezing, or offloading the processes that sit idle in your RAM.
Enable them. Restart Chrome. Check your RAM usage after a day of normal browsing. If you see a drop, keep them. If something breaks, set that flag back to Default. There is no risk in experimenting.
But remember: flags optimize what you already have. The bigger win is preventing tabs from existing in the first place. Combine these flags with a preview workflow, and Chrome becomes fast again.