How to Limit How Much RAM Microsoft Edge Can Consume

Microsoft Edge is, despite what many people believe, a very good web browser. That said, there is always room for improvement. Being based on Chromium, it inherits many of Google Chrome’s best features — but also some of its worst habits. The latter is especially evident in terms of performance, where desktop versions tend to hog an unreasonable amount of system resources.
It is true that both Microsoft and Google have worked to address these shortcomings with varying degrees of success. However, Edge has introduced a very useful and long-awaited feature: a control to limit how much RAM the browser can consume. Starting with Edge version 125, a RAM cap slider is available directly in the browser settings — no flags or registry tweaks required.
Why Edge Uses So Much RAM in the First Place
Before diving into the fix, it helps to understand what’s actually going on. Like Chrome, Edge runs each tab as a separate process. That design makes the browser more stable — one crashing tab won’t take down the rest — but it comes at the cost of memory. Add extensions, background services, and pre-rendering into the mix, and it’s easy to see why Edge can chew through 2–4 GB of RAM even with a modest number of tabs open.
On a machine with 8 GB of total RAM, that leaves precious little headroom for other apps. For gamers especially, having Edge running in the background while playing a demanding title can cause stuttering or slowdowns. That’s exactly the use case Microsoft had in mind when they built the resource controls feature.
How to Enable the RAM Limit in Microsoft Edge
The option lives in Edge’s performance settings and is available in Edge version 125 and later. Here’s how to turn it on:
- Open Microsoft Edge and click the three-dot menu (…) in the top-right corner.
- Select Settings from the dropdown.
- In the left sidebar, click System and performance.
- Scroll down to the Manage your performance section.
- Find the Resource controls toggle and switch it on.
- Once enabled, a slider will appear. Drag it to set a maximum RAM amount — anywhere from 1 GB up to 32 GB, or leave it at “No set limit.”
- Beneath the slider, choose when the limit applies: either “When you’re PC gaming” or “Always.”
That’s all there is to it. Edge will now respect the ceiling you’ve set, offloading unused tabs to disk when it approaches the limit.
Choosing the Right RAM Limit
Setting the limit too aggressively is probably the most common mistake people make with this feature. If you cap Edge at 1 GB on a machine where you regularly have 15 tabs open, you’ll end up with constant tab reloads, stuttering video playback, and a generally sluggish experience. The browser needs memory to function well, so you’re not trying to starve it — you’re just putting a reasonable ceiling on it.
A practical rule of thumb: allocate roughly 30–40% of your total system RAM to Edge. Here’s a quick reference:
- 8 GB system RAM — set the limit to around 2–3 GB for gaming, 4 GB for general use
- 16 GB system RAM — 4–6 GB is a sensible gaming limit; 8 GB if you keep many tabs open
- 32 GB system RAM — you probably don’t need a strict limit, but 8–12 GB keeps things tidy
If you’re not a gamer, setting the limit to “Always” at around 4 GB on a 16 GB machine is a reasonable starting point. You can always adjust it later based on how the browser feels.
Other Built-In Tools That Help with Memory
The RAM cap is the headline feature, but Edge has a couple of other tools worth enabling alongside it.
Sleeping Tabs is one of the most effective memory savers Edge offers. When a tab has been sitting in the background for a set period of inactivity, Edge puts it into a low-power sleep state. According to Microsoft, a sleeping tab uses about 85% less RAM and 90% less CPU than an active one. To configure it, go to Settings > System and performance and toggle on “Save resources with sleeping tabs.” You can set the inactivity timeout anywhere from 5 minutes to 12 hours — 30 minutes is a good default for most people.
You can also add exceptions. If you have a tab you never want to sleep — say, a music streaming service or a work dashboard — click “Add” under “Never put these sites to sleep” and paste in the URL. That site will stay fully active no matter what.
Efficiency Mode (sometimes called “Performance mode”) is another lever in the same settings panel. When enabled, it reduces Edge’s background activity, lowers the priority of inactive tabs, and can bring the sleep timeout down to as little as 5 minutes during resource-heavy moments. It’s a good companion to the RAM limit, especially on laptops where battery life also matters.
Monitoring Edge’s Memory Usage in Real Time
If you want to see exactly which tabs are eating the most memory, Edge has a built-in task manager. Press Shift + Esc while Edge is open, and you’ll get a breakdown of memory and CPU usage per tab, extension, and background process. This is handy for identifying a runaway extension or a tab with a memory leak before it becomes a problem.
The Browser Essentials sidebar (the heart icon in the toolbar, or Settings > Browser essentials) also shows a real-time RAM usage summary for the whole browser. It’s a quicker at-a-glance view when you don’t need the full task manager breakdown.
Troubleshooting: What to Do If Tabs Keep Reloading
If you’ve set a RAM limit and notice that tabs are constantly reloading when you switch back to them, the limit is almost certainly set too low. Raise it by 1–2 GB and see if the behavior improves. Tab reloading isn’t just annoying — it can mean lost form data or interrupted work — so it’s worth taking the time to find a value that actually works for your browsing habits.
Another thing to check: extensions. Some extensions, particularly ad-heavy or script-injecting ones, hold onto significant memory on their own. In the Edge task manager (Shift + Esc), look at the extension rows. If something is using 200–300 MB by itself, it might be worth disabling it and seeing whether a lighter alternative exists.
Finally, keep Edge updated. Microsoft has been actively improving memory management in recent releases, and staying on the latest stable build ensures you’re getting all the performance patches that have shipped since the feature launched.






